Re: [44net] New Linux Boot Scripts for Testing

Lynwood, Thank you for pointing out the issue. It allowed unknown traffic coming from ampr machines to reach the GW, which is wrong. I corrected it in the firewall rules. Anyway, this should not prevent my gw from working. As I said, you can traceroute 44.182.21.1, 44.182.21.254 or 44.182.30.1 (the later not always up). Could you please check again? Ttrace to 44.182.0.12 should die at hop 1 without forwarding. -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of lleachii(a)aol.com Sent: Tuesday, August 04, 2015 16:00 To: 44net(a)hamradio.ucsd.edu Subject: Re: [44net] New Linux Boot Scripts for Testing (...) - finally, I traceroute from my tunnel: user@kb3vwg-001:~$ traceroute 44.182.0.12 -s 44.60.44.2 traceroute to 44.182.0.12 (44.182.0.12), 30 hops max, 60 byte packets 1 * * * !*!*!*!*!* 2 89.122.214.254 (89.122.214.254) 156.075 ms 157.348 ms 158.606 ms !*!*!*!*!* 3 10.0.225.49 (10.0.225.49) 160.229 ms 161.495 ms 162.890 ms 4 10.0.245.209 (10.0.245.209) 186.365 ms 188.425 ms 191.056 ms 5 10.0.200.138 (10.0.200.138) 192.674 ms 194.866 ms 196.200 ms 6 193.231.106.82 (193.231.106.82) 197.768 ms 175.030 ms 175.328 ms 7 tge1-2.fr4.ams.llnw.net (69.28.171.54) 185.121 ms 185.355 ms 177.489 ms (...)