• February 22, 2025, 09:56:32 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Need ULTIMATE clarification of tagged and untagged ports  (Read 12392 times)

yonglu

  • Level 1 Member
  • *
  • Posts: 2
Need ULTIMATE clarification of tagged and untagged ports
« on: January 23, 2013, 06:39:49 PM »

All,

I like to make myself totally/absolutely clear about a Dlink switch's tagged and untagged ports behavior upon receiving different tagged and untagged packets. The exhaustive list is like below:

On a tagged port:

1. What happens if it receives an untagged frame? Drop it immediately?
2. What if it receives a tagged frame with the VLAN ID that this port belongs to? Take it and forward it with the VLAN ID tag I think?
3. What if it receives a tagged frame with a VLAN ID that this port does NOT belong to? Drop it immediately?

For an untagged port:

4. What happens if it receives an untagged frame? Take it and forward it?
5. What if it receives a tagged frame with the VLAN ID this port lelongs to? Take it and forward it?
6. What if it receives a tagged frame with a VLAN ID tthis port does NOT belong to? Drop it?

Also can a port be tagged port for multiple VLANs? I think so and this implements the "trunk port" in Cisco term, corrct?
can a port be untagged port for multple VLANs? Acutally the answer should be yes because I already have a switch with such config, but how does the switch decide the VLAN for an incoming untagged packet?

Thanks a lot!

Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Need ULTIMATE clarification of tagged and untagged ports
« Reply #1 on: January 24, 2013, 06:34:22 AM »

Which DLink switch are you referring too?
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

yonglu

  • Level 1 Member
  • *
  • Posts: 2
Re: Need ULTIMATE clarification of tagged and untagged ports
« Reply #2 on: January 24, 2013, 05:43:25 PM »

DGS-3120-24TC
Logged

dovydas

  • Level 1 Member
  • *
  • Posts: 1
Re: Need ULTIMATE clarification of tagged and untagged ports
« Reply #3 on: January 25, 2013, 06:52:50 AM »

I am struggling to configure vlans using D-Link and Linux LACP bonded vlan interfaces ("bond0.2"). Coming from Cisco world to D-Link terminology is a huge confusion for me.

I would like to ask exactly the same questions that user Yonglu has asked. And I have DGS-3120-24TC - exactly the same switch as Yonglu.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Need ULTIMATE clarification of tagged and untagged ports
« Reply #4 on: January 25, 2013, 07:03:52 AM »

I highly recommend phone contacting DLink support for these models and inquired about the information and terminology that you need regarding this units.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Planck

  • Level 1 Member
  • *
  • Posts: 23
Re: Need ULTIMATE clarification of tagged and untagged ports
« Reply #5 on: February 21, 2013, 01:47:24 AM »

Tagged/untagged is a function for forwarding a package. If a tag-aware switch receives a tagges packed, it will forward it with the tag. The only place it untagges it, is if you have a full untagged VLAN.
Here is what i normally do:
Vlan 1: Untagged all the way, an used for discovery and management
All other VLAN's: Tagged until end destination

If you do it like that, then you never hav these issue.

Remember if you use PVID, then all traffic on that port vil be tagged from that port and onwards!


Best regards

Mikkel Planck
www.structureit.dk
Logged