NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
VLAN trunk with WAP
I'm trying to get VLANs working with my wireless access point. I have my firewall/router plugged into port 1 on the switch and have 6 VLANs setup on the firewall/router. On the switch I have VLAN 1 a...
schumaku wrote:
Kingrazor001 wrote:
schumaku wrote:
Kingrazor001 wrote:
I tried applying VLAN ID 5 to a port untagged with port 1 tagged and PVID of 5 on that port and it worked.The test port must be VLAN ID 5, Untagged, PVID 5.
The test port must be VLAN ID [2..6], Untagged, PVID [2..6] mor generic for the other VLANs.
So it looks like VLAN trunking isn't supported. If that's the case, I'd need to have one SSID per WAP to use VLANs with this switch. Right now all WAPs have all SSIDs. Guess I need a new switch.
Nope, no new switch. Just a slightly flat learning curve on VLANs, and thier troubleshooting.
I'm asking you to set-up a non-trunked port for a test system - and move this through all the VLANs required - like this we can ensure the VLAN work appropriate between the switch and the router.
Look, >95% of the issues are on the router/VLAN/IP subnet/DHCP configuration side, and not on the L2 switches. And when I read above that you have two untagged VLANs configured on a port, that's the guaranteed start into a disaster.
I have it working now. I apparently attached the VLANs on the router to the WAN port instead of the LAN port.
Kingrazor001 wrote:
schumaku wrote:
Kingrazor001 wrote:
I tried applying VLAN ID 5 to a port untagged with port 1 tagged and PVID of 5 on that port and it worked.The test port must be VLAN ID 5, Untagged, PVID 5.
The test port must be VLAN ID [2..6], Untagged, PVID [2..6] mor generic for the other VLANs.
So it looks like VLAN trunking isn't supported. If that's the case, I'd need to have one SSID per WAP to use VLANs with this switch. Right now all WAPs have all SSIDs. Guess I need a new switch.
Nope, no new switch. Just a slightly flat learning curve on VLANs, and thier troubleshooting.
I'm asking you to set-up a non-trunked port for a test system - and move this through all the VLANs required - like this we can ensure the VLAN work appropriate between the switch and the router.
Look, >95% of the issues are on the router/VLAN/IP subnet/DHCP configuration side, and not on the L2 switches. And when I read above that you have two untagged VLANs configured on a port, that's the guaranteed start into a disaster.
schumaku wrote:
Kingrazor001 wrote:
schumaku wrote:
Kingrazor001 wrote:
I tried applying VLAN ID 5 to a port untagged with port 1 tagged and PVID of 5 on that port and it worked.The test port must be VLAN ID 5, Untagged, PVID 5.
The test port must be VLAN ID [2..6], Untagged, PVID [2..6] mor generic for the other VLANs.
So it looks like VLAN trunking isn't supported. If that's the case, I'd need to have one SSID per WAP to use VLANs with this switch. Right now all WAPs have all SSIDs. Guess I need a new switch.
Nope, no new switch. Just a slightly flat learning curve on VLANs, and thier troubleshooting.
I'm asking you to set-up a non-trunked port for a test system - and move this through all the VLANs required - like this we can ensure the VLAN work appropriate between the switch and the router.
Look, >95% of the issues are on the router/VLAN/IP subnet/DHCP configuration side, and not on the L2 switches. And when I read above that you have two untagged VLANs configured on a port, that's the guaranteed start into a disaster.
I have it working now. I apparently attached the VLANs on the router to the WAN port instead of the LAN port.
Excellent find, glad you have your set-up up and running!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
