Hi Marius,
I understand that I'll have to make an ipip tunnel to all of the other gateways (as listed in the encap file). I was under the impression that for non-44net traffic in and out, a tunnel to amprgw was used. There is no 44.0.0.1 entry in the encap file, though, so I'm beginning to wonder if I really am misunderstanding.
Thanks for your reply.
On Wed, Jan 29, 2014 at 11:12 PM, Marius Petrescu marius@yo2loj.ro wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hi Ryan,
Unfortunately, ampr doesn't work this way. You need an ipip interface with a direct connection to every gw from the encap file. Your set-up will encap all traffic to ampr hosts and send it to amprgw which is not what you want.
That is what the mentioned scrip accomplishes.
Marius,YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Ryan Elliott Turner Sent: Thursday, January 30, 2014 04:27 To: 44net@hamradio.ucsd.edu Subject: [44net] Getting mikrotik router gateway connected to amprgw
...
/interface ipip add local-address=99.173.137.24 name=ampr-gw remote-address=169.228.66.251 /ip route add distance=1 dst-address=44.0.0.0/8 gateway=ampr-gw
....
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net