Re: [44net] (no subject)

The issue in your setup is 'ip route add default dev tunl0 via 169.228.66.251 onlink table 44' which should go away if ypu want to reach BGP announced networks. 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 Marius Petrescu Sent: Thursday, June 18, 2015 01:42 To: 'AMPRNet working group' Subject: Re: [44net] (no subject) (Please trim inclusions from previous messages) _______________________________________________ Steve, That's a rule directing your system to use routing table 44 for ampr purposes, not a route. It must be there, and it won't work without it. -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Steve L Sent: Thursday, June 18, 2015 00:09 To: 44net(a)hamradio.ucsd.edu Subject: [44net] (no subject) (Please trim inclusions from previous messages) _______________________________________________ That occurred to me after I sent my last message. Part of my startup script included this default route: ip rule add to 44.0.0.0/8 table 44 priority 44 So I commented that out, and then could reach hamwan.org, but wasn't able to reach hambook.de.ampr.org and other hosts. I also upgraded to ampr-ripd 1.13 If someone can reach both from their IPIP gateway I'd be most grateful if you'd share your startup script with me. Here is my script: http://www.qsl.net/kb9mwr/wapr/tcpip/startampr _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net