Allowing traffic on VLAN ID (PVID) mismatched links
However, there can be instances where traffic passing between mismatched VLANs on a link is desirable. When enabled on the switch, the ignore-pvid-inconsistency command allows this behavior.
When an untagged packet enters a port, the switch attaches the Port VLAN ID (PVID) to it. When the switch receives a packet on a given port tagged with that port's PVID, it forwards the packet to...
HOME / PVID connected via switch - Automation Authority Telecom & Energy Systems
PVID connected via switch - Automation Authority Telecom & Energy Systems [PDF]
However, there can be instances where traffic passing between mismatched VLANs on a link is desirable. When enabled on the switch, the ignore-pvid-inconsistency command allows this behavior.
You set the PVID to vlan 10 on the trunk port from the peplink to the switch, and anything plugged into the switch on a port with no vlan becomes vlan 10 at the peplink.
It is a single VLAN ID associated with a port. PVIDs are used in the General port mode. Other port modes are Access, Trunk and Customer. I don''t know much about the Customer port
This article explains the concept of the PVID in our Zyxel Switches and how it affects the connectivity from your network devices and the management of the switch itself.
Background: This post provides a configuration guide to set up a VLAN-tagged and untagged port, PVID, and trunk on TP-Link switches.
When an untagged packet enters a port, the switch attaches the Port VLAN ID (PVID) to it. When the switch receives a packet on a given port tagged with that port''s PVID, it forwards the
The PVID is used for VLAN which is run untagged on the switch port - and does define the VLAN where the untagged switch incoming traffic is associated to.
The switch supports only IEEE 802.1Q trunk ports. An IEEE 802.1Q trunk port supports simultaneous tagged and untagged traffic. An IEEE 802.1Q trunk port is assigned a default port