As much As I understand Marius refer o it in his script
"
To get internet traffic from ucsd-gw into the main routing table and ensure reply via ucsd-gw, # some mangle rules and one route are needed. # We will use connection mark "c-44net" and routing mark "44net": # /ip firewall mangle # add action=mark-connection chain=prerouting comment="Mark incoming Inet to AMPR" \ # in-interface=ucsd-gw new-connection-mark=c-44net passthrough=yes # add action=mark-routing chain=prerouting comment="Mark connection Inet to AMPR" \ # in-interface=ucsd-gw new-routing-mark=main passthrough=no # add action=mark-routing chain=prerouting comment="Mark replies AMPR to Inet" \ # connection-mark=c-44net new-routing-mark=44net passthrough=no # /ip route # add comment="Default UCSD reply route" distance=250 gateway=ucsd-gw routing-mark=44net #"
________________________________ From: 44Net 44net-bounces+ronenp=hotmail.com@hamradio.ucsd.edu on behalf of Rob Janssen pe1chl@amsat.org Sent: Monday, September 26, 2016 11:29 AM To: 44net@hamradio.ucsd.edu Subject: Re: [44net] Fwd: MicroTik and Dumb Questions
(Please trim inclusions from previous messages) _______________________________________________
You need to use mangle rules in firewall to mark the incoming packets from the gateway interface and then using route marking route them back out the way they came.
That is another approach, but you will have to handle outgoing connections as well.
Rob _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net