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 assigned to all ports untagged, and VLANs 2-6 assigned to port 1 and port 3 tagged. Each port has a PVID of 1. The WAP is plugged into port 3 and supports tagged VLANs for its SSIDs. When I assign an SSID a VLAN tag, clients can't connect to the WAP.
What do I need to change to configure port 3 as a trunk with all VLANs?
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.
19 Replies
Replies have been turned off for this discussion
To start with troubleshooting, configure a test port on the switch dedicated for each VLAN (samle VLAN ID and PVID) [U]ntagged and connect a computer there - it should get an IP address bc DHCP for that subnet, and be able to ping the related default gateway, and (depending on the firewall rules) reach the Internet or some internal LAN.
schumaku wrote:
To start with troubleshooting, configure a test port on the switch dedicated for each VLAN (samle VLAN ID and PVID) [U]ntagged and connect a computer there - it should get an IP address bc DHCP for that subnet, and be able to ping the related default gateway, and (depending on the firewall rules) reach the Internet or some internal LAN.
This worked. I tested by first untagging port 24 on VLAN 2 and connected a computer to it. No IP. Then I tagged that port. Still no IP. Then I changed the PVID for that port from 1 to 2 while the port was untagged. That worked and I got an IP from the correct subnet.
What I don't know though is how to configure this port as a trunk port and have multiple VLANs assigned to it, since you can only assign one PVID to each port.
Great, you started testing and experiencing - exactly what I expected.
Now there is a little error in the config - the PVID does define the VLAN untagged incoming packets are assigned to Define the test port to VLAN ID 2 [u]ntagged, and PVID 2 - and a normal computer (not VLAN aware) will work straight away.
If these test ports are fine, you can have an eye on the WAC trunk port - all the VLANs (except of the base one which you might want or have to keep untagged for the WAC administration) must be [t]agged, only the base VLAN is [u]ntagged and PVID.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
