| |
I0OJJ > TCPIP 12.08.13 20:45l 59 Lines 2153 Bytes #999 (0) @ WW
BID : 17029_I0OJJ
Read: GUEST
Subj: Re^2: RIPv2 updates from 44.131.160.1
Path: IZ3LSV<IR1UAW<IQ5KG<I0OJJ
Sent: 130812/1937Z 17029@I0OJJ.ILAZ.ITA.EU $:17029_I0OJJ
From: I0OJJ@I0OJJ.ILAZ.ITA.EU
To : TCPIP@WW
Hi Matt,
>Hi Gus,
>rip44d is a Perl script written by OH7LZB, which listens
>for RIPv2 from the main AMPRNet gateway at UCSD, and
>updates the routing table with the appropriate mesh
>routes to the other IPIP gateways on AMPRNet. You can
>find more info about it here:
>http://wiki.ampr.org/index.php/Rip44d
TNX for the info about the 'rip44d' ... just tried,
it works very well on my server.
I should compile and install two CPAN libraries prior to
run the rip44d:
IO::Interface
IO::Socket::Multicast
>(The older method of doing this was to download from a UCSD
>FTP server an encap.txt file that is run throw a munging script
>to produce a list of commands that load the routing into the
>routing table)
Yes, I know. However, as nowadays, a new 'encap.txt' is released
by the new 'portal.ampr.org' suddenly as one parameter is changed
on its database: i.e., a change of a host dynamic IP address...
The 'encap.txt' format remains fully compatible without any change
for sourcing it on JNOS/TNOS servers, so not so bad.
But, as per JNOS2.0i, on January 2011, a kinda RIPv2 server
was implemented to it to accomplish that automatic routing map,
since the AMPRnet gateway system began offering RIPv2 updates
through the IPIP tunnel. I knew and apply only this last method...
>If the intent of the new 44.131.160.1 gateway advertisements
>is so it can act as a backup for the main UCSD AMPRNet
>gateway, then the rip44d script will need to be updated to
>properly handle those advertisements. To make it robust
>it should be able to handle the case well where the information
>in the 44.131.160.1 gateway may not be as up-to-date as the
>main UCSD gateway.
I don't know about the new 'ampr.org' setup, however it
appears as a new reorganization, as a follow-up of the new
'portal.ampr.org'...
However the 160router.ampr.org is belonging to portal.ampr.org
so it is impossible to be out-to-date.
The actual rip44d claims are due (I think) to the fact that
its multicasts lack of a password entry... so, by setting on
it the actual password string, the rip44d continue to run as due.
73, gus i0ojj
Read previous mail | Read next mail
| |
