Need help with VLAN tagging on an HP Procurve
Need help with VLAN tagging on an HP Procurve
(OP)
I have 4 vlans on a procurve switch.
VLAN1 - Network Devices (Server, printers, WAPs)
VLAN100 - Admin (Office workers)
VLAN200 - Teachers
VLAN300 - Students
There is a server doing DHCP. There are 4 ranges of IPs 1 for each VLAN.
The router is on Port 44. VLAN 1, 100, 200, 300 - Tagged
The Server is on Port 46. VLAN 1 - Untagged
The WAPs are on Ports 1, 11, 31 VLAN 1, 100, 200, 300 - Tagged
All other ports are on VLANs 100, 200 or 300 - Untagged
The WAPs all have VLANs 100, 200, 300. Each VLAN on a different SSID.
I have IP helper with the server IP on VLANs 100, 200, 300.
There are IPs from the different subnets on their respective VLANs in the switch.
The gateway for each subnet is on a different subinterface on the router.
The router is a linux box. (Untangle)
***********************************************************************************************
The WAPs are not able to talk to the server, therefore no computers on the wireless networks can get an IP.
The server can only talk to the router if I change port 44 to untagged.
What combination of tagged and untagged ports do I need to make everything talk?
Do I need to put the VLANs on the subinterfaces of the router?
VLAN1 - Network Devices (Server, printers, WAPs)
VLAN100 - Admin (Office workers)
VLAN200 - Teachers
VLAN300 - Students
There is a server doing DHCP. There are 4 ranges of IPs 1 for each VLAN.
The router is on Port 44. VLAN 1, 100, 200, 300 - Tagged
The Server is on Port 46. VLAN 1 - Untagged
The WAPs are on Ports 1, 11, 31 VLAN 1, 100, 200, 300 - Tagged
All other ports are on VLANs 100, 200 or 300 - Untagged
The WAPs all have VLANs 100, 200, 300. Each VLAN on a different SSID.
I have IP helper with the server IP on VLANs 100, 200, 300.
There are IPs from the different subnets on their respective VLANs in the switch.
The gateway for each subnet is on a different subinterface on the router.
The router is a linux box. (Untangle)
***********************************************************************************************
The WAPs are not able to talk to the server, therefore no computers on the wireless networks can get an IP.
The server can only talk to the router if I change port 44 to untagged.
What combination of tagged and untagged ports do I need to make everything talk?
Do I need to put the VLANs on the subinterfaces of the router?
Talk To Other Members
RE: Need help with VLAN tagging on an HP Procurve
Do the WAPs have an IP address in VLAN1?
Do they have VLAN1 configured as their management VLAN?
Is VLAN1 configured as untagged/native on the WAP network port? If so, configured VLAN1 as untagged on the switch.
2/ "The server can only talk to the router if I change port 44 to untagged."
So, the VLAN1 subinterface on the router is defined as "native"? If so, then the switch *also* has to have VLAN1 as untagged/native, as you have found.
3/ Wherever you have a connection, you have to make sure the two ports facing each other are configured for 802.1q (or not) and, if so, that they are configured with the same untagged/native VLAN, and the same tagged VLANs, so that those VLANs can pass over the trunk you've formed.
4/ "Do I need to put the VLANs on the subinterfaces of the router?"
Yes. Depends what router you're using, but it will look something like
int g0/0.100
encap dot1q 100
ip add 10.1.100.1
int g0/0.200
encap dot1q 200
ip add 10.1.200.1
int g0/0.300
encap dot1q 300
ip add 10.1.300.1