IoT network with different subnet

[arsnlgunnr]

Hi all,
I created an IoT network via GNP with the separate subnet/VLAN configuartion. When connecting devices to the separate IoT network over wifi, some devices are assigned an IP with the correct subnet and others still maintained an IP belonging to the main network subnet. Is this because I'm using an unmanaged switch?

Current AI Mesh network set up:
RT-BE88U (main)
RT-BE86U x2 (nodes)
-Ethernet backhaul
-Nodes connect to main router via un-managed switch
-firmware: merlin 3006.102.7

TIA!

 

[bbunge]

Is this because I'm using an unmanaged switch?

No. It is likely that you had some of those WIFI clients connected to your main WIFI then switched them to the guest WIFI. It will take some time before the Asus Network Manager wakes up and realizes the IP's for those clients have changed. Rebooting the router may help then again it may not. The DHCP clients on the guest WIFI will get the right IP range address. Check the DHCP leases.

 

[OzarkEdge]

Hi all,
I created an IoT network via GNP with the separate subnet/VLAN configuartion. When connecting devices to the separate IoT network over wifi, some devices are assigned an IP with the correct subnet and others still maintained an IP belonging to the main network subnet. Is this because I'm using an unmanaged switch?

Current AI Mesh network set up:
RT-BE88U (main)
RT-BE86U x2 (nodes)
-Ethernet backhaul
-Nodes connect to main router via un-managed switch
-firmware: merlin 3006.102.7

TIA!

I would think that a simple switch does not affect DHCP IP address assignments.

Maybe the wireless clients are reflecting the DHCP of the network they are connecting to?

Does it work correctly with stock ASUSWRT firmware?

Does it work if you create your own custom IoT GNP instead of using the built-in IoT network?

OE

 

[jksmurf]

@bbunge has the most likely explanation.

If it doesn’t change after a main reboot, and allow it to settle for 10-15mins or so, could you please check your GNP, VLAN, AiMesh settings to confirm all 3 nodes are checked. Just to confirm the IoT network is set up to be propagated to all the nodes? Just curious really, I don't think it is the cause though.

 

[Justinh]

I had a similar issue recently where I reserved a different IP address for a device in DHCP settings but the router didn't force it on the device. I can't remember now exactly what I did, but I spent a good bit of time trying to get the device on the new address. I think it had to do with the lease time. Maybe I temporarily set the lease to be a short time?

 

[jksmurf]

I had a similar issue recently where I reserved a different IP address for a device in DHCP settings but the router didn't force it on the device. I can't remember now exactly what I did, but I spent a good bit of time trying to get the device on the new address. I think it had to do with the lease time. Maybe I temporarily set the lease to be a short time?

Possibly ... a router reboot should renew the leases so hopefully that will fix it. Easy enough to do (as long as the family are not online ... otherwise go sit in the naughty chair...)

 

[arsnlgunnr]

@jksmurf @Justinh @OzarkEdge @bbunge

Thanks all for the replies! Based on the feedback, when connecting the devices to the IoT network and they don't get the desired IP, sounds like I just need to give it some time for the IP address to be assigned properly.

I did delete and re-create the IoT network and joined 4 devices. 3 were assigned an IP in the correct subnet right away. The remaining 1 retained it's main network IP but updated after about 5-10 min to the correct subnet IP. Will continue to monitor and make sure those 4 don't hop back and forth between subnets before adding the remaining devices to the IoT network.