for now everything look pretty good, upgrade was smooth and i found issue of my VLAN configuration. With restart routerOS was disabling my bridge port device, I was able to fix it now. Only thing I'm dealing with is the Quick Set option, with old winbox and system update I was closing the tab with O...

Thanks, sindy and everyone else for your professional support!

To summarize what was not written, the trick was to remove all VLAN interfaces except the management VLAN1110.

here I am fwyYQDQkQ2FmM1mAHHwTnq/jj5cRWLc9PFvNvkXgPu8Dq7h1KglRCQ+83tWoxDBq 5ymuqo3wma0TG2+zKtcQhHC3ZlHwy1JuYs/3rFVulCtz1Zp6BSICLn5iKf1yZiDn 2cKP3os1KArcuW8AkVaDc2qc3HD6CkGISu3sX7lJIRHBrkcUhYSv928EkYSngRw7 KWeGM7QXT2+mOW4WFHREOpXKQqqbGdvdC4ZDPNJtMdE9DcrICOQAs2X93yGU9aCZ yuVwPJ01VWI4SQXwQeHQ/AMsi6zLkQ...

I'm not afraid of hell, heaven is for wimps :) So I'll delete all VLANs, assuming that's related to external distribution. I'll change the PVID on the bridge to 1, same as on the ports. I'll set VLAN1110 to be tagged on ether1 and the bridge. Then I'll accept the lease on the VLAN1110 interface. Wha...

hi sindy, I have opened a thread here, all the details are included

viewtopic.php?p=1089400#p1089400

1500 is the base VLAN with the gateway. It is tagged on the trunk port of the physical switch before ether1, just like all other VLANs. VLAN1 is untagged and port on the switch have PVID1. Management is VLAN1110. There is nothing connected behind the CAP AX; it's just an AP with SSID that distribute...

Sorry, now I'm confused. It's clear that ether1 is the trunk. The management VLAN is 1110, the base VLAN is 1500, and the rest are just pass-through. Ether2 is not active or in the bridge at all. Config is attached

Hi, I'd like to ask if you managed to solve this problem. I know it's been a while and many things have changed, but I am now in the exact same situation with identical symptoms, except for the problematic message in the log.

I apologize for spamming with the message above; I was just confused after solving the issue with the lease for the bridge. However, after investigating and searching for what could be causing this problem, I found that the solution might be what you mentioned earlier: https://help.mikrotik.com/docs...

Now, another problem has occurred. I get the address on the bridge interface in VLAN1500, so that's fine. The problem is that I can't ping the gateway. I tried running Torch to find out where the problem is, and when I turn it on for bridgeLocal with the ICMP protocol, the ping starts working, but i...

Yes, TheCat12 is the Master! Thanks a lot, I really appreciate your help.

Bridge UP and solved. Closing

Is it even a mistake not to have an IP on the bridge interface?
Isn't it enough to have IPs on the VLANs if it works?

The only problem is with this:

No i don't, have just one and radius is managing what Vlan will be assigned. This piece of hw is Cap ax device as an one of AP's as bridge for it. As i was mentioning, vlan's are up, dhcp working, CapsMan managing SSID's and the rest is basically managed by OPNsense FW. Vlan's tagget on ether1 with ...

Got you, that could work. However, when I applied it, it didn't. The reason is simple: possibly, I didn't specify it deeply enough. I have a physical switch before it where all VLANs are tagged and VLAN1 is untagged. The RADIUS server is just forwarding requests to a Debian FreeRADIUS server, and up...

Thanks for reply, please find the file attached.

to add, vlan1500 is tagged base vlan, 1110 is management

Hello, I have a MikroTik CAP ax and I am trying to set up VLANs. The configuration with CAPsMAN running as a VM on Proxmox (10.10.0.5) works well for VLAN 1110 (10.10.0.201). However, I am struggling to set up bridgeLocal with tagged VLAN 1500 to receive a DHCP lease (although this is not a necessit...

Hi, i'm struggling with issue related OVPN default route. I have MT router connected to OVPN server running on Debian. MT(os7.3) interface IP is 192.168.201.6 and Debian 192.168.201.5. The connection is running properly and it's tested, so i can access OVPN's GW on 192.168.201.1 on server side. MT L...