-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
According to the rip44d startup output your system does not have a public IP, so your system is probably behind a NAT.
Unless your NAT router has been specifically configured, the 44net router in the internal LAN won't receive the IPIP packets. The specific configuration for the NAT router depends on the exact make, model and firmware of the router. In some cases a working configuration will be impossible.
You may find more information and details in this list's archives.
73 de Marc, LX1DUC
On 19/06/2013 22:15, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello,
Been curious and just wanted to give a try running rip44d...
Downloaded: https://github.com/hessu/rip44d Followed exactly procedure decribed here: http://wiki.ampr.org/index.php/Rip44d
Executed: linux~/rip44d$sudo ./rip44d -v found local address: 192.168.0.101 found local address: 44.165.2.1 found local address: 127.0.0.1 found local address: 44.165.2.2 found local address: 44.165.2.2 found local address: 44.165.2.2 found local address: 44.165.2.2 found local address: 44.165.2.2 opening UDP socket 520... entering main loop, waiting for RIPv2 datagrams
Waited more than half an hour and... nothing happend at all. According to a/m source, “Amprgw transmits the RIP routing table updates every 5 minutes” Does Amprgw still broadcasts RIPv2 info?
Best regards
Tom - sp2lob
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html