My network is running fine. However I have a question on the different treatment of default vlan id (0 or 1) across different products for switch chip VLAN implementation.
On the HAPAC2, this is the setting: (I assume with the port default vlan empty, it defaults to 1)
On the Powerbox, the default port vlan is 0 (which I assumed to be treated the same as 1). However, if I don’t add “vlan=0” in the switch vlan table, when I enable “VLAN Mode = Secure” for the uplink port, the winbox connection to the switch cuts. Now I am thinking MT treats vl 0 and 1 differently (whereas I previously assumed they are treated the same way). For trunk ports, should I:
Set the default vlan id on the HAPAC2’s ports to 0 and add VL=0 to the vlan table? or instead
Set the default vlan id on the Powerbox’s ports to 1?
More info:
On the main MT router, trunk ports on the bridge come with default port vl-id=1 (thus I assumed MT’s native vlan-id is 1 for trunk port default untagged traffic). Now after introducing the powerbox to the network, I am not so sure.
That’s clear enough. Does that mean that Mikrotik’s VLAN-on-the-Bridge implementation treats Native VLAN as 1 (as the pvid defaults to 1 on the bridge ports), as well as HAPAC2’s switch chip (Atheros8327).
BUT the Powerbox VLAN-on-switch-chip with the Atheros8227 (if not mistaken) treats Native VLAN as 0?
Sorry dont use powerbox, but RoS is RoS and the same so vlan1 is the default pvid and normally is never removed or changed for vlan filtering or bridge ports.
The only time one defines a PVID on a bridge port (access port) is when that port is going to a dumb device.
Typically no one uses vlan1 or vlan0 for any vlans (they should be avoided).
RoS is the same but unfortunately the variety of switch chip used seem to be the fly in the ointment so to speak. I am out of spare Powerboxes and HAPAC2s to test but my feeling is HAPAC2’s switch chip native pvid is 1 whereas Powerbox’s switch chip native pvid is 0.
Vlans implemented on the bridge has a native pvid of 1 as well.