This has nothing to do with port 520. The rip packages are encapsulated in proto 4 ip frames. They pass right through and are decapsulated in the tunnel driver on the machine which hosts your tunnel endpoint. So from the routers point of view, there are only IP proto 4 frames which have to pass through, no port 520 RIP traffic. They emerge only at the tunnel interface from where rip44d has to process them, where they are indeed port 520 UDP frames. Not before that.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of JJ Sent: Saturday, August 25, 2012 09:41 To: 44net@hamradio.ucsd.edu Subject: Re: [44net] rip44d fedora 4
(Please trim inclusions from previous messages) _______________________________________________ On 08/25/2012 01:54 AM, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________
Same problem for me on mint 12 and mint 13...no luck at all and I've spent
6 hours trying..I do know that most commercial routers don't pass rip packets but i've put my system direct in the dmz still to no avail, however it works right away in jnos2...
John
Routers have to pass IPIP traffic (proto 4), the RIP annoncements arrive via tunnel interface from amprgw, not directly.
Marius
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
yes, but do the routers understand ipip port 520 udp?
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net