VLANs and Tomato Wifi
-
@parry Windows 7 uses the DNS server that is entered, but changes it if I select a different subnet. Debian 8 (OK I know that is ancient) also looks for the DNS server irrespective of what is set. It seems that OS X will search for a DNS server if you dont enter one manually and in fact if you remove the one installed manually it will find the DNS server appropriate to your network. BUT if you enter a DNS server manually into the WiFi client it appears to hang around.
-
Yeah, that would explain what you're seeing.
That seems like unexpected behaviour unless perhaps you move the access point from the LAN to VLAN3? In that case the SSID and MAC of the access point would remain the same so it might see the connection as the same.
The MAC of the DHCP server would change though which would cause Windows to see it as a different network.Steve
-
@parry For the future - just leave the DNS in Tomato set to 0.0.0.0 which it uses as a default. The DHCP server in pfsense provides the access to DNS
