4 Aug
2015
4 Aug
'15
7:59 p.m.
Marius,
I'm seeing odd behavior when I traceroute to you. My traffic destined
for you is encapsulated properly, but (unless I need a valid IP), the
packets seem to leave you unenscapsulated (perhaps using Masquerade
NAT???) and travel toward the Main AMPR Gateway:
- first, I verified my route
user@kb3vwg-001:~$ ip route get 44.182.0.0
44.182.0.0 via 89.122.215.236 dev tunl0 src 44.60.44.2
cache window 840
- next, that source and destination would use the proper table:
user@kb3vwg-001:~$ ip rule show
0: from all lookup local
10: from all to 192.168.0.0/16 lookup main
11: from 192.168.0.0/16 lookup main
15: from all to 44.24.221.1 lookup main
****FROM YOU*** 22: from all to 44.60.44.0/24 lookup 42 ****
43: from all to 44.24.240.0/20 lookup 43
****TO YOU***44: from all to 44.0.0.0/8 lookup 44 ***
45: from 44.0.0.0/8 lookup 44
4400: from 44.60.44.0/24 lookup 40
7777: from all to 44.0.0.0/8 lookup 7777
7778: from 44.0.0.0/8 lookup 7777
32766: from all lookup main
32767: from all lookup default
- 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
8 tge2-6.fr4.lga.llnw.net (69.28.189.49) 261.977 ms 260.528 ms
269.815 ms
9 tge1-2.fr4.ord.llnw.net (69.28.172.198) 287.947 ms 288.808 ms
285.129 ms
10 tge1-3.fr4.sjc.llnw.net (69.28.172.77) 345.404 ms 346.292 ms
329.787 ms
11 paix-px1--limelight-10ge.cenic.net (198.32.251.193) 335.805 ms
327.859 ms *
12 dc-lax-agg6--svl-agg4-100ge.cenic.net (137.164.11.0) 338.919 ms
dc-svl-agg4--paix-px1-10g.cenic.net (137.164.47.21) 326.279 ms 332.317 ms
13 dc-riv-agg4--lax-agg6-100ge.cenic.net (137.164.11.3) 337.663 ms
dc-lax-agg6--svl-agg4-100ge.cenic.net (137.164.11.0) 340.068 ms
dc-riv-agg4--lax-agg6-100ge.cenic.net (137.164.11.3) 344.378 ms
14 dc-sdg-agg4--riv-agg4-10ge-2.cenic.net (137.164.47.15) 345.599 ms
dc-riv-agg4--lax-agg6-100ge.cenic.net (137.164.11.3) 344.061 ms
dc-sdg-agg4--riv-agg4-10ge.cenic.net (137.164.47.111) 344.344 ms
15 dc-sdg-agg4--riv-agg4-10ge-2.cenic.net (137.164.47.15) 352.518 ms
dc-sdg-agg4--riv-agg4-10ge.cenic.net (137.164.47.111) 344.658 ms
352.857 ms
16 nodem-core--mx0-30ge.ucsd.edu (132.239.254.163) 339.536 ms
dc-ucsd-1--sdg-agg4.cenic.net (137.164.23.54) 347.626 ms
nodem-core--mx0-30ge.ucsd.edu (132.239.254.163) 341.363 ms
17 nodem-core--mx0-30ge.ucsd.edu (132.239.254.163) 414.562 ms
ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu
(132.239.255.131) 345.084 ms nodem-core--mx0-30ge.ucsd.edu
(132.239.254.163) 387.159 ms
18 ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu
(132.239.255.131) 350.108 ms 347.151 ms amprgw.sysnet.ucsd.edu
(169.228.66.251) 348.789 ms
19 amprgw.sysnet.ucsd.edu (169.228.66.251) 342.078 ms 341.454 ms *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
It appears the traffic is entering your device, and then travling onward
to the Main AMPR Gateway. I verified the traffic is encapsulated, by
using Wireshark to monitor the line.
- Lynwood
KB3VWG