Also, if you’ve set halfway already, you probably will access the router if internet is disconnected.
Set your PC to 192.168.1.11 (eg.) fixed IP address for the time of modification.
Please reset the router to factory defaults from Administration>Factory defaults after replacing the firmware every time.
You’ll no longer be able to run remote commands with the new build, but it will work flawlessly. Old builds are very old now and can’t communicate perfectly with today’s devices every now and then.
We are sorry for replying this late. Could you verify that your AP is working well with another firmware/setting?
If it loses all information with a reboot, then it’s probably a device issue.
First off, please do not modify the hotspot subnet of 192.168.182.0 unless you have specific problems.
Second, the WAN and LAN side of the hotspot router/computer cannot be in the same subnet, for networking standard reasons.
The following syntax is not OK: ‘HS_DYNIP=192.168.1’ in the default.conf file.
You cannot avoid NAT, otherwise coovachilli simply won’t work. So you have to enable it, by setting up two different subnets(and masquerading) on the two sides of the coovachilli processing network ‘node’.
There are a few things to put together with coovachilli on linux.
Can you ping anything on the internet from the linux based machine?
If yes, then you don’t get proper routing.
The interface of the hotspot (not tun0, but its physical carrier) should have an ACCEPT, ACCEPT, REJECT firewall rule(input, output, forward) forwarding rule in the firewall file. It also has to have a proper zone section defined in the firewall file.
Like this:
config ‘zone’
option ‘name’ ‘eth3’ (e.g.)
option ‘input’ ‘ACCEPT’
option ‘output’ ‘ACCEPT’
option ‘forward’ ‘REJECT’
option masq ‘1’ (you probably need this to have NAT from this interface towards the gateway interface)
