nostr:npub1yck44z5zqxmwpqzqs75ay6ffjdw843ng9p6mz0lzfff3fgz2djlsngujmw Straaaaange choice of wording.

And whether VLAN 1 has an actual VLAN ID value stamped into the frame header or not is imatterial to your described situation.

VLAN 1 being untagged is still logically batshit insane.

nostr:npub1yck44z5zqxmwpqzqs75ay6ffjdw843ng9p6mz0lzfff3fgz2djlsngujmw What? No.... What? Huh? WTF?

This is not how VLANs work. Do you just, refuse to aknowledge the existance of VLAN pop and push operations, AKA.... access ports?

I can't even, what on Earth are you smoking?

nostr:npub1yck44z5zqxmwpqzqs75ay6ffjdw843ng9p6mz0lzfff3fgz2djlsngujmw

For starters, it depends on which side of this ridiculous debate you happen to agree with. Some vendors say VLAN 1 is a tagged frame, with a vlan id of one on it. I agree with this stance, as does Juniper.

Other vendors consider VLAN 1 is an untagged frame. They often call this the "native VLAN." On some platforms, one is merely the default, and it can be changed.

On others, VLAN 1 is always an untagged frame.

I consider both of these to be incorrect. A VLAN is a VLAN, and requires a tag. VLAN 1 shouldn't be some special case.

The biggest offender here is Cisco. They have products that do all three of these cases. This is due to the fact that so many of Cisco's products come from aquisittions. But the effect is the same, their own catalog isn't consistent.

I honestly don't know how most other vendors go at this point, because it is just so much safer avoiding VLAN 1 entirely. I never even find out. Have numerous Calix and A10 devices on my current network, I have no idea how either treats VLAN 1.

nuintari's rules of networking 0x0c:

Never use VLAN ID 1. Vendors can't agree how it should appear on the wire.