Let me try to explain a little what's happening here... Your system has usually 3 preexisting routing tables, 'local' (255),'main' (254) and 'default' (253). Usually, regular routes go to the table 'main', the table 'local' holds local interface IPs and broadcast routes, and the table 'default' is empty, and holds last resort routes. The specific 44 routes could go to table main, but for easier management, most OMs choos e separate routing table for those, in your case it is numer 44. For the system to use table 44 for its decision on routing ampr traffic, a rule has to be set to specify to use another table than 'main'. This is done by 'ip rule add to 44.0.0.0/8 table 44', meaning 'all packets with destination 44/8 will use table 44' So, it will hold all '44.x.x.x/n via GW_Address dev tunl0' routes. To have a specific default route for 44 packets, something like '44/8 via something' has to be added. A specific default destination via your public interface should be added to table 44 if the IP falls trough without finding any matching subnet. The stuff described up to this point, ensures IPIP tunnel and regular internet routing. To be able to accept incoming connections from the internet, another step has to be taken, usually using another table (e.g. 'default' which is empty). To understand this, remember that internet to 44/8 will come through the default UCSD tunnel (where you get your RIP broadcasts, too), from a public IP to your 44 address. Responses to these requests have to go back to the same tunnel. For this, we need a default route to ucsd in that separate table: 'ip route add default via 169.228.66.251 dev tunl0 onlink table default' And create our rule: 'ip rule add from (your ip/range) table default' combined with the next rule: 'ip rule add from (your ip/range) to 44.0.0.0/8 table 44' Take care that the rules are applied by priority, the newest added rule having precedence. So the order is important. Rules can be shown with 'ip rule list', the number shown being the priority, the lower the number, the higher the priority. This gives the following behavior: - packets to from your 44 sources to 44/8 destinations will go via table 44 (directly to peers via IPIP) - on non match they (should) go to the default public IP interface - packets to from your 44 sources to non-44/8 destinations will go via table 'default' (and to ucsd via IPIP to their internet peers) All other routing should be done in table 'main', e.g. for LAN and non 44net traffic. CAVEAT: Contrary to routes, rules get not erased when bringing down an interface, so they must be explicitly deleted or set only once on system startup. Take care if restarting the interfaces by script. I hope this explains some of the cryptic stuff. Marius, YO2LOJ -----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 ---- Quote ---- NO GATEWAY SHOULD EVER HAVE A DEFAULT 44/8 ROUTE TO UCSD BECAUSE IT DOESN'T WORK AND IS POINTLESS. Marius, YO2LOJ _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net