add comment="Default Route to GPRS Router for Local Traffic" disabled=no \
distance=1 dst-address=0.0.0.0/0 gateway=192.168.1.50 routing-mark=direct \
scope=30 target-scope=10
I then have a mangle rule that marks all traffic coming in ether1 as direct (I have tried a few of these)…
The issue is, I can never get the MT to reply using this interface. If both the L2TP tunnel, and ether2 are down, you can not ping the public IP of the GSM Modem (which is configured to pass all traffic to the MT). By using torch I can see that the data is reaching the interface, but the reply is never sent back.
You have to mark incoming connections and ensure that correct routing mark is set in output chain if packets destination is router itselft. Examples can be found here: http://wiki.mikrotik.com/wiki/PCC
Thanks - I had a look… and Im pretty sure I have tried this… I would have thought in my case, this would have worked (ping been received on ether1, and reply going no where)… I see this has marking the inbound connection on ether1, and ensuring the reply goes out ether1… and would then use to_ether1 route table…
Just thought I would add to this - if I remove the route marking on the route, everything works as expected… however this then effects the other routes so isnt a solution, more an observation.
It appears that there needs to be a matching route in the default routing table… if this doesnt exisit it appears the Mikrotik doesnt go looking for Routing marks… Could someone confirm this?
As a work around, the following has got things working for me:
/interface bridge
add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes \
comment="" disabled=no forward-delay=15s l2mtu=65535 max-message-age=20s \
mtu=1500 name=NULL0 priority=0x8000 protocol-mode=none \
transmit-hold-count=6
/ip address
add address=10.255.255.9/30 broadcast=10.255.255.11 comment="IP for NULL0" disabled=no \
interface=NULL0 network=10.255.255.8
/ip route
add comment="Default Route to NULL Interface that is always avaliable - requir\
ed for routing marks to work correctly" disabled=no distance=200 \
dst-address=0.0.0.0/0 gateway=10.255.255.10 scope=30 target-scope=10