I was wondering if Sprint had any intention to fix thier hostnames on
thier routers. Ever since upgrading the recent versions of Os's, the name
resolveres no longer resolve names with '/'s in them. Ie:
on a cisco:
1 nac-nyc1-s0-3Mb.nac.net (207.99.7.14) 4 msec 4 msec 16 msec
2 e9-0.border1.nyc1.genuity.net (207.240.48.49) [AS 3847] 12 msec 4 msec
3 f6.core1.nyc1.genuity.net (207.240.1.81) [AS 3847] 12 msec 12 msec 8
4 peer1.nyc1.genuity.net (207.240.48.3) [AS 3847] 16 msec 16 msec 56
5 sl-pen-2-F4/0.sprintlink.net (192.157.69.10) [AS 3561] 132 msec 212
6 sl-pen-20-F1/0-100M.sprintlink.net (144.232.0.121) [AS 1239] 20 msec
7 sl-pen-17-P4/0/0-155M.sprintlink.net (144.232.0.65) [AS 1239] 16 msec
yet, on freeBsd 2.2:
traceroute to www.visi.com (204.73.178.2), 30 hops max, 40 byte packets
1 nac-whi4-Fa0-100Mb (207.99.5.204) 0.989 ms 2.527 ms 0.840 ms
2 nac-nyc1-s0-3Mb (207.99.7.14) 23.137 ms 22.779 ms 12.263 ms
3 e9-0.border1.nyc1.genuity.net (207.240.48.49) 38.895 ms 14.305 ms
4 f6.core1.nyc1.genuity.net (207.240.1.81) 12.118 ms 9.193 ms 10.028
5 peer1.nyc1.genuity.net (207.240.48.3) 24.715 ms 23.773 ms 16.742 ms
6 192.157.69.10 (192.157.69.10) 20.605 ms 27.076 ms 18.037 ms
7 144.232.0.121 (144.232.0.121) 20.211 ms 28.754 ms 10.973 ms
8 144.232.0.65 (144.232.0.65) 10.669 ms 17.250 ms 23.139 ms
Hrmph.