Linksys EA3500 running 21.02.3 and operating as dumb AP.
After following the VanTech tutorial on Youtube I still cannot establish a connection on Guest. Both interface SSIDs are visible but can successfully connect to only the existing one.
Firewall zone has Guest => WAN, reject, accept, reject.
Firewall Traffic rule: Guest DHCP: Incoming IPv4 and IPv6 from Guestzone to this device on UDP port 67. {DNS was configured during the Guest interface setup.}
Symptoms and Indications:
Guest SSID is visible to WiFi devices.
Interface has DHCP enabled with unique subnet 192.168.2.1/10 and mask 255.255.255.0.
While attempting to connect WiFi device(s) to Guest the WiFi device appears in the "Associated Stations" list under Luci's Network->Wireless page.
Devices can connect to the other/non-Guest interface on radio0 whether Guest is enabled or not.
Thought this was initially related to issue 9343 but I really don't know as it is beyond my depth.
Disabling the other/non-Guest interface yields no change in symptoms.
Reboot yields no change in symptoms.
Is this an EA3500 limitation?
Is there some conflict between this dumb AP that usually directs DHCP requests to the main router and the DHCP server that should be enabled under this Guest interface? Not sure how to check for that.
Suggested troubleshooting steps...?
Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
psherman, My novice understanding is that any given packet whose destination address is outside the local Network address range would automagically reach the WAN. Plz advise...
I think this is actually the correct ip address. The op is running this device as a dumb ap. The main router is 192.168.1.1, so it stands to reason that this dumb ap would be 192.168.1.2.
Incorporated changes and rebooted the dumb AP but to no avail. Devices still time out while trying to connect.
Given that the main router is set to only provide addresses in the range 192.168.1.2/24 could that be the source of the problem?
Otherwise, how to troubleshoot from here?
You also will want to either allow DNS (TCP + UDP port 53) into the router, or specify option 6 in the DHCP config for the advertised DNS to the guest network to be something other than the router itself (the Google DNS entries you have in the interface definition won't do anything there -- you need to set that in the DHCP config).
Plz check my understanding... because the Guest-Block-All rule appears last it has lower precedence and would not be acted upon in the case of a DHCP request because the Guest-DHCP rule would intercept the request. FWIW, omitting the Block rule had no impact on the symptoms.
"specify option 6 in the DHCP config" - I don't understand to what this refers. Can you provide mark-up of the file?
This is true, but the block rule is not necessary, or not properly specified.
It is not necessary if the desire is to block the guest network from accessing this router -- there is already input = reject in the zone's settings.
If it is intended to prevent the guest network from accessing the main LAN, the rule is improperly constructed. Instead, you want to explicitly include the destination of 192.168.1.0/24 (or is it /26 -- you mentioned that earlier) and that will prevent access.
The way the rule is currently functioning is that it will drop all connections from the guest zone, regardless of their destination (i.e. this router, the upstream network, an the internet -- all blocked).
This is the beginning of your DHCP server definition for your guest network...
You would add the following line to that stanza to advertise 8.8.8.8 (Google DNS) as the DNS server in the DHCP response.
Performed a router restore to the previous stable config to essentially start over. Next, I simply followed the info provided on OpenWRTs Guest Wi-Fi basics. With that I was able to establish connections with Hosts buuuuut the devices then have no internet connection.
Firewall config and rules for new guest interface looked correct though I did change from Guest=>wan to Guest=>lan as you suggested due to wan indicating it was "empty"
One small step forward today...
Took a different tack (a step backwards) to verify integrity of the OpenWRT's Guest Wi-Fi Basics routine {on my hardware}. Instead of applying the routine to the dumb AP I instead applied it to the main router and was pleasantly surprised to find that it worked immediately. So, I learned that there is a communication issue peculiar to either the Guest setup when on the dumb AP or between the dumb AP and the main router.
To test the latter, I turned off the radios on the main router leaving only the dumb APs radios active. Ahh, I discovered that devices can connect to the private network thru the dumb AP but then cannot reach the internet.
So, I was unaware that the real problem lay in the basic network, i.e., not a solid foundation upon which to setup the Guest network. Working on that first...
