IoT VLAN

[ChrisAhlund]

I'm super new to this so I just wondered if I did anything wrong here... I wanted to create a secure IoT VLAN on my AX86U Pro, so I created a IoT network in Guest Network Pro via the Asus APP and disabled "use same subnet as main". I then assigned a port for my IKEA hub to the IoT network with "access mode" in the web GUI. Then I connected my phone to the IoT network and installed the rest of my smart bulds and outlets that goes on Wi-Fi. That's it?

 

[Justinh]

I then assigned a port for my IKEA hub to the IoT network with "access mode"

I don't know what this means.

Otherwise, that is it. You can look at the network details or the summary info to see that you created a VLAN.

 

[ChrisAhlund]

I don't know what this means.

Otherwise, that is it. You can look at the network details or the summary info to see that you created a VLAN.
View attachment 62642

I connected one of the LAN/ethernet ports to the IoT network. Then you can choose to set that port to either "trunk" or "access" mode and I think that access is used when you only want to control one port. Good that the setup looks alright! I'm 99% sure that I disabled "same subnet as main" when I set up the IoT, but what's the easiest way to make sure that I did so?

 

[Justinh]

Look in the "Advanced Settings" of the network. If the IP address is different from your main network, then you did indeed disable "same subnet as main". Also, if you didn't do that, the title of the network would say "(Main Subnet)".

 

[ChrisAhlund]

My main, guest and iot network have all different IP addresses so it looks good Thank you so much for your help! One last thing. I'm trying to delete these offline devices in the picture from the list, but when I restart the Asus APP they are back. I think they all are my phone... Are they some remain from when I connected my phone to my other networks to add devices? Can they be removed somehow or do they have to be there for this all to work?

 

[Justinh]

I'm not sure where you are seeing these clients. But clients tend to remain shown for a while and sometimes not show; known issue. There is a way on the CLI to clear up the list, but I'd just ignore it for now.

 

[ChrisAhlund]

It's in the devices list in the Asus APP, on top of the list that shows offline devices. Yeah I know, it's just annoying. Thanks again for the help!

 

[margentieri152]

It's in the devices list in the Asus APP, on top of the list that shows offline devices. Yeah I know, it's just annoying. Thanks again for the help!

Hey, so have you had any issues with your wired client? I recently purchased an RT-BE96U and just got it all set up with a new IoT network and VLAN as well. I'm set up exactly as you've described here. My main network is on the 192.168.50.x subnet and my IoT network is on the 192.168.52.x subnet.

All my wireless IoT clients connect to the wireless IoT network no problem; my problem lies with my wired clients. Even though I've assigned the ethernet ports those clients are connected to to my IoT VLAN in Access mode, all those wired clients are being assigned IP addresses from the main 192.168.50.x network, rather than having a 192.168.52.x IP address from the IoT network like it should, and that's preventing my wireless IoT clients from locally communicating with my wired clients. It's super frustrating.

 

[ChrisAhlund]

After some tinkering with the ports yesterday I noticed this as well, but after a restart of the router, the wired client got assigned the 52 IP address like the rest av the IoT clients.

 

[margentieri152]

After some tinkering with the ports yesterday I noticed this as well, but after a restart of the router, the wired client got assigned the 52 IP address like the rest av the IoT clients.

Lucky you. Thankfully, I was able to find a workaround. It seems this is a bug in the Asus defined IoT network, at least on the RT-BE96U. I was able to set up a Customized Network and use that as my IoT network instead, and that new IoT "Customized Network" has no problem connecting my wired clients. Nothing I did could make them connect when using the pre-defined IoT Network. Oh well, at least I got it working ¯\_(ツ)_/¯