Not that I understand much of the VLANs and mangle and firewall filter rules you have, but generally speaking, it seems that your configuration (from 18-05-2025) is what I would call “a bloody mess of inconsistent and illogical names/comments, capable of confusing any reader, including you” 
Examples:
The bridge is called “lan”. ← it is a bridge, call it “bridge” or “bridge1” or “br-main” or “pontevecchio” 
but don’t use a different case (same) name as an interface-list (LAN).
ether14 has comment “Budh” BUT there is actually a bonding (what for?) of SFP1 and SFP2 with comment AND name “budh”
Names should be UNIQUE (and when possible self-explaining) comments should be either omitted (if unnecessary) or actually useful.
Interfaces are added to interface-lists in an order that can only come out as the result of dice throwing. 
There are quite a few entries that look like non-sequiturs or remnants of previous experiments.
Don’t be shy, if you have a VLAN 105, call it 105, NOT VLAN 5 (105)!
You have to understand that the simpler, more linear and ordered a configuration is, the easier it is to understand it BOTH for a stranger on an internet forum AND for the future you, that in three to six months time won’t be anymore capable of understanding why you made this (or that) setting.
Maybe useful, maybe not, try using my parser (shameless plug 
):
http://forum.mikrotik.com/t/configuration-parser-spreadsheet/183922/1
http://forum.mikrotik.com/t/configuration-parser-spreadsheet/183922/1
if you get the hang of it, it is very handy to highlight this kind of mix-ups.
Since - set aside my occasional grumpiness - I am after all a good guy at heart, find attached a copy of the spreadsheet with your configuration loaded and a couple of *_check sheets added, but it is only a base for you to experiment with.
Config_Parser_Alpha_4_Aankhen.zip (207 KB)