Subject: Re: Problems routing packets...
To: None <netbsd-help@NetBSD.org>
From: James K. Lowden <jklowden@schemamania.org>
List: netbsd-help
Date: 12/27/2007 01:01:03
Rich Neswold wrote:
> 'tcpdump' shows that the Wii tries to access an HTTPS server at
> 125.199.254.49. It also shows that trying to connect to this address
> results in an ICMP packet getting returned indicating "Destination
> Host Unreachable". It turns out that no machine in my house can ping -
> or otherwise access - 125.199.254.49. I checked the firewall logfile
> and didn't see any packets getting blocked. 'tcpdump' shows pings
> entering the household interface, but not ever leaving the pppoe
> interface.
Hmm. What about traceroute(8)? I show something quite wiierd going on
over there in Japan.
$ traceroute 125.199.254.49
traceroute to 125.199.254.49 (125.199.254.49), 64 hops max, 40 byte
packets
1 192.168.2.254 (192.168.2.254) 5.746 ms 2.298 ms 3.149 ms
2 er1.nyc1.speakeasy.net (216.254.83.1) 16.521 ms 17.092 ms 15.438 ms
3 220.ge-0-1-0.cr2.nyc1.speakeasy.net (69.17.83.201) 13.915 ms 13.875
ms 12.941 ms
4 166.90.136.33 (166.90.136.33) 15.023 ms 18.104 ms 12.870 ms
5 vlan51.csw1.newyork1.level3.net (4.68.97.30) 13.217 ms 25.245 ms
17.602 ms
6 ae-64-64.ebr4.newyork1.level3.net (4.69.134.113) 13.261 ms 14.411 ms
16.805 ms
7 ae-2.ebr4.sanjose1.level3.net (4.69.135.185) 83.027 ms 90.732 ms
89.693 ms
8 ae-94-94.csw4.sanjose1.level3.net (4.69.134.254) 93.029 ms
ae-84-84.csw3.sanjose1.level3.net (4.69.134.250) 84.435 ms
ae-94-94.csw4.sanjose1.level3.net (4.69.134.254) 83.920 m
s
9 ge-6-2-0-99.bbr1.sanjose1.level3.net (4.68.18.193) 87.571 ms 88.147
ms ge-0-3-0-69.bbr1.sanjose1.level3.net (4.68.18.1) 119.643 ms
10 so-14-0.hsa3.sanjose1.level3.net (4.68.114.154) 126.057 ms 90.477 ms
so-12-0.hsa3.sanjose1.level3.net (4.68.125.146) 88.780 ms
11 kddi-americ.hsa3.sanjose1.level3.net (4.79.58.22) 85.990 ms 87.419
ms 88.379 ms
12 pacbb001.kddnet.ad.jp (124.211.34.53) 111.116 ms 85.590 ms 88.083
ms
13 otecbb103.kddnet.ad.jp (203.181.100.193) 202.790 ms 206.042 ms
201.736 ms
14 cm-ote138.kddnet.ad.jp (124.211.33.66) 225.930 ms 220.274 ms
216.901 ms
15 125.29.26.26 (125.29.26.26) 215.739 ms 216.604 ms 215.541 ms
16 122.131.0.30 (122.131.0.30) 220.038 ms 220.779 ms 220.862 ms
17 122.131.0.13 (122.131.0.13) 210.553 ms 208.450 ms 210.744 ms
18 133.205.46.30 (133.205.46.30) 210.893 ms 208.167 ms 210.514 ms
19 133.205.46.65 (133.205.46.65) 209.890 ms 209.959 ms 208.961 ms
20 125.199.254.35 (125.199.254.35) 244.409 ms 221.284 ms *
21 125.199.254.45 (125.199.254.45) 212.350 ms 209.869 ms 209.616 ms
22 125.199.254.35 (125.199.254.35) 221.026 ms 221.784 ms 222.310 ms
23 125.199.254.45 (125.199.254.45) 209.714 ms 209.481 ms 212.388 ms
24 125.199.254.35 (125.199.254.35) 222.002 ms 220.548 ms 221.776 ms
25 125.199.254.45 (125.199.254.45) 208.817 ms 210.754 ms 211.126 ms
26 125.199.254.35 (125.199.254.35) 221.322 ms 219.987 ms 221.232 ms
27 * 125.199.254.45 (125.199.254.45) 213.167 ms 210.722 ms
28 125.199.254.35 (125.199.254.35) 222.220 ms 219.872 ms 222.027 ms
29 125.199.254.45 (125.199.254.45) 208.844 ms 211.298 ms 211.196 ms
30 125.199.254.35 (125.199.254.35) 218.836 ms 220.120 ms 220.140 ms
31 125.199.254.45 (125.199.254.45) 211.090 ms 209.731 ms 210.004 ms
32 125.199.254.35 (125.199.254.35) 221.200 ms 220.863 ms 225.141 ms
33 125.199.254.45 (125.199.254.45) 213.880 ms 208.937 ms 210.105 ms
34 125.199.254.35 (125.199.254.35) 220.227 ms 220.465 ms 223.046 ms
35 * 125.199.254.45 (125.199.254.45) 214.462 ms 212.717 ms
...
62 125.199.254.35 (125.199.254.35) 220.026 ms 221.885 ms *
63 125.199.254.45 (125.199.254.45) 213.316 ms * 215.518 ms
64 125.199.254.35 (125.199.254.35) 222.180 ms 222.451 ms 222.780 ms
ping(8) works though:
$ ping -o 125.199.254.49
PING 125.199.254.49 (125.199.254.49): 56 data bytes
64 bytes from 125.199.254.49: icmp_seq=0 ttl=238 time=213.868 ms
--- 125.199.254.49 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 213.868/213.868/213.868/0.000 ms
Your description suggests to me that your router is dropping the packets,
whether or not the log says so. If your traceroute doesn't show you
getting past your default gateway, that'd cinch it.
HTH.
--jkl