On Jun 18, Pete Templin wrote : : : Let me try some somewhat off-topic questions here: I really think the ISP : is clueless and not communicating the presence of our network to its : upstream provider. Could a bunch of you developers please try the : following three traceroute commands and tell me what you get? : : % traceroute 204.186.27.145
: % traceroute 204.186.230.1
: % traceroute 204.186.230.2
:
: .27.145 is the modem and the connection to the Internet via the ISP.
: .230.1 is the ethernet card in the Linux box, on the local area network.
: .230.2 is the NT server which will be our second DNS server, etc.
:
: I seem to get caught in a routing loop at fngw-T3-prolog.NEREP.NET when I
: try the second and third command, and it looks to me like that router is
: misconfigured. The ISP claims that traceroute (and ping) won't work until
: DNS is ready.
Nonsens. May be they work slower, but they work. And you can always
use ``-n'' to traceroute w/o name resolving. DNS is completely
unrelated to routing.
eremit:~ # traceroute 204.186.27.145
traceroute to 204.186.27.145 (204.186.27.145), 30 hops max, 40 byte packets
1 icm-gate.saechsisches-elbland.de (194.123.25.190) 27.195 ms 27.054 ms
26.939 ms
2 ibh-gate1.ibh.net (194.45.31.29) 50.29 ms 50.01 ms 56.963 ms 3
ibh-gate.ibh.net (194.45.31.30) 51.76 ms 51.781 ms 51.19 ms
4 chemnitz.core.xlink.net (194.120.78.133) 57.25 ms 105.558 ms 58.361 ms
5 * * *
6 karlsruhe.core.xlink.net (194.122.225.1) 98.37 ms 96.781 ms 95.653 ms
7 frankfurt.core.xlink.net (194.122.225.42) 109.917 ms 113.131 ms 108.684 ms
8 Vienna2.VA.US.EU.net (134.222.19.1) 254.898 ms 259.182 ms 239.618 ms
9 San-Jose1.CA.US.EU.net (134.222.228.106) 792.154 ms 296.204 ms 260.284 ms
10 gsl-mae-w-fddi.gsl.net (198.32.136.94) 979.068 ms * 1518.2 ms
11 gsl-stock-1-Hssi4/0.gsl.net (204.59.128.33) 1920.53 ms 329.952 ms 321.473
ms
12 gsl-sl-stock-fddi.gsl.net (204.59.128.198) 312.614 ms 403.723 ms 297.429
ms
13 sl-stk-23-P4/0/0-155M.sprintlink.net (144.232.1.26) 543.649 ms 744.718 ms
599.111 ms
14 * sl-stk-20-P4/0/0-155M.sprintlink.net (144.232.1.21) 334.649 ms 331.505 ms
15 sl-stk-21-P4/0/0-155M.sprintlink.net (144.232.1.17) 301.825 ms 321.421 ms *
16 144.232.8.57 (144.232.8.57) 283.953 ms 291.426 ms 308.99 ms
17 sl-pen-22-F5/0/0.sprintlink.net (144.228.60.22) 278.382 ms 280.623 ms
282.512 ms
18 144.232.168.2 (144.232.168.2) 300.747 ms 292.89 ms 295.388 ms
19 * * *
20 core01-abe-fe30-T3.FAST.NET (198.69.204.1) 318.931 ms 317.116 ms 312.133
ms
21 fngw-T3-prolog.NEREP.NET (205.147.225.6) 308.903 ms 336.497 ms 323.524 ms
22 gateway-s0.tv13.ptd.net (204.186.255.6) 388.148 ms 345.53 ms 356.983 ms
23 gateway-s0.mil.ptd.net (204.186.254.21) 432.429 ms 351.471 ms 493.89 ms
24 * * *
25 * * *
^C
traceroute to 204.186.230.1 (204.186.230.1), 30 hops max, 40 byte packets
1 icm-gate.saechsisches-elbland.de (194.123.25.190) 28.066 ms 31.566 ms
27.179 ms
2 ibh-gate1.ibh.net (194.45.31.29) 53.118 ms 50.551 ms 50.364 ms
3 ibh-gate.ibh.net (194.45.31.30) 58.86 ms 52.723 ms 52.477 ms
4 chemnitz.core.xlink.net (194.120.78.133) 64.676 ms 92.984 ms 98.325 ms
5 * * *
6 karlsruhe.core.xlink.net (194.122.225.1) 88.906 ms 81.939 ms 122.273 ms
7 frankfurt.core.xlink.net (194.122.225.42) 129.058 ms 115.213 ms 116.426 ms
8 Vienna2.VA.US.EU.net (134.222.19.1) 2005.84 ms 2280.09 ms 743.107 ms
9 San-Jose1.CA.US.EU.net (134.222.228.106) 627.704 ms 271.645 ms 273.687 ms
10 gsl-mae-w-fddi.gsl.net (198.32.136.94) 2948.17 ms 2681.96 ms 1974.74 ms
11 gsl-stock-1-Hssi4/0.gsl.net (204.59.128.33) 544.379 ms 703.606 ms 1471.63
ms
12 gsl-sl-stock-fddi.gsl.net (204.59.128.198) 495 ms 323.716 ms 320.277 ms
13 sl-stk-23-P4/0/0-155M.sprintlink.net (144.232.1.26) 470.4 ms 485.678 ms
648.39 ms
14 sl-stk-20-P4/0/0-155M.sprintlink.net (144.232.1.21) 373.106 ms 361.862 ms
304.152 ms
15 sl-stk-21-P4/0/0-155M.sprintlink.net (144.232.1.17) 318.659 ms 372.524 ms *
16 144.232.8.57 (144.232.8.57) 311.08 ms 301.47 ms 287.477 ms
17 sl-pen-22-F5/0/0.sprintlink.net (144.228.60.22) 260.334 ms 285.043 ms
265.991 ms
18 144.232.168.2 (144.232.168.2) 290.843 ms 269.845 ms 299.547 ms
19 core02-abe-hssi0-0-0.nerep.net (206.245.159.33) 301.207 ms 338.254 ms
318.793 ms
20 core01-abe-fe30-T3.FAST.NET (198.69.204.1) 326.682 ms 336.889 ms 325.614
ms
21 fngw-T3-prolog.NEREP.NET (205.147.225.6) 445.769 ms 353.404 ms 327.593 ms
22 fngw-T3-prolog.NEREP.NET (205.147.225.6) 370.935 ms !H * 316.007 ms !H
eremit:~ #
Same for .2
: I also can't seem to get out of the intranet via the Linux diald machine.
: I'm testing stuff using tracert under WinNT, and getting *'s. Here's the
: output of route (I've tried cleaning it up manually, but it still doesn't
: route):
:
: Kernel IP routing table
: Destination Gateway Genmask Flags Metric Ref Use Iface
: cs10.mil.ptd.ne * 255.255.255.255 UH 0 0 1 ppp0
~~~~~~~~ what is this route for? I'd assume, the default below
is it really necessary for diald?
: cs10.mil.ptd.ne * 255.255.255.255 UH 1 0 0 sl0
~~~~~~~~~ this should suffice, additional to the default entry below.
If it's the host on the other end, your ISP.
: 204.186.230.0 * 255.255.255.0 U 0 0 24 eth0
: 127.0.0.0 * 255.0.0.0 U 0 0 70 lo
: default cs10.mil.ptd.ne 0.0.0.0 UG 1 0 3 ppp0
:
: I have created some accounts for generic testing. If any of are brave
: enough to take a snoop on the actual machine, let me know and I'll "let
: you in."
... yep, but how could we reach your host?
Heiko
--
email : [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
pgp : A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92
finger: [EMAIL PROTECTED] [EMAIL PROTECTED]
pgpvVzkhwrFgC.pgp
Description: PGP signature
