Re: [44net] rip44d fedora 4

Sugestion: RIP messages sent by amprgw are multicast. You should check your firewall rules so they don't block multicast traffic. -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of JJ Sent: Saturday, August 25, 2012 16:30 To: AMPRNet working group Subject: Re: [44net] rip44d fedora 4 (Please trim inclusions from previous messages) _______________________________________________ yes true, I knew that actually, just referencing port 520 as some op's might not know which port to try to forward from the router, hi, I should have been clearer...what I'm refering to is the fact that protocol 4 is not understood by most routers - I've read that cisco- based routers do however, but I can't verify that...I'm running dd-wrt on mine and it still stubbornly won't pass rip packets to my internal ip that it has assigned to me..so now I'm using an ip within the routers subnet assigned as dmz and using jnos2 which parses the ripv2 packets just fine on my persistant linux tun0. However, if I drop jnos, and run rip44d pointed at the same tun0, linux rip44d does not see any rip packets...(had to edit rip44 to change tunl0 to tun0)...so still "dead in the water", yes, waited more than 5 minutes, hi, waited 1 hour...not sure how to proceed after that... Cheers, Bald John