I've tried my vlan configs in the GUI but:
1) It doesn't seem to work. My choices in the menu are neither reflected by 'swconfig dev switch0 show,' nor do they appear as toggleable options in the networking menu of the GUI. (I admit maybe I was just being impatient and needed to wait for a few reboots?)
2) Unless I'm mistaken, it seems like it’s giving me the choice between either adding VLAN 1 as a tagged member of port 4 or excluding VLAN 1 from the port entirely? But what about adding VLAN1 as an native vlan? Or is it just assumed that VLAN1 will always be untagged, perhaps?
So far, only my default VLAN (VLAN 1) has been working. My other VLAN clients cannot ping their respective bridges. I believe my switch is configured properly because I can get clients from the same isolated VLAN talking to each other over the switch—just nothing to the router. Zero RX traffic on br4,br5 and br6.
I have the following for my start-up commands. Please let me know if I have any obvious mistakes.
Quote:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "1 2 3 4 5t"
swconfig dev switch0 vlan 4 set ports "4t 5t"
swconfig dev switch0 vlan 5 set ports "4t 5t"
swconfig dev switch0 vlan 6 set ports "4t 5t"
swconfig dev switch0 apply
Subsequent to these startup commands, I do get this in the GUI:
But still, no Rx traffic on any bridges besides br0. I can't ping them. I've tried using the GUI to set the addresses of the bridges, but they just reset back to 0.0.0.0/0.
If anyone read all of this, thank you so much!
(EDIT): One last thing I wanted to mention was how with this cli config it appears that all the new bridges have the same MAC address. Is that by design? I don't have a deep understanding of this stuff but for instance on my linux machine the default behavior is that new bridges get their own unique local mac addresses, which makes me wonder.
Last edited by mad_mike on Mon Dec 29, 2025 11:31; edited 6 times in total
No, there is no GUI option for this.
You only need this if you are using strange switch hardware that does not allow you to tag VLAN1 or if you have no idea how to configure VLANs.
(by the way, pretty much every €20 switch allows this)
Alternatively, you can of course also use any other VLAN than 1, then it will also work with strange hardware.
According to the specification, all VLANs 1-4094 can be tagged or untagged... _________________ Quickstart guides:
Yes it is working now. My switch is from Cisco's SG lineup. I was able to configure the trunk link in 'general 802.1Q' mode, which as ho1Aetoo pointed out does not necessarily require an untagged VLAN.
