-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guest Wifi mixed with Main Wifi #218
Comments
Okay, I can see what the issue is. The way that they determine if the current AP is a Guest is by (stupidly) looking at the setting of ap_isolation, so when you turned off ap_isolation for the Guest network, it buggered up the setting handling. I will have to have a think and see if I can work out a way to get around it. |
I have made a change that I think has fixed it. Please give it try and let me know. You can apply the fix with these commands:
|
I am going to mark this as closed as I have just done a release. If there are any further problems, please re-open. |
Hi, thank you so much for the rapid fix! My apologies, I was working night shift so was unable to reply sooner; I've tested the latest update and can confirm this has fixed the issue of the network editing pages overlapping. Unfortunately for some reason DHCP / IP assignment doesn't seem to be working on my Guest/HomeWifiIOT network still. Devices can connect and function on the network if they manually specify a static IP/gateway, but fail to connect/be assigned an IP if trying to connect with DHCP. |
Hmm. I just set up the Guest Wi-Fi on my test DJA0230 (basically the same as a DJA0231). I named the SSID HomeWiFiIOT and turned off AP Isolation. I then connected to that SSID with my phone, and I got an IP (192.168.2.7). What does the log say when you try to connect a device? It should be something like:
I assume that you do have |
Figured it out, was (of course) user error. A couple days ago I had gone in and tried to disable a couple of Firewall User-defined Rules preventing WAN in/out on the IOT subnet. In my sleep-deprived state I stupidly accidently disabled the Guest1 Zone rule instead, just noticed that. Re-enabling it fixed the DHCP issue. Thanks for your help and sorry for the trouble. |
I am glad you sorted it out. |
This is an odd/difficult bug to explain; essentially my Guest Wifi hotspot has somehow merged with my main wifi hotspot and I cannot edit their settings individually. Concurrently; devices trying to connect to the Guest wifi hotspot have their connection fail during IP configuration.
I have a main Wifi hotspot named HomeWifi which is associated with the
lan
lan interface and addresses in subnet192.168.0.x
. It has band steering enabled.I have a guest Wifi hotspot named HomeWifiIOT which is associated with the
Guest1
lan interface and addresses in the subnet192.168.1.x
. It has band steering & 5GHz disabled.When I go to edit HomeWifiIOT in the Wifi card (e.g. change the password, etc.), the information displayed is the same as the information for HomeWifi, as demonstrated here:
HomeWifiIOT still exists as a separate hotspot that my devices can see.
If I try to edit any of HomeWifiIOT's settings, it changes settings for HomeWifi instead, and then HomeWifiIOT disappears from my devices' available networks list. After a reboot of the router, the IOT hotspot returns, but attempting to connect to it fails with IP configuration error.
Looking at the source code for the page, both HomeWifi and HomeWifiIOT lead to different AP settings:
In case it's helpful, the output of
uci show wireless
:The text was updated successfully, but these errors were encountered: