Only maint routing table have “Connected routes”
If packet have routing mark then no “connecter routes” for him, then packet go to forward. Can i solve it?
If it’s for something simple like multi WAN where you need to exclude private networks, you can do:
/ip route rule
add action=lookup-only-in-table dst-address=10.0.0.0/8 table=main
add action=lookup-only-in-table dst-address=172.16.0.0/12 table=main
add action=lookup-only-in-table dst-address=192.168.0.0/16 table=main
No, I have local PC ip “192.168.0.2” and local router IP “192.168.0.1”
I mark routing all from 192.168.0.2 to not 192.168.0.0/24 as VPN (go to internet over vpn)
then my router have dst-nat redirect tcp\upd 53 to 192.168.0.1.
How can i send packet 192.168.0.2->192.168.0.1:53 with wouting mark VPN to router input?
Now i have workaround with second (re)mangle rule to clear routing mark for port 53, but it’s not good.
You have RouterOS v7, correct? In v6 this just works and you don’t have to do anything, because local destination always has priority. No matter what the routing mark is, if destination address is assigned to router, packets always go in input (and you have to use action=route if you want to override this behaviour). But it seems that in v7 this is no longer the case. Question is whether this change is intentional or mistake/bug.
You have RouterOS v7, correct?
yes
You can write to support and ask whether this change in v7 is bug or feature. I’m leaning towards the former, because it would be quite significant change that can break lot of things.