×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Need help with VLAN tagging on an HP Procurve

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?

RE: Need help with VLAN tagging on an HP Procurve

1/ "The WAPs are not able to talk to the server"

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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close