| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 679 | RackTables | 802.1Q VLANs | public | 2012-11-26 10:30 | 2012-12-01 15:12 |
| Reporter | xoggy | Assigned To | infrastation | ||
| Priority | low | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | MacBook Pro Retina | OS | Mac OS X | OS Version | 10.8.2 |
| Product Version | 0.20.1 | ||||
| Summary | 679: Not showing Tagged / Accessports right under 802.1Q ports | ||||
| Description | Even if i chose a VLAN as Native (Accessport) and have outer VLAN's tagged it will still show just a T infront of the accessport. It reads "T100+1, 10, 101" it should be "A100+T1, 10, 100, 101" See the picture. it will explain everyting i hope :) | ||||
| Tags | No tags attached. | ||||
 |
This is not a bug. An access port (A) belongs to exactly one VLAN, untagged, and is translated to the switch software as an "access" port, whether the software supports such a concept. A trunk (T) port can belong to 0 or more VLANs, of which 0 or 1 VLANs can be set as "native" (untagged) and the rest are tagged. The VLAN ID to the left of "+" is the untagged, and VLAN IDs to the right are tagged. A port is either access or trunk, not two modes at once. |
 |
Indeed you right it's not a bug its more like a tweak to make it easier to read and understand. :) You have absolutely right except the part that a port can't be two modes at the same time. It's not a problem at all to have like a VLAN Tagged and another one UnTagged on the same port, this is often used to endpoint switches to "hide" the tagged vlans if a uplink cable is unplugged and connected directly to a computer :) So it was a little mind error by me, i think that the correct way it should show up as is: A100+T1,10,101 Sorry it my mistake did some confusion :) |
|
|
Access/trunk mode is a property of a 802.1Q port, and tagged/untagged is a property of a VLAN associated with that port. These two things are related, but one does not substitute the other. The notation syntax currently implemented accurately delivers both pieces of this information, please try different VLAN configurations and see. I am closing this request. |
