aex.perez
Very Senior Member
Not new to Merlin, but new to 3006.102 family (both ASUS and Merlin)
Finally back on Merlin after trying a few prior release, and trying on ASUS stock firmware as well even working on this with ASUS (the feedback function, which is another mess).
Been having a problem with one specific device, getting it's IP config via DHCP that lives on the Main MLO network. Connects via Wifi 2.4 Ghz perfectly fine. But whenever I enable a Network that I created using the Guest Network profile.
As soon as I mark it active, the particular device can't get or renew it's IP address on the Main/MLO. Just see repetitive DHCPOFFER with the devices MACADDR and DHCPDISCOVER with the same MACADDR and the IP address that gets assigned in the log. It connects fine to the Main MLO based Network and gets an IP as soon as the Guest Network is turned off.
I would think under normal circumstances, the Guest Network having a different VLAN should have no impact. I have created it from scratch several times trying to be a vanilla as possible, basically only have a different SSID and Network Password the rest is pretty much default. Where should I look? If it was multiple devices failing that's one thing. It is a singular IoT device but that shouldn't matter as it does not use the Guest network, connects to the Main just fine, and gets an IP as long as the Guest is inactive.
This happens regardless if it's Merlin (so not a Merlin issue) or Stock. Have tried previous versions of both, even Reset and configing from scratch (NOT recovering a saved config). But now that I'm back on Merlin I have a lot more visibility, I just need some suggestions on what/whare to look for anything that could cause this?
Finally back on Merlin after trying a few prior release, and trying on ASUS stock firmware as well even working on this with ASUS (the feedback function, which is another mess).
Been having a problem with one specific device, getting it's IP config via DHCP that lives on the Main MLO network. Connects via Wifi 2.4 Ghz perfectly fine. But whenever I enable a Network that I created using the Guest Network profile.
As soon as I mark it active, the particular device can't get or renew it's IP address on the Main/MLO. Just see repetitive DHCPOFFER with the devices MACADDR and DHCPDISCOVER with the same MACADDR and the IP address that gets assigned in the log. It connects fine to the Main MLO based Network and gets an IP as soon as the Guest Network is turned off.
I would think under normal circumstances, the Guest Network having a different VLAN should have no impact. I have created it from scratch several times trying to be a vanilla as possible, basically only have a different SSID and Network Password the rest is pretty much default. Where should I look? If it was multiple devices failing that's one thing. It is a singular IoT device but that shouldn't matter as it does not use the Guest network, connects to the Main just fine, and gets an IP as long as the Guest is inactive.
This happens regardless if it's Merlin (so not a Merlin issue) or Stock. Have tried previous versions of both, even Reset and configing from scratch (NOT recovering a saved config). But now that I'm back on Merlin I have a lot more visibility, I just need some suggestions on what/whare to look for anything that could cause this?
