dsa_software...aware_bridge(9)

💅 dsa_software_untag_vlan_aware_bridge(9)

okay so we're in the Kernel API Manual bestie, buckle up 🎀

---

✨ NAME ✨

dsa_software_untag_vlan_aware_bridge — literally the software untagging situation for the VLAN-aware bridge 🦋

---

🌸 SYNOPSIS 🌸

void dsa_software_untag_vlan_aware_bridge (struct sk_buff *skb , struct net_device *br , u16 vid );

no cap, that's the whole signature 💅

---

🎀 ARGUMENTS 🎀

• skb — Pointer to received socket buffer (packet). it's giving "the actual packet, bestie" ✨
• br — Pointer to bridge upper interface of ingress port. the bridge's main character interface, basically 👑
• vid — Parsed VID from packet. the VLAN ID we already fished out of the packet 🍓

---

🔥 DESCRIPTION 🔥

so here's the vibe check: the bridge can process tagged packets. but software like STP/PTP may not — they're lowkey not built for that 😭

the bridge can also process untagged packets, and it does that to the same effect as if they were tagged with the PVID of the ingress port. same energy, fr fr 💫

so! packets tagged with the PVID of the bridge port must be software-untagged, so that both use cases are supported. that's the whole point, periodt 🫶

ngl this one's short but it matters — skip the untagging and you break one of the two use cases. not iconic behaviour 💀

---

💜 SEE ALSO 💜

• Kernel file ./net/dsa/tag.h
• dsa_software_untag_vlan_unaware_bridge(9)
• dsa_software_vlan_untag(9)
• module_dsa_tag_drivers(9)
• module_dsa_tag_driver(9)

---

alright that's the page, bestie 🌈 this lil number lives over in ./net/dsa — dated October 2026 — from the Kernel API Manual. slay, go untag some packets 💖✨🎀