25 Jul
2015
25 Jul
'15
11:04 p.m.
Steve,
I already tried that, actually I think it is in the script you sent me.
Anyway....
root@stimpy:~# ip tunnel change ttl 64 mode ipip tunl0
root@stimpy:~# traceroute 44.88.0.9
traceroute to 44.88.0.9 (44.88.0.9), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
now here is to you... no problem at all.
root@stimpy:~# traceroute 44.92.21.35
traceroute to 44.92.21.35 (44.92.21.35), 30 hops max, 60 byte packets
1 hsmm-gw.kb9mwr.ampr.org (44.92.21.1) 59.777 ms 65.366 ms 65.341 ms
2 kb9mwr.ampr.org (44.92.21.35) 65.361 ms 65.359 ms 65.352 ms
Corey N3FE
On Sat, Jul 25, 2015 at 10:55 PM, Steve L <kb9mwr(a)gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Corey,
I get ping replies from 44.88.0.9
To traceroute over a tunnel, you may have to change the TTL to 64 like so:
This is from my gateway, 44.92.21.1
root@ampr-gw:~# ip tunnel change ttl 64 mode ipip tunl0
root@ampr-gw:~# traceroute 44.88.0.9
traceroute to 44.88.0.9 (44.88.0.9), 30 hops max, 60 byte packets
1 gw.ct.ampr.org (44.88.0.1) 62.346 ms 68.416 ms 68.897 ms
2 n1uro.ampr.org (44.88.0.9) 71.669 ms 72.287 ms 72.554 ms
root@ampr-gw:~# ip route show table 44 | grep 44.88.0
44.88.0.0/27 via 76.28.121.159 dev tunl0 proto 44 onlink window 840
44.88.0.2 via 76.28.121.159 dev tunl0 proto 44 onlink window 840
44.88.0.192/29 via 76.28.121.159 dev tunl0 proto 44 onlink window 840
44.88.0.200 via 66.162.28.8 dev tunl0 proto 44 onlink window 840
44.88.0.201 via 66.162.28.8 dev tunl0 proto 44 onlink window 840
If I remember correctly N1URO uses the munge method, and exactly how
he has that configured is best to leave to him explain.
Steve, KB9MWR
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net