Jean Christophe Andr? wrote: >> vuhung at a-True-OS-Shell$tracert yahoo.com <http://yahoo.com> > Ahem... "tracert" is a Windows command... ;-) > >> 1 1 ms 1 ms <1 ms 192.168.1.1 >> 2 * 38 ms 37 ms 192.168.255.17 >> 3 38 ms 38 ms 38 ms 210.245.0.97 > Mhhh... Why do you have two level of NAT? > Check your public IP address in your modem please. > Is it one of some private network (see RFC 1918) ? > If so, you'll need to do port redirection at the 2nd level too!
That's what FPT offers ADSL customers these days. It wasn't like that just a month or two ago. Look at this: thaolx at hp6730s:~$ traceroute google.com traceroute to google.com (74.125.67.100), 30 hops max, 40 byte packets 1 gw (192.168.1.1) 2.148 ms 2.899 ms 3.519 ms 2 192.168.255.17 (192.168.255.17) 674.503 ms 674.469 ms 674.433 ms 3 210.245.0.97 (210.245.0.97) 674.397 ms 674.359 ms 674.324 ms 4 210.245.1.13 (210.245.1.13) 688.687 ms 688.651 ms 689.257 ms 5 74.125.51.153 (74.125.51.153) 778.481 ms 778.446 ms 778.357 ms 6 64.233.175.209 (64.233.175.209) 724.247 ms 722.554 ms 775.250 ms 7 209.85.249.236 (209.85.249.236) 777.380 ms 610.186 ms 634.845 ms 8 216.239.43.212 (216.239.43.212) 780.326 ms 780.300 ms 209.85.248.131 (209.85.248.131) 963.266 ms 9 * * * 10 * * 72.14.239.90 (72.14.239.90) 1131.757 ms 11 209.85.254.247 (209.85.254.247) 1033.819 ms * 209.85.254.249 (209.85.254.249) 1061.115 ms 12 * * 209.85.255.194 (209.85.255.194) 423.495 ms 13 209.85.255.194 (209.85.255.194) 425.273 ms 209.85.255.198 (209.85.255.198) 426.507 ms 427.179 ms 14 gw-in-f100.google.com (74.125.67.100) 854.510 ms 886.456 ms 886.422 ms thaolx at hp6730s:~$ And this: thaolx at hp6730s:~$ traceroute 5c.homeip.net traceroute to 5c.homeip.net (58.187.128.37), 30 hops max, 40 byte packets 1 gw (192.168.1.1) 4.708 ms 5.449 ms 5.991 ms thaolx at hp6730s:~$ Note 5c.homeip.net is the dynamic name I use for the wan interface on my modem. Even though the wan interface has a public address, the next hop is a private address. As for the port-forwading problem, I have it too. I used port-forward for my torrent client but it has stopped working. I think it has something to do with this new addressing scheme but haven't had time to dig futher.
