Guest network pro issue 3006.102.5

[78whisky]

Is there something I ned to do to fix the following.

I installed the latest firmware 3006.102.5 on my ax86u pro la couple of days ago. Installed new firmware, factory reset and hard reset with wps button on router. I am having problems with the guest networks and some devices disconnecting, the main one being a wiser heat hub.

I can connect the wiser heat hub to the routers main 2.4g network and it works fine, as soon as I create a vlan guest network, VPN network within the guest network pro I loose connection.

So currently I need to have any networks in the guest network pro disabled to be able to connect to the wiser heat hub.

I have been looking at the logs and it seems to loop through dhcpdiscover, dhcprequest,

I been trying to dix over the last few days and just summarised what info I put into gpt below.

“Wiser Heat Hub is stuck in a DHCP loop — the router keeps sending DHCP offers, but the hub never sends a DHCP request to complete the handshake. It associates to Wi-Fi (2.4GHz), but fails to get an IP. This only happens when Guest Network Pro or VLANs are enabled; disabling them makes it connect fine. Looks like the hub can’t handle isolation or bridging issues.”

Any help would be much appreciated.

Thanks

 

[jerry6]

NOT FAMILIAR WITH THAT MODEL , BUT DO YOU HAVE SMART CONNECT ENABLED ?

 

[octopus]

Is there something I ned to do to fix the following.

I installed the latest firmware 3006.102.5 on my ax86u pro la couple of days ago. Installed new firmware, factory reset and hard reset with wps button on router. I am having problems with the guest networks and some devices disconnecting, the main one being a wiser heat hub.

I can connect the wiser heat hub to the routers main 2.4g network and it works fine, as soon as I create a vlan guest network, VPN network within the guest network pro I loose connection.

So currently I need to have any networks in the guest network pro disabled to be able to connect to the wiser heat hub.

I have been looking at the logs and it seems to loop through dhcpdiscover, dhcprequest,

I been trying to dix over the last few days and just summarised what info I put into gpt below.



Any help would be much appreciated.

Thanks

Can you remove release tag as you don't release anything.

 

[78whisky]

NOT FAMILIAR WITH THAT MODEL , BUT DO YOU HAVE SMART CONNECT ENABLED ?

No I don't have smart connect enabled, 2.4 and 5 are both separate.

 

[bbunge]

Change the WIFI encryption in the guest WIFI from WPA2-Personal to WPA/WPA2-Personal. Some older IoT clients do not like the WIFI in the 3006.102.5. I've tested the 3006.102.5 betas/release and several of my IoT clients would not connect.
As of now I have gone back, again, to Asus firmware. All my IoT clients connect with WPA2-Personal.

Edit: Dual Band SmartConnect has nothing to do with this issue. I use and recommend the use of SmartConnect. It does work!

 

[bennor]

I can connect the wiser heat hub to the routers main 2.4g network and it works fine, as soon as I create a vlan guest network, VPN network within the guest network pro I loose connection.

Just to confirm, are you loosing 2.4 Ghz Wifi to just one device or to all 2.4Ghz devices? Are you loosing that 2.4Ghz WiFi only when enabling VPN on the Guest Network Pro Profile? Are 5Ghz clients affected? Since you are creating/using VPN, have you setup rules in VPN Director? If so, what are those rules?

For what ever reason some experience issues under 3006.102.x firmware with 2.4Ghz WiFi clients. Typically it revolves around certain IoT devices being unable to connect to the 2.4Ghz band. Standard troubleshooting steps for the 2.4Ghz WiFi band:

• Set Channel bandwidth to 20 Mhz
• Set Control Channel to 1, 6 or 11
• Set Authentication Method to WPA 2-Personal (quite a few IoT devices do not support WPA 3 or WPA2/WPA3-Personal)
• Check the IoT device to ensure it supports AES (some IoT devices support TKIP only)
• In some rare instances Smart Connect may cause an issue, disable Smart Connect and use unique SSID's for each WiFi band and avoid using special characters for both the SSID and WiFi password
• On the IoT device, forget all saved SSID/passwords and make a new connection (this may involve accessing the online portal for the IoT device and deleting any saved SSID connections and passwords)
• Reboot the router (for what ever reason sometimes the RT-AX86U Pro's 2.4 Ghz WiFi band has issues and 2.4 Ghz WiFi clients cannot reconnect, a router reboot typically fixes the issue)
• Last resort, perform a hard factory reset and manual reconfiguration (do not import a saved router.cfg file)

 

[78whisky]

Just to confirm, are you loosing 2.4 Ghz Wifi to just one device or to all 2.4Ghz devices? Are you loosing that 2.4Ghz WiFi only when enabling VPN on the Guest Network Pro Profile? Are 5Ghz clients affected? Since you are creating/using VPN, have you setup rules in VPN Director? If so, what are those rules?

For what ever reason some experience issues under 3006.102.x firmware with 2.4Ghz WiFi clients. Typically it revolves around certain IoT devices being unable to connect to the 2.4Ghz band. Standard troubleshooting steps for the 2.4Ghz WiFi band:

• Set Channel bandwidth to 20 Mhz
• Set Control Channel to 1, 6 or 11
• Set Authentication Method to WPA 2-Personal (quite a few IoT devices do not support WPA 3 or WPA2/WPA3-Personal)
• Check the IoT device to ensure it supports AES (some IoT devices support TKIP only)
• In some rare instances Smart Connect may cause an issue, disable Smart Connect and use unique SSID's for each WiFi band and avoid using special characters for both the SSID and WiFi password
• On the IoT device, forget all saved SSID/passwords and make a new connection (this may involve accessing the online portal for the IoT device and deleting any saved SSID connections and passwords)
• Reboot the router (for what ever reason sometimes the RT-AX86U Pro's 2.4 Ghz WiFi band has issues and 2.4 Ghz WiFi clients cannot reconnect, a router reboot typically fixes the issue)
• Last resort, perform a hard factory reset and manual reconfiguration (do not import a saved router.cfg file)

Thank you for your reply.

Just to confirm I have this device connected to the main 2.4g network and NOT the Iot, guest, vpn network (all within guest network pro).

There is one other 2.5g device affected but it's some sort of smart switch, I haven't had a chance to find out what it is, I just noticed my client list drop 2 devices each time.

5G devices are not affected.

I have a Wireguard VPN client set up with 3 devices using it, all wired, director has these devices added and told to use WGC1.

The VPN network I turn on is the pre defined VPN in guest network pro, once this is enabled the device drops. turn it off and it appears and can connect again. This is the same with guest network.

I have tried most of the troubleshooting points already but will change bandwidth, and remove a . from a password.

This is from the system log when I enable one of the guest networks, before this they are all disabled and the heat hub is connected.

Aug 6 16:58:50 dnsmasq-dhcp[17300]: DHCPREQUEST(br0) 192.168.50.203 dc:a0:d0:f3:41:3a
Aug 6 16:58:50 dnsmasq-dhcp[17300]: DHCPACK(br0) 192.168.50.203 dc:a0:d0:f3:41:3a
Aug 6 16:58:50 dnsmasq-dhcp[17300]: DHCPREQUEST(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 16:58:50 dnsmasq-dhcp[17300]: DHCPACK(br0) 192.168.50.48 fc:fe:c2:03:79:83 WiserHeat037983
Aug 6 16:58:55 roamast: ROAMING Start...
Aug 6 16:59:07 dnsmasq-dhcp[17300]: DHCPREQUEST(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 16:59:07 dnsmasq-dhcp[17300]: DHCPACK(br0) 192.168.50.48 fc:fe:c2:03:79:83 WiserHeat037983
Aug 6 16:59:40 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 16:59:40 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 16:59:45 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 16:59:45 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 16:59:54 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 16:59:54 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:00:10 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:00:10 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83

Aug 6 17:02:02 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:02:02 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:02:19 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:02:19 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:02:34 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:02:34 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:02:51 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:02:51 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:02:53 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:FE:C2:03:79:83, status: 0, reason: Unspecified reason (1), rssi:0
Aug 6 17:02:53 wlceventd: wlceventd_proc_event(685): eth6: Auth FC:FE:C2:03:79:83, status: Successful (0), rssi:-68
Aug 6 17:02:53 wlceventd: wlceventd_proc_event(722): eth6: Assoc FC:FE:C2:03:79:83, status: Successful (0), rssi:-68
Aug 6 17:02:54 hostapd: eth6: STA fc:fe:c2:03:79:83 IEEE 802.11: associated
Aug 6 17:02:54 hostapd: eth6: STA fc:fe:c2:03:79:83 RADIUS: starting accounting session BB0C9E8AEE33CEF3
Aug 6 17:02:54 hostapd: eth6: STA fc:fe:c2:03:79:83 WPA: pairwise key handshake completed (RSN)
Aug 6 17:02:55 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:02:55 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:03:00 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:03:00 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:03:08 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:03:08 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:03:24 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:03:24 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:03:41 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:03:41 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:03:55 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:FE:C2:03:79:83, status: 0, reason: Unspecified reason (1), rssi:-68
Aug 6 17:03:55 wlceventd: wlceventd_proc_event(685): eth6: Auth FC:FE:C2:03:79:83, status: Successful (0), rssi:-68
Aug 6 17:03:55 hostapd: eth6: STA fc:fe:c2:03:79:83 IEEE 802.11: associated
Aug 6 17:03:55 wlceventd: wlceventd_proc_event(722): eth6: Assoc FC:FE:C2:03:79:83, status: Successful (0), rssi:-68
Aug 6 17:03:55 hostapd: eth6: STA fc:fe:c2:03:79:83 RADIUS: starting accounting session BB0C9E8AEE33CEF3
Aug 6 17:03:55 hostapd: eth6: STA fc:fe:c2:03:79:83 WPA: pairwise key handshake completed (RSN)
Aug 6 17:03:57 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83

Aug 6 17:05:13 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:05:13 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:05:29 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:05:29 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:05:44 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:05:44 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:06:01 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:06:01 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:06:16 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:06:16 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:06:32 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:06:32 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:06:49 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:06:49 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:07:04 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:07:04 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:07:21 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:07:21 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:07:36 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:07:36 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:07:54 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:FE:C2:03:79:83, status: 0, reason: Unspecified reason (1), rssi:0
Aug 6 17:07:54 wlceventd: wlceventd_proc_event(685): eth6: Auth FC:FE:C2:03:79:83, status: Successful (0), rssi:-66
Aug 6 17:07:54 wlceventd: wlceventd_proc_event(722): eth6: Assoc FC:FE:C2:03:79:83, status: Successful (0), rssi:-66
Aug 6 17:07:54 hostapd: eth6: STA fc:fe:c2:03:79:83 IEEE 802.11: associated
Aug 6 17:07:54 hostapd: eth6: STA fc:fe:c2:03:79:83 RADIUS: starting accounting session BB0C9E8AEE33CEF3
Aug 6 17:07:54 hostapd: eth6: STA fc:fe:c2:03:79:83 WPA: pairwise key handshake completed (RSN)
Aug 6 17:07:56 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:07:56 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83
Aug 6 17:08:00 dnsmasq-dhcp[17300]: DHCPDISCOVER(br0) fc:fe:c2:03:79:83
Aug 6 17:08:00 dnsmasq-dhcp[17300]: DHCPOFFER(br0) 192.168.50.48 fc:fe:c2:03:79:83

 

[78whisky]

Change the WIFI encryption in the guest WIFI from WPA2-Personal to WPA/WPA2-Personal. Some older IoT clients do not like the WIFI in the 3006.102.5. I've tested the 3006.102.5 betas/release and several of my IoT clients would not connect.
As of now I have gone back, again, to Asus firmware. All my IoT clients connect with WPA2-Personal.

Edit: Dual Band SmartConnect has nothing to do with this issue. I use and recommend the use of SmartConnect. It does work!

Thank you for your reply, it's good to know ASUS is working ok.

 

[bennor]

The VPN network I turn on is the pre defined VPN in guest network pro, once this is enabled the device drops. turn it off and it appears and can connect again. This is the same with guest network.

Maybe dump the IPTables (or the like) and see what's going on with the firewall rules at the time you enable the VPN and it triggers the WiFi client to disconnect. It might yield some clues.