Non encapsulated traffic is not part of ampr networking. It usually originates from local or forwarded traffic via badly set up routes. Local traffic may be useful depending on your setup, but external non encapsulated stuff is not... The easiest way to get rid of it is to allow only IPIP packets (protocol 4) on that interface via an iptable rule: iptables -A INPUT -i interface_name ! -p ipencap -J DROP or in the forward chain if it is the case (again depending on your setup)... iptables -A FORWARD -o interface_name ! -p ipencap -J DROP Marius, YO2LOJ -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Lakenet Sent: Thursday, October 03, 2013 19:14 To: 44 Net Subject: [44net] RIP question (Please trim inclusions from previous messages) _______________________________________________ I run JNOS 2.0i with Ubuntu Linux 12.04. I am set up to receive RIP broadcasts and they are working fine. Along with the encapsulated RIP broadcast is coming non encapsulated data and JNOS is responding Unreachable Port Returned. Is this non encapsulated data something that I asked for in AmperNet registration or does it just come along or have to come along with the encap data? Jerry, N0MR _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html