44 Net RIP or is it R.I.P.?

Bill V WA7NWP wa7nwp at gmail.com
Tue Feb 9 12:48:28 PST 2010

Looks like it's about time for the old Carrier Pigeon to retire...


it seems that the RIP packets have now begun to appear. Sounds good. So,
by listening to them, I can update the routes instead of using the encap

I now need to see what sort of listener/daemon to install... Sounds much
better than updating through ftp once a day !

73 Guido

On Tue, Feb 9, 2010 at 12:34 PM, Bill V WA7NWP <wa7nwp at gmail.com> wrote:
> A bit of news and happenings on the 44 net.  While I still don't hold
> any real hope for the existing system, this is encouraging me  to get
> some systems on the air and start experimenting with the various
> routing procedures...
> I still think we may find the 1200 baud routing packets useful to
> convey information for disjoint tunneled high speed (WIFI or better)
> cells.
> Bill - WA7NWP
> ----------------------------------
>> On Fri, 2010-02-05 at 12:12 -0800, Brian wrote:
>> > Theoretically yes, once a method for gateways to dynamically register their
>> > addresses and subnets has been developed.
>> >
>> > Phil Karn is working on getting OpenVPN implemented on the AMPRGW
>> > for precisely that purpose.  When we had dinner a week or so ago,
>> > he mentioned he's awfully busy with work and other matters just now,
>> > so it may be a little while.  But it's being done.
>> >     - Brian
>> Hello everybody !
>> I am not getting these RIP broadcasts from UCSD. I am wondering whether
>> it is a matter of listening on the wrong port or it's just that my ISP
>> is dropping those packets...
>> I have been listening on both port 520 and 521 and there was nothing
>> coming in. Am I missing something ?
>> 73 Guido IZ6RDB
> They are sent every 5 minutes as UDP packets to port 520 to each of the
> gateway IP addresses listed in the encap file.  Currently that takes 10
> full length (24 entries) and 1 short (11 entries) packets to send.
> They're not broadcasts because broadcasts generally don't cross routers,
> and getting everyone set up to use multicast seemed like too much hassle.
> I'm troubleshooting a bug where some routes don't seem to appear.
>       - Brian

More information about the Seatcp mailing list