Recent content by TD99

I was under the impression that "Guest Network = VLAN", regardless of Ethernet vs. WiFi, because when a guest network is created, so is the VLAN. Even Asus Support stated that a managed switch is REQUIRED for Guest Network/VLAN support (but I do take what they say with a grain of salt).

OK folks, I'm back again with an update. To recap (again), I originally wanted all IoT devices (Alexa, cameras, smart switches, etc.) to be on their own guest network VLAN but could never get it working with my current hardware. In the end, I was able to solve the issue and separate traffic...

I did some more testing and have some good news... well, good for me at least... To recap, I originally wanted all IoT devices (Alexa, cameras, smart switches, Govee, etc.) to be on their own guest network VLAN but could never get it working with my current hardware. In the end, I was able to...

Update on this scenario... Contacted ASUS Support moments ago, and according to them, for Guest Network Pro to work, all routers/nodes must be one of the following models: GT-AX6000, GT-BE19000, GT-BE96, GT-BE98, GT-BE98 Pro, RT-AX57 Go, RT-AX86U Pro, RT-AX88U Pro, RT-BE86U, RT-BE88U, RT-BE96U...

I was thinking, since all network traffic routes through my pfSense firewall, I set up some rules so that any wireless device (192.168.2.XXX) can only access the main Asus RT-AX86U Pro router (192.168.2.2, running in AP Mode), the physical ethernet interface port on the pfSense (192.168.2.1) and...

I have everything on a single SSID now (sucks, I know), but AiMesh is now working fine and all clients are connected with their proper DHCP addresses. Back to using my unmanaged NETGEAR GS108 switch that a Frontier tech gave me for free. Family is already on my back about the wi-fi bouncing so...

Put the RT-AX86U Pro into Router mode. Same results. Wireless devices connecting to node get a regular 192.168.10.XXX address instead of 192.168.52.XXX. My Workout Room node: Wireless devices that connect to the main RT-AX86U Pro router, get a .52 address just fine: TP-Link TL-SG108E...

Going to try that right now...

Yeah, I tried that before. I just tried it again and this is what I get:

Dang, lots of replies since my post on Friday. Just read them all. Thanks everyone for your input. I've tried everything suggested, no dice. I think you may be right. Tried that. Still no go. All wireless devices that connect with one of the two nodes still get the wrong IP (192.168.2.XXX)...

Hi all, I'm glad I found this thread, which I've thoroughly read. I've been struggling for a week and need some assistance before I lose my mind. Based on an article I recently read on Ars Technica detailing the vulnerabilities of Asus routers, I finally upgraded my RT-AX86U Pro (running in AP...

Edit: Yep. Thought this over a bit more and realized that in order for the clients to show up, they needed IPs. And since pfsense if my DHCP server, I had to first create the VLANs on pfsense and then assign them to an existing pfsense interface...

Yeah, we're on the same page. Going to stick with 3.0.0.4.388_24199 for now and will closely observe what others are experiencing in the new revs. Thanks!

Hi all, yesterday I upgraded from 3.0.0.4.388_24199 to 3.0.0.6.102_34312 in an attempt to fix a problem with some PCs/phones not being able to ping my wifi printer after a day or so -- and now both Guest Networks (one 2.4GHz and one 5GHz) no longer function correctly. My IoT devices (e.g. Kasa...