Mundy

IT Knowledge Base

User Tools

Site Tools


tagged_vs_untagged_ports

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
tagged_vs_untagged_ports [2018/02/26 13:58]
Dan Mundy created
tagged_vs_untagged_ports [2018/04/09 09:56] (current)
Line 19: Line 19:
 VLANs don't cross over VPNs, they are constrained to a physical network segment. VLANs don't cross over VPNs, they are constrained to a physical network segment.
 If you have a remote office, with only one internet connection, keep the phones on the same subnet as the PCs. So I guess the phone system at head office must be accessible from the data network too. If you really must have phones at remote office on separate VLAN but only have one internet connection, then you'll need an ethernet bridge, but this will cause broadcasts to cross the WAN. If you have a remote office, with only one internet connection, keep the phones on the same subnet as the PCs. So I guess the phone system at head office must be accessible from the data network too. If you really must have phones at remote office on separate VLAN but only have one internet connection, then you'll need an ethernet bridge, but this will cause broadcasts to cross the WAN.
 +
 +----
 +
 +<​blockquote>​
 +When you set a port as untagged on a VLAN, any traffic that comes in without a tag is placed on that VLAN.  So for your first example, untagged traffic would go to VLAN2.
 +
 +When you have traffic that is tagged by a device, such as  VoIP phone, or Access point, the port that is connected on must be configured to allow traffic on that VLAN.  Some switches denote this by allowing you to tag that switch on that VLAN.  If you don't do this, traffic is discarded.
 +
 +Cisco switches configured with Trunk ports will allow all VLANs unless you exclude them.  An access port only allows untagged traffic and it will go to the VLAN that you define for the port.
 +
 +http://​www.cisco.com/​c/​en/​us/​td/​docs/​switches/​datacenter/​nexus5000/​sw/​configuration/​guide/​cli/​CLIConfigurationGuide/​AccessTrunk.html
 +
 +<​cite>​[[https://​community.spiceworks.com/​topic/​1983172-trunk-vs-tagging|Trunk Vs. Tagging - Networking - Spiceworks]]</​cite>​
 +</​blockquote>​
 +
 +
tagged_vs_untagged_ports.txt · Last modified: 2018/04/09 09:56 (external edit)