Re: [44net] Why rip44d?

It doesn't populate anything unless instructed to do so. If you configure one single interface with a single IP it will accept ALL 44 traffic for encapsulation, so it creates only one single route: 44.0.0.0/8 via tunnel_if. Local routes, having bigger netmask will take precedence. The poulating of routes was needed in rip44d and ampr-ripd because the kernel IPIP tunnel device needs those routes to find out its gateways for encapsulation (this is the way to configure it for multipoint operation). So, in a simple config, you get a virtual ethernet interface from amprd having your ampr gateway address as ip, a netmask of 8 and one single route, as any interface would. All other route handling is done internally. Marius -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Mark Phillips Sent: Wednesday, August 07, 2013 05:56 To: AMPRNet working group Subject: Re: [44net] Why rip44d? (Please trim inclusions from previous messages) _______________________________________________ Are you running any kind of NOS on your Pi? As far as I can tell, the ampr daemon simply populates a non-NOS machine - or am I wrong here? Mark On Tue, Aug 6, 2013 at 10:49 PM, <sp2lob(a)tlen.pl> wrote: _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html