NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AX4200 Management VLAN, Static IP incompatible?
I have a few AX4200s at home. They are configured to use 3 different static IPs for their management interface. I'm running 3 explicit vlans - 1001 for management, 1002 and 1003 for different classes...
Just adding a VLAN capable switch won't magically make your consumer-routers with NAT (isolating the WAN IP from the internal LAN and IP subnetworks). Each of these routers requires it's own subnet (this is what you might be able to implement on a Plus or Smart switch). Sure, you can configure three ports on such a switch for associating each router LAN with an VLAN. and implement trunk ports to connect the WAX220, allowing dedicated SSIDs for each of these VLANs. For simplicity, I suggest to keep the primary VLAN (the LAN you have on your primary router) as an untagged VLAN, also what should serve the management (V)LAN in the future.
Which of the three routers should serve the management VLAN in the future?
Sure, if you are so desperate to run everything tagged, feel free.... However, without a VLAN-capable Plus or Smart Switch, you can't achieve what you have in mind anyway.
I use 2 SSIDs for different classes of wifi traffic, and all 3 APs annouce both SSIDs.
I'm using these as APs, not routers. I'm not even sure they can route, except for the guest network functionality, which I don't use. Note that these are WAX220 devices, not RAX43 or something like that. I guess I should have focused on the unambiguous model number, rather than the first model number.
Specifically, I expect them to only have an IP on the management VLAN, and to act as bridges between each SSID and the correct (non-management) VLAN. AFAIK, this is what they are all doing. I've seen no evidence of the APs themselves taking IPs on vlans 1002 or 1003.
They are indeed all plugged into a managed switch (MS510TXUP in particular), but for the purposes of the question, it could be unmanaged - my router is set up to deal with a trunked line, managing a subnet on each VLAN.
BGalehouse wrote:
I use 2 SSIDs for different classes of wifi traffic, and all 3 APs annouce both SSIDs.
This reads like a good plan.
BGalehouse wrote:
I'm using these as APs, not routers. I'm not even sure they can route, except for the guest network functionality, which I don't use. Note that these are WAX220 devices, not RAX43 or something like that. I guess I should have focused on the unambiguous model number, rather than the first model number.
Probably I had a reply to a different thread in my head when answering before
BGalehouse wrote:
Specifically, I expect them to only have an IP on the management VLAN, and to act as bridges between each SSID and the correct (non-management) VLAN. AFAIK, this is what they are all doing. I've seen no evidence of the APs themselves taking IPs on vlans 1002 or 1003.
Wait a moment. An access point is a bridge connecting a wireless network identified by an SSID. It's the wireless client connecting to the SSID, where your router is taking care of each subnet, over the trunk.
BGalehouse wrote:
They are indeed all plugged into a managed switch (MS510TXUP in particular), but for the purposes of the question, it could be unmanaged - my router is set up to deal with a trunked line, managing a subnet on each VLAN.
No way, this isn't enough, You must configure the VLANs on the MS510TXUP, define trunk ports for the VLANs for the link to your router, and for the link to your WAX220. And the WAX220 must be configured to map each SSID desired to a VLAN.
If done properly, your wireless clients on each SSID will get IP configs assigned accordingly.
schumaku wrote:No way, this isn't enough, You must configure the VLANs on the MS510TXUP, define trunk ports for the VLANs for the link to your router, and for the link to your WAX220. And the WAX220 must be configured to map each SSID desired to a VLAN.
If done properly, your wireless clients on each SSID will get IP configs assigned accordingly.
IP assignment is working fine. My frustration is that the APs won't let me change any wireless settings, complaining about the combination of static + VLAN management interface setup. I'll probably just go set up my dhcp server with static assignments for these mac addresses, and then the APs can be set for dhcp + VLAN, which was working earlier. I'm not sure why I didn't think of this work-around sooner. But it feels like a firmware bug, and perhaps I just needed to grumble.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
