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
-----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
Hello Marc,
Many thanks for your valuable prompt reply. I have public address 87.251.250.110 but I'm running my Raspberry PI server intentionally behind my own router TP Link TL-MR3420. You may try, for instance, to telnet on ports 3600, 6300 and 7300. Also on my 44.165.2.2 address, as I'm included in encap.txt file.
route addprivate 44.165.2/29 encap 87.251.250.110
And yes, of course your answer is simply selfexplanatory. I haven't took this into consideration, thus once more thank you.
If I understand it corectly, if I'll run rip44d procedure from my desktop PC (without router!) then I should succeed, am I right? Google's my friend, but anyway, I better dig into archive of the list!
Best regards.
Tom - sp2lob
-----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:
I just put my box in dmz zone from router and the rip packets come in fine then...tried fwding, no luck, dmz was only option with mine...
Hello JJ,
Well, will try dmz as well, on the nearest occasion.
Many thanks. Tom - sp2lob
On 13-06-19 06:27 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello JJ,
Well, will try dmz as well, on the nearest occasion.
Many thanks. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
Yes, I loaded DD-WRT on my wrt54gs thinking that I could just forward port 520 rip packets, but no matter how I tried, no way would the packets arrive on my linux box 192.x.x.x unless I assigned the linux box a static 192 ip, then put it in DMZ, hi... GL, de John
Hello JJ,
Once more , MANY THANKS for your suggestion! This amazingly did the trick for me, indeed!
I shut down my previous routing and then run rip44d. Additionally opened port 520 in the router, just in case... And I have it working!!!
BTW, what time is in your place now?
Best regards. Tom - sp2lob
On 13-06-19 07:12 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello JJ,
Once more , MANY THANKS for your suggestion! This amazingly did the trick for me, indeed!
I shut down my previous routing and then run rip44d. Additionally opened port 520 in the router, just in case... And I have it working!!!
BTW, what time is in your place now?
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
it is 7:16 PM AST here ...lovely sunny evening if it weren't for the blackflies, hi...hay, glad you have rip going... :-)
-
jj -
Marc, LX1DUC -
sp2lob＠tlen.pl