After adding a virtual interface in Wireless -> Wireless Security -> Virtual Interfaces the virtual interface gets added successfully. However, after selecting "Advanced Settings" then selecting "Unbridged" from "Network Configuration" I am unable to specify an IP and subnet mask.
I specify e.g.
IP: 192.168.2.1
Subnet mask: 255.255.255.0
However, even as I type "255" I'm told the range must be "1 - 223"!
Why is 255.255.255.0 not a valid subnet mask for 192.168.2.1? I tried some other IPs too, like 192.168.1.1, 10.0.0.1, etc. They all have the same problem.
Then I tried to edit the javascript on the web page and removed the restriction, then I can add it, but the settings didn't get applied.
Furthermore, no settings related to "Advanced Settings" are actually applied! Even if I don't specify an IP (or even a "valid" IP/subnet which it asks for), I click "Apply", then go to a different menu and back again, and the settings are now erased, by "erased" I mean that the "Advanced Settings" checkbox was ticked before, now the tick is gone.
I've tried saving, then applying, applying, then saving, but it doesn't seem to matter at all.
The same problem happens if I try to do this through Setup -> Networking -> Bridging.
I can successfully create the bridge, however, when I try to add an IP and subnet mask, it fails. In this part of the menu system I'm not told by some javascript I can't do it, but applying it just removes the IP address and subnet mask I specified and doesn't seem to apply it at all (from ifconfig when I telnet into the device).
Thanks, installed the latest build and I am allowed to add a sane subnet mask.
However, I don't get much closer. I can authenticate, but I don't obtain any IP by DHCP. Furthermore, when I telnet in and check ifconfig, there is no interface that has the IP I've assigned (I would expect to see ath0.1 in my case have 192.168.2.1 at subnet 255.255.255.0).
I didn't forget to add an entry for "Multiple DHCP server". I've added one on ath0.1, which then gets listed as:
"Interface ath0.1: IP 192.168.2.1/255.255.255.0".
However, then I noticed that when I click "save" (apply works), the settings are dropped and it reverts it back to "br0".
Furthermore, when I force my test client to have 192.168.2.125 and the ath0.1 interface to have 192.168.2.1 (both on 255.255.255.0) I am unable to ping 192.168.2.1 from 192.168.2.125, even though I am successfully authenticated.
While you are telenet 'in around there run
cat /tmp/dnsmasq.conf
and lets see what she says. You don't have to include any dhcp-host you may have set.
EDIT:
fractal5 wrote:
I am unable to ping 192.168.2.1 from 192.168.2.125, even though I am successfully authenticated.
You won't be able to ping it if 'Net Isolation' is turned on.
That was without "Net Isolation".
After doing a factory reset, and following the guide verbatim once more, it now for whatever reason appears to give me an IP. But it gives me an IP on 192.168.2.0/24, even though the ath0.1 interface is configured up on 10.0.0.0/24 (IP 10.0.0.1).
Furthermore, I can reach the whole LAN even though I have both AP and Net isolation enabled. Why would it lease IPs from 192.168.2.0/24?
Edit:
Sorry about that, it got 192.168.2.111 because I was forcing the interface to have that on my test laptop (obviously). However, I still don't understand why I can reach the LAN from the guest network.
After doing a factory reset, and following the guide verbatim once more, it now for whatever reason appears to give me an IP. But it gives me an IP on 192.168.2.0/24, even though the ath0.1 interface is configured up on 10.0.0.0/24 (IP 10.0.0.1).
That seems about near impossible. did you do a reboot after you got it set correctly?
most times a reboot will sort things out when adding or deleting multiple networks.
Also I would change the 3600 for the ath0.1 lease time to something like 720 (12 hrs). The dd-wrt 3600 default has been kinda stupid for long time now.
After doing a factory reset, and following the guide verbatim once more, it now for whatever reason appears to give me an IP. But it gives me an IP on 192.168.2.0/24, even though the ath0.1 interface is configured up on 10.0.0.0/24 (IP 10.0.0.1).
That seems about near impossible. did you do a reboot after you got it set correctly?
most times a reboot will sort things out when adding or deleting multiple networks.
Also I would change the 3600 for the ath0.1 lease time to something like 720 (12 hrs). The dd-wrt 3600 default has been kinda stupid for long time now.
Yes, I also rebooted.
Now I have it working, although the only thing I've changed since my previous efforts is basically factory reset and some reboots.
However, what doesn't work is "Net Isolation".
Regardless of having "Net Isolation" enabled or not I can still reach my LAN (192.168.1.0/24) from the guest network (192.168.2.0/24).
If I switch from having my guest network on 192.168.2.0/24 to 10.0.0.0/24, I can still reach my LAN, even with Net Isolation enabled. However, when I perform this switch (from 192.168.2.0/24 to 10.0.0.0/24) I can no longer reach the Internet.
