Ronen,
Traceroute over IPencap should work. You may need to ensure the TTL is 64 for your encapsulated routes.
Your tunnel packets might be inheriting the TTL from some other interface like an IPV6 one.
root@ampr-gw:~# traceroute hambook.de.ampr.org traceroute to hambook.de.ampr.org (44.225.164.16), 30 hops max, 60 byte packets 1 db0fhn.as64626.de.ampr.org (44.130.60.100) 134.560 ms 141.343 ms 139.976 ms 2 hamnet.db0fhn.as64626.de.ampr.org (44.130.60.101) 141.220 ms 140.716 ms 140.461 ms 3 bb-db0fhn.db0gw-2.as64621.de.ampr.org (44.224.2.5) 151.931 ms 152.563 ms 152.748 ms 4 bb-hubwest.db0hsn.as64621.de.ampr.org (44.224.2.18) 158.393 ms 159.046 ms 158.744 ms 5 44.224.53.158 (44.224.53.158) 158.890 ms 178.360 ms 178.948 ms 6 koedsp-core.db0dsp.as64632.de.ampr.org (44.224.24.59) 203.592 ms 162.314 ms 164.085 ms 7 link-kpg-koe.db0ko.as64634.de.ampr.org (44.224.28.157) 174.770 ms 206.083 ms 207.899 ms 8 eth3-core.db0kpg.as64634.de.ampr.org (44.224.28.158) 206.909 ms 206.145 ms 205.800 ms 9 bb-db0kpg.db0ko.as64634.de.ampr.org (44.224.28.161) 205.897 ms 206.280 ms 207.114 ms 10 bb-db0kpg.db0ko.as64634.de.ampr.org (44.224.28.161) 3189.252 ms !H 3191.819 ms !H 3192.353 ms !H root@ampr-gw:~#
C:\Users\user>tracert hambook.de.ampr.org
Tracing route to hambook.de.ampr.org [44.225.164.16] over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 44.92.21.129 2 137 ms 134 ms 135 ms db0fhn.as64626.de.ampr.org [44.130.60.100] 3 135 ms 132 ms 135 ms hamnet.db0fhn.as64626.de.ampr.org [44.130.60.101] 4 147 ms 147 ms 146 ms bb-db0fhn.db0gw-2.as64621.de.ampr.org [44.224.2.5] 5 153 ms 153 ms 153 ms bb-hubwest.db0hsn.as64621.de.ampr.org [44.224.2.18] 6 175 ms 157 ms 155 ms 44.224.53.158 7 160 ms 181 ms 158 ms koedsp-core.db0dsp.as64632.de.ampr.org [44.224.24.59] 8 176 ms 159 ms 161 ms link-kpg-koe.db0ko.as64634.de.ampr.org [44.224.28.157] 9 164 ms 161 ms 162 ms eth3-core.db0kpg.as64634.de.ampr.org [44.224.28.158] 10 170 ms 168 ms 197 ms bb-db0kpg.db0ko.as64634.de.ampr.org [44.224.28.161] 11 bb-db0kpg.db0ko.as64634.de.ampr.org [44.224.28.161] reports: Destination host unreachable.
Trace complete.
C:\Users\user>
Hello Steve,
Are you connected via an IPIP tunnel? This looks like you have native 44/8 connectivity via BGP. Back to the larger conversation, an IPIP tunnel is just that, a TUNNEL and exposure to the intermediate hops to provide end to end connectivity are usually hidden. Some tunnel encapsulations have options to resolve this such as GRE - https://utcc.utoronto.ca/~cks/space/blog/tech/TranslucentGRE .
You might be able to fake this out with Hping2 though: http://inet-access.net/pipermail/list/2003-October/000575.html
For example, tracing to router.db0fhn.ampr.org (not 100% is this the correct IP to use or not but you get the idea) -- sudo hping2 -0 -H 4 -d 10 --traceroute router.db0fhn.ampr.org
HPING 141.75.245.225 (eth0 141.75.245.225): raw IP mode set, 20 headers + 10 data bytes hop=1 TTL 0 during transit from ip=69.12.138.1 name=dgw hop=2 TTL 0 during transit from ip=64.142.73.165 name=104.at-2-1-0.gw3.200p-sf.sonic.net hop=3 TTL 0 during transit from ip=70.36.211.53 name=0.ae2.gw.200p-sf.sonic.net hop=4 TTL 0 during transit from ip=208.106.96.250 name=as0.gw2.200p-sf.sonic.net hop=5 TTL 0 during transit from ip=69.12.211.117 name=0.ge-7-2-0.gw.pao1.sonic.net hop=6 TTL 0 during transit from ip=199.127.107.189 name=UNKNOWN hop=7 TTL 0 during transit from ip=65.50.198.86 name=xe0-1-0-0.core2.ash.layer42.net hop=8 TTL 0 during transit from ip=193.159.165.85 name=UNKNOWN hop=9 TTL 0 during transit from ip=62.154.49.110 name=h-ea3-i.H.DE.NET.DTAG.DE hop=10 TTL 0 during transit from ip=80.156.160.138 name=UNKNOWN hop=11 TTL 0 during transit from ip=188.1.144.221 name=cr-fra2-be12-7.x-win.dfn.de hop=12 TTL 0 during transit from ip=188.1.144.217 name=cr-erl2-be8-7.x-win.dfn.de hop=13 TTL 0 during transit from ip=188.1.144.42 name=xr-erl1-vlan50.x-win.dfn.de hop=14 TTL 0 during transit from ip=188.1.233.142 name=kr-fhnbg4.x-win.dfn.de --
--David KI6ZHD
-
David Ranch -
Steve L