NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WC7520 SSIDs with VLANs
Hi folks, I have a Netgear WC7520 that I've been using for a long time successfully both in work and home environments. The need has arisen for a couple of extra SSIDs using tagged VLANs for Gues...
Well, I've finally gotten to the bottom of the mystery and it was far simpler than I thought. The "fault" as it were was a mis-configuration of the DHCP Server on my 2x Server 2012 R2 VMs. I had all of my scopes sitting under a superscope for organisation and tidiness but it turns out that changes the behaviour of DHCP server.
After much research online I found a Superscope is used when you have multiple subnets on the same physical/logical network (i.e. no VLANs but multiple subnets). Going into DHCP, right-clicking each scope and choosing "Remove from Superscope" fixed the problem.
Thanks for all of your help!
Hi DaneA,
Thanks for your help! I had set those VLANs on the Profiles in the Controller, and just double-checked that they are both correct now when you prompted and everything is right.
I stumbled across that documentation when I was searching for answers earlier, as far as I can tell I've done everything right (Profiles set with VLAN ID, VLAN is tagged on ports going to all WAPs and the Controller).
An interesting discovery I've made tonight is that the DHCP Addresses are being handed to clients if the DHCP server is in the same VLAN as the SSID. For example, if I added a DHCP Server directly on VLAN 107, clients can receive an address. Currently, I am using a DHCP Relay so as not to multi-home the domain controller across a ridiculous number of VLANs.
The DHCP relay is working for all VLANs (about 6 or 7) on Wired devices, and VLAN 104 works on Wireless with the Relay. If it's relevant, the DHCP Relay is running on a Netgear M5300-28G.
Cheers,
dojobel.
Let us try this. Kindly set a static IP address to the wireless clients that you want to connect on the respective SSIDs of VLAN 107 and VLAN 108. Then, check if you will be able to get a reply from other devices connected within the same VLAN as well as check if you will be able to go online wirelessly.
Regards,
DaneA
NETGEAR Community Team
Hi DaneA,
It works with the static address - I can ping the gateway and other devices :)
It sure is a confusing one because I would suspect the DHCP relay on the M5300 being at fault, but Wired clients are working fine so I'm not so sure.
Cheers,
dojobel
Thanks for the update. The port on the M5300-28G switch that is directly connected to the WC7520 should be set as tagged (T) port. Kindly double-check it. Also, double-check if the port(s) on the M5300-28G switch connected to the access points are also set as tagged (T) ports.
Regards,
DaneA
NETGEAR Community Team
Hi DaneA,
I've just checked and the port is currently configured as a Trunk port and permits the VLANs 104 (Untagged), 107 (tagged), 108 (tagged). I can ping the M5300 when I use a static address so I think those might be working okay, otherwise my other option is to use a General port instead of a Trunk. Let me know what you think.
I've also moved the WC7520 to a GS748Tv4 Switch and tagged the VLANs on the ports but it doesn't seem to work there either. I'm starting to think my culprit may be the M5300 in some way - I've just tried to use a Virtual Machine attached to VLAN 107 via a Tagged VLAN and now I'm getting an IP address from the wrong VLAN (VLAN 104). Nothing is accessible though, unless I give it a static address matching VLAN 107.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
