Hello!
I have just bought and configured mu Asus RT-AX86U, and I am generally happy with it!
But, there's this one thing... I want one of my devices on a guestnet for IoT devices, which should be isolated from my core network (intranet). My core network uses the "192.168.1.*" addresses, while the guest network use "192.168.101.*"
Somewhere along the lines I made the mistake to assign this deivce a manual DHCP address in the same range as the core network. This is removed since long, but it seems to still hang around as a ghost?
The troublesome device always getting it's DHCP address as "*.1.92", which is within the core network, and it's assigned the same gateway and DNS servers as the core network. If I try to ping from the core network the device is not reached, but the device manages to get online, which should be impossible should it use the given DNS servers in the core network?
I have tried to assign an IP in the guest network range (that was not allowed), I have tried to set a static IP on the device and then switch back to DHCP (no change), I have tried to reset all DHCP leases on the router via SSH (no change), and quite a few smaller changes that didn't do anything....
Don't really know what to do next...?
Any thoughts on further tests or tricks from the experts?
Rickard
I have just bought and configured mu Asus RT-AX86U, and I am generally happy with it!
But, there's this one thing... I want one of my devices on a guestnet for IoT devices, which should be isolated from my core network (intranet). My core network uses the "192.168.1.*" addresses, while the guest network use "192.168.101.*"
Somewhere along the lines I made the mistake to assign this deivce a manual DHCP address in the same range as the core network. This is removed since long, but it seems to still hang around as a ghost?
The troublesome device always getting it's DHCP address as "*.1.92", which is within the core network, and it's assigned the same gateway and DNS servers as the core network. If I try to ping from the core network the device is not reached, but the device manages to get online, which should be impossible should it use the given DNS servers in the core network?
I have tried to assign an IP in the guest network range (that was not allowed), I have tried to set a static IP on the device and then switch back to DHCP (no change), I have tried to reset all DHCP leases on the router via SSH (no change), and quite a few smaller changes that didn't do anything....
Don't really know what to do next...?
Any thoughts on further tests or tricks from the experts?
Rickard