It is my understanding that when I configure an access port of a specific vlan, I do the following
create a bridge
add port into bridge
define PVID in the bridge port to by my access vlan
create a vlan inside the bridge and list the port as untagged.
This means anything going out on that port on the specified vlan goes out untagged
anything coming in untagged on that port, gets into the vlan noted with PVID.
Today I connected another “dumb” old switch on such an access port and a few hosts behind it. These hosts should only be in my vlan 527. I have set up a DHCP server on the vlan 527 but the hosts dont get IP’s. When I define the DHCP server on the bridge port instead , they get ips but they can not talk to hosts on vlan 527.
So obviously something is missing.
Depends on the series switch how its configured. CRS1xx,2xx are configured differently from the CRS3xx,5xx. Check out this section of the documentation.
Linux host is connected on a brocade switch (which has no vlan config whatsoever) which is on port ether7-brocade.
Linux host has IP 10.134.235.14 it can not ping 10.134.235.7 with above config
If I move subnet 10.134.235.0/24 out of vlan527 to default vlan 1 all works but thats not the idea
thats what Mikrotik does when you type /export.
The ports where configured with th web gui. so this is not the problem.
The only thing I see different the doc is that they use admit-untagged-only on the bridge port. So it would drop any tagged packets coming in. But as there is nothing like this coming in anyway, it should not matter.
Clearly there are no issues because you know the relevant area of problem. You should thus be able to solve it yourself…
If you dont post the entire config we could be missing some related issues, an MT config is not all isolated…
Well then if you can’t figure it out neither, it must be a bug.
If such simple switching doesn’t work as documented, it doesn’t make any sense to use Mikrotik switches. Layer2 hell as usual.
No you must be eating st bernard food, I said, you need to provide the complete config to often determine the source of issues…
I dont have enough information to make a determination as I dont guess…
You have to enable vlan-filtering on bridge0. Without it, none of vlan config starts to work - including vlan tagging/untagging on access/hybrid ports …