If you want an non vlan aware connection dumped into vlan60, you untag it into that vlan. Tagged ports only permit traffic into the tagged vlan when the packets are tagged into that vlan themselves. So non 802.1Q traffic goes to the untagged designation as it is "not tagged" to a specific one.
So if this port needs access to other vlans than just the one its untagged into, the nic must support 802.1Q (vlan tagging) so it can choose the additional vlans made available to it by the tagged references in the switch. With HP, a trunk is an aggregate link, such as 802.3ad LACP etc... From: paul chinnery [mailto:[email protected]] Sent: Monday, July 27, 2009 10:04 AM To: NT System Admin Issues Subject: Procurve2180 Vlan tagging I am more used to working with Cisco switches than HP so I'm not very knowledgeable with configuring vlan's on a Procurve With the HP, am I correct that when I wish to place a port into vlan60, I "tag" it? And if I want to that port to communicate with other vlans, I select those vlans and "untag" it? With Cisco, I would enable trunking on the port connected to my core switch and then on the individual ports, I would just place them into whatever vlan I wish. With the HP, it seems like each port is a trunk port when I use tagging. ________________________________ Windows Live(tm) Hotmail(r): Celebrate the moment with your favorite sports pics. Check it out.<http://www.windowslive.com/Online/Hotmail/Campaign/QuickAdd?ocid=TXT_TAGLM_WL_QA_HM_sports_photos_072009&cat=sports> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
