I-Root Server avaiable at the WIX
There is now an instance of an anycast I-Root name server attached to the WIX. Those peering with the WIX route servers should be seeing an announcment for 192.36.148.0/24. From Wellington I'm seeing RTTs like this: $ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17) 56(84) bytes of data. 64 bytes from 192.36.148.17: icmp_seq=1 ttl=252 time=3.90 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=252 time=1.12 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=252 time=1.73 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=252 time=2.07 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=252 time=1.18 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=252 time=1.62 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=252 time=1.80 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=252 time=1.92 ms 64 bytes from 192.36.148.17: icmp_seq=9 ttl=252 time=1.43 ms --- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8080ms rtt min/avg/max/mdev = 1.125/1.867/3.905/0.782 ms and from a host in Auckland which doesn't see the announcement I see: $ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17): 56 data bytes 64 bytes from 192.36.148.17: icmp_seq=0 ttl=55 time=257.7 ms 64 bytes from 192.36.148.17: icmp_seq=1 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=55 time=256.8 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=55 time=256.2 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=55 time=257.9 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=55 time=259.5 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=55 time=256.5 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=55 time=257.2 ms --- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 packets received, 0% packet loss round-trip min/avg/max = 255.9/257.0/259.5 ms Thanks to InternetNZ who funded this and to Packet Clearing House and Autonomica for making it happen. Enjoy!
And as you would expect: Tracing route to i.root-servers.net [192.36.148.17] over a maximum of 30 hops: 1 7 ms 6 ms 6 ms 10.23.25.50 2 6 ms 6 ms 6 ms 10.23.20.5 3 50 ms 49 ms 50 ms 203-167-185-1.dsl.clear.net.nz [203.167.185.1] 4 48 ms 48 ms 47 ms 192.168.253.201 5 58 ms 58 ms 60 ms ba3-atm11-0-0-490-acld.auckland.clix.net.nz [203.97.81.57] 6 59 ms 57 ms 59 ms jcore2-ge-0-2-0-927-acld.auckland.clix.net.nz [218.101.61.14] 7 58 ms 57 ms 58 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 8 183 ms 183 ms 184 ms xcore2.tspn.telstraclear.net [203.98.42.66] 9 184 ms 184 ms 183 ms GigabitEthernet3-0.GW1.LAX1.ALTER.NET [157.130.245.21] 10 191 ms 191 ms 192 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218] 11 189 ms 189 ms 187 ms 0.so-0-0-0.TL1.LAX2.ALTER.NET [152.63.2.62] 12 252 ms 252 ms 253 ms 0.so-7-0-0.IL1.DCA6.ALTER.NET [152.63.9.193] 13 254 ms 256 ms 255 ms so-0-0-0.IR1.DCA4.ALTER.NET [146.188.13.34] 14 345 ms 345 ms 345 ms so-5-0-0.TR1.AMS2.ALTER.NET [146.188.5.198] 15 339 ms 337 ms 336 ms so-5-0-0.XR1.AMS6.ALTER.NET [146.188.8.77] 16 345 ms 344 ms 346 ms so-4-0-0.CR1.AMS9.ALTER.NET [212.136.185.101] 17 338 ms 337 ms 337 ms so-0-0-0.HR1.AMS9.ALTER.NET [212.136.185.94] 18 336 ms 337 ms 336 ms so-0-0-0.UR1.AMS9.ALTER.NET [212.136.177.150] 19 345 ms 345 ms 348 ms Vlan101.MSFC0.DS2.AMS9.ALTER.NET [212.136.185.66] 20 337 ms 336 ms 337 ms ge-0-1.r1.ams.dnsnode.net [213.53.32.210] 21 338 ms 337 ms 337 ms i.root-servers.net [192.36.148.17] Trace complete. Barry
-----Original Message----- From: Andy Linton [mailto:asjl(a)citylink.co.nz] Sent: Tuesday, 1 March 2005 9:44 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] I-Root Server avaiable at the WIX
There is now an instance of an anycast I-Root name server attached to the WIX. Those peering with the WIX route servers should be seeing an announcment for 192.36.148.0/24.
From Wellington I'm seeing RTTs like this:
$ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17) 56(84) bytes of data. 64 bytes from 192.36.148.17: icmp_seq=1 ttl=252 time=3.90 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=252 time=1.12 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=252 time=1.73 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=252 time=2.07 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=252 time=1.18 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=252 time=1.62 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=252 time=1.80 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=252 time=1.92 ms 64 bytes from 192.36.148.17: icmp_seq=9 ttl=252 time=1.43 ms
--- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8080ms rtt min/avg/max/mdev = 1.125/1.867/3.905/0.782 ms
and from a host in Auckland which doesn't see the announcement I see:
$ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17): 56 data bytes 64 bytes from 192.36.148.17: icmp_seq=0 ttl=55 time=257.7 ms 64 bytes from 192.36.148.17: icmp_seq=1 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=55 time=256.8 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=55 time=256.2 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=55 time=257.9 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=55 time=259.5 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=55 time=256.5 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=55 time=257.2 ms
--- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 packets received, 0% packet loss round-trip min/avg/max = 255.9/257.0/259.5 ms
Thanks to InternetNZ who funded this and to Packet Clearing House and Autonomica for making it happen.
Enjoy!
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
man that sucks lol Barry Murphy wrote:
And as you would expect:
Tracing route to i.root-servers.net [192.36.148.17] over a maximum of 30 hops:
1 7 ms 6 ms 6 ms 10.23.25.50 2 6 ms 6 ms 6 ms 10.23.20.5 3 50 ms 49 ms 50 ms 203-167-185-1.dsl.clear.net.nz [203.167.185.1] 4 48 ms 48 ms 47 ms 192.168.253.201 5 58 ms 58 ms 60 ms ba3-atm11-0-0-490-acld.auckland.clix.net.nz [203.97.81.57] 6 59 ms 57 ms 59 ms jcore2-ge-0-2-0-927-acld.auckland.clix.net.nz [218.101.61.14] 7 58 ms 57 ms 58 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 8 183 ms 183 ms 184 ms xcore2.tspn.telstraclear.net [203.98.42.66] 9 184 ms 184 ms 183 ms GigabitEthernet3-0.GW1.LAX1.ALTER.NET [157.130.245.21] 10 191 ms 191 ms 192 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218] 11 189 ms 189 ms 187 ms 0.so-0-0-0.TL1.LAX2.ALTER.NET [152.63.2.62] 12 252 ms 252 ms 253 ms 0.so-7-0-0.IL1.DCA6.ALTER.NET [152.63.9.193] 13 254 ms 256 ms 255 ms so-0-0-0.IR1.DCA4.ALTER.NET [146.188.13.34] 14 345 ms 345 ms 345 ms so-5-0-0.TR1.AMS2.ALTER.NET [146.188.5.198] 15 339 ms 337 ms 336 ms so-5-0-0.XR1.AMS6.ALTER.NET [146.188.8.77] 16 345 ms 344 ms 346 ms so-4-0-0.CR1.AMS9.ALTER.NET [212.136.185.101] 17 338 ms 337 ms 337 ms so-0-0-0.HR1.AMS9.ALTER.NET [212.136.185.94] 18 336 ms 337 ms 336 ms so-0-0-0.UR1.AMS9.ALTER.NET [212.136.177.150] 19 345 ms 345 ms 348 ms Vlan101.MSFC0.DS2.AMS9.ALTER.NET [212.136.185.66] 20 337 ms 336 ms 337 ms ge-0-1.r1.ams.dnsnode.net [213.53.32.210] 21 338 ms 337 ms 337 ms i.root-servers.net [192.36.148.17]
Trace complete.
Barry
-----Original Message----- From: Andy Linton [mailto:asjl(a)citylink.co.nz] Sent: Tuesday, 1 March 2005 9:44 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] I-Root Server avaiable at the WIX
There is now an instance of an anycast I-Root name server attached to the WIX. Those peering with the WIX route servers should be seeing an announcment for 192.36.148.0/24.
From Wellington I'm seeing RTTs like this:
$ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17) 56(84) bytes of data. 64 bytes from 192.36.148.17: icmp_seq=1 ttl=252 time=3.90 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=252 time=1.12 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=252 time=1.73 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=252 time=2.07 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=252 time=1.18 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=252 time=1.62 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=252 time=1.80 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=252 time=1.92 ms 64 bytes from 192.36.148.17: icmp_seq=9 ttl=252 time=1.43 ms
--- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8080ms rtt min/avg/max/mdev = 1.125/1.867/3.905/0.782 ms
and from a host in Auckland which doesn't see the announcement I see:
$ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17): 56 data bytes 64 bytes from 192.36.148.17: icmp_seq=0 ttl=55 time=257.7 ms 64 bytes from 192.36.148.17: icmp_seq=1 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=55 time=256.8 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=55 time=256.2 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=55 time=257.9 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=55 time=259.5 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=55 time=256.5 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=55 time=257.2 ms
--- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 packets received, 0% packet loss round-trip min/avg/max = 255.9/257.0/259.5 ms
Thanks to InternetNZ who funded this and to Packet Clearing House and Autonomica for making it happen.
Enjoy!
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Looks ok for me.. traceroute to i.root-servers.net (192.36.148.17), 30 hops max, 38 byte packets 1 fe1-0-0.cr1.akl1.concept.net.nz (202.150.96.30) 0.567 ms 0.496 ms 0.482 ms 2 fe0-0-0.br1.akl1.concept.net.nz (202.150.96.254) 0.423 ms 0.569 ms 0.334 ms 3 pch1.wix.net.nz (202.7.1.253) 12.210 ms 10.478 ms 13.021 ms 4 i.root-servers.net (192.36.148.17) 13.604 ms 19.880 ms 10.404 ms -----Original Message----- From: Dan Clark [mailto:dan(a)scarfies.net] Sent: Tuesday, 1 March 2005 10:00 a.m. To: Barry Murphy Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] I-Root Server avaiable at the WIX man that sucks lol Barry Murphy wrote:
And as you would expect:
Tracing route to i.root-servers.net [192.36.148.17] over a maximum of 30 hops:
1 7 ms 6 ms 6 ms 10.23.25.50 2 6 ms 6 ms 6 ms 10.23.20.5 3 50 ms 49 ms 50 ms 203-167-185-1.dsl.clear.net.nz [203.167.185.1] 4 48 ms 48 ms 47 ms 192.168.253.201 5 58 ms 58 ms 60 ms ba3-atm11-0-0-490-acld.auckland.clix.net.nz [203.97.81.57] 6 59 ms 57 ms 59 ms jcore2-ge-0-2-0-927-acld.auckland.clix.net.nz [218.101.61.14] 7 58 ms 57 ms 58 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 8 183 ms 183 ms 184 ms xcore2.tspn.telstraclear.net [203.98.42.66] 9 184 ms 184 ms 183 ms GigabitEthernet3-0.GW1.LAX1.ALTER.NET [157.130.245.21] 10 191 ms 191 ms 192 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218] 11 189 ms 189 ms 187 ms 0.so-0-0-0.TL1.LAX2.ALTER.NET [152.63.2.62] 12 252 ms 252 ms 253 ms 0.so-7-0-0.IL1.DCA6.ALTER.NET [152.63.9.193] 13 254 ms 256 ms 255 ms so-0-0-0.IR1.DCA4.ALTER.NET [146.188.13.34] 14 345 ms 345 ms 345 ms so-5-0-0.TR1.AMS2.ALTER.NET [146.188.5.198] 15 339 ms 337 ms 336 ms so-5-0-0.XR1.AMS6.ALTER.NET [146.188.8.77] 16 345 ms 344 ms 346 ms so-4-0-0.CR1.AMS9.ALTER.NET [212.136.185.101] 17 338 ms 337 ms 337 ms so-0-0-0.HR1.AMS9.ALTER.NET [212.136.185.94] 18 336 ms 337 ms 336 ms so-0-0-0.UR1.AMS9.ALTER.NET [212.136.177.150] 19 345 ms 345 ms 348 ms Vlan101.MSFC0.DS2.AMS9.ALTER.NET [212.136.185.66] 20 337 ms 336 ms 337 ms ge-0-1.r1.ams.dnsnode.net [213.53.32.210] 21 338 ms 337 ms 337 ms i.root-servers.net [192.36.148.17]
Trace complete.
Barry
-----Original Message----- From: Andy Linton [mailto:asjl(a)citylink.co.nz] Sent: Tuesday, 1 March 2005 9:44 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] I-Root Server avaiable at the WIX
There is now an instance of an anycast I-Root name server attached to the WIX. Those peering with the WIX route servers should be seeing an announcment for 192.36.148.0/24.
From Wellington I'm seeing RTTs like this:
$ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17) 56(84) bytes of data. 64 bytes from 192.36.148.17: icmp_seq=1 ttl=252 time=3.90 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=252 time=1.12 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=252 time=1.73 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=252 time=2.07 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=252 time=1.18 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=252 time=1.62 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=252 time=1.80 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=252 time=1.92 ms 64 bytes from 192.36.148.17: icmp_seq=9 ttl=252 time=1.43 ms
--- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8080ms rtt min/avg/max/mdev = 1.125/1.867/3.905/0.782 ms
and from a host in Auckland which doesn't see the announcement I see:
$ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17): 56 data bytes 64 bytes from 192.36.148.17: icmp_seq=0 ttl=55 time=257.7 ms 64 bytes from 192.36.148.17: icmp_seq=1 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=55 time=256.8 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=55 time=256.2 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=55 time=257.9 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=55 time=259.5 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=55 time=256.5 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=55 time=257.2 ms
--- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 packets received, 0% packet loss round-trip min/avg/max = 255.9/257.0/259.5 ms
Thanks to InternetNZ who funded this and to Packet Clearing House and Autonomica for making it happen.
Enjoy!
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Equally uninspiring results from my laptop at Canterbury unversity...
traceroute to i.root-servers.net (192.36.148.17), 30 hops max, 40 byte
packets
1 172.18.254.254 (172.18.254.254) 17.798 ms 2.545 ms 1.653 ms
2 cantcp.canterbury.ac.nz (132.181.3.233) 22.563 ms 1.846 ms 36.179 ms
3 202.36.179.126 (202.36.179.126) 3.137 ms 2.456 ms 6.486 ms
4 202.36.179.1 (202.36.179.1) 3.386 ms 3.115 ms 2.841 ms
5 202.124.98.241 (202.124.98.241) 5.076 ms 7.14 ms 3.155 ms
6 202.50.245.249 (202.50.245.249) 79.986 ms 19.496 ms 25.348 ms
7 ge-0-3-0-6.akbr3.global-gateway.net.nz (202.37.246.18) 28.652 ms
18.355 ms 18.161 ms
8 p4-7.sybr2.global-gateway.net.nz (203.96.120.230) 44.952 ms 58.725 ms
48.907 ms
9 p4-6.sybr3.global-gateway.net.nz (203.96.120.194) 45.201 ms 48.182 ms
49.675 ms
10 pos-1-2.gw2.syd1.asianetcom.net (202.147.41.117) 71.08 ms 56.613 ms
48.162 ms
11 po2-1.gw1.nrt4.asianetcom.net (202.147.55.110) 217.825 ms 211.565 ms
209.219 ms
12 gi4-3.cr2.nrt1.asianetcom.net (202.147.1.126) 218.581 ms 205.288 ms
213.021 ms
13 gi5-2.gw1.nrt2.asianetcom.net (202.147.0.166) 206.643 ms 207.427 ms
215.932 ms
14 202.232.8.165 (202.232.8.165) 213.189 ms 206.817 ms 202.425 ms
15 tky001bb00.iij.net (210.130.143.52) 207.701 ms 202.97 ms 207.396 ms
16 tky001ix03.iij.net (210.130.143.49) 208.993 ms 202.824 ms 206.6 ms
17 202.249.2.180 (202.249.2.180) 205.6 ms 211.996 ms 214.902 ms
18 i.root-servers.net (192.36.148.17) 203.938 ms 211.547 ms 203.048 ms
On 2005-03-01 11:24 AM, "Craig Spiers"
Looks ok for me..
traceroute to i.root-servers.net (192.36.148.17), 30 hops max, 38 byte packets 1 fe1-0-0.cr1.akl1.concept.net.nz (202.150.96.30) 0.567 ms 0.496 ms 0.482 ms 2 fe0-0-0.br1.akl1.concept.net.nz (202.150.96.254) 0.423 ms 0.569 ms 0.334 ms 3 pch1.wix.net.nz (202.7.1.253) 12.210 ms 10.478 ms 13.021 ms 4 i.root-servers.net (192.36.148.17) 13.604 ms 19.880 ms 10.404 ms
-----Original Message----- From: Dan Clark [mailto:dan(a)scarfies.net] Sent: Tuesday, 1 March 2005 10:00 a.m. To: Barry Murphy Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] I-Root Server avaiable at the WIX
man that sucks lol
Barry Murphy wrote:
And as you would expect:
Tracing route to i.root-servers.net [192.36.148.17] over a maximum of 30 hops:
1 7 ms 6 ms 6 ms 10.23.25.50 2 6 ms 6 ms 6 ms 10.23.20.5 3 50 ms 49 ms 50 ms 203-167-185-1.dsl.clear.net.nz [203.167.185.1] 4 48 ms 48 ms 47 ms 192.168.253.201 5 58 ms 58 ms 60 ms ba3-atm11-0-0-490-acld.auckland.clix.net.nz [203.97.81.57] 6 59 ms 57 ms 59 ms jcore2-ge-0-2-0-927-acld.auckland.clix.net.nz [218.101.61.14] 7 58 ms 57 ms 58 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 8 183 ms 183 ms 184 ms xcore2.tspn.telstraclear.net [203.98.42.66] 9 184 ms 184 ms 183 ms GigabitEthernet3-0.GW1.LAX1.ALTER.NET [157.130.245.21] 10 191 ms 191 ms 192 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218] 11 189 ms 189 ms 187 ms 0.so-0-0-0.TL1.LAX2.ALTER.NET [152.63.2.62] 12 252 ms 252 ms 253 ms 0.so-7-0-0.IL1.DCA6.ALTER.NET [152.63.9.193] 13 254 ms 256 ms 255 ms so-0-0-0.IR1.DCA4.ALTER.NET [146.188.13.34] 14 345 ms 345 ms 345 ms so-5-0-0.TR1.AMS2.ALTER.NET [146.188.5.198] 15 339 ms 337 ms 336 ms so-5-0-0.XR1.AMS6.ALTER.NET [146.188.8.77] 16 345 ms 344 ms 346 ms so-4-0-0.CR1.AMS9.ALTER.NET [212.136.185.101] 17 338 ms 337 ms 337 ms so-0-0-0.HR1.AMS9.ALTER.NET [212.136.185.94] 18 336 ms 337 ms 336 ms so-0-0-0.UR1.AMS9.ALTER.NET [212.136.177.150] 19 345 ms 345 ms 348 ms Vlan101.MSFC0.DS2.AMS9.ALTER.NET [212.136.185.66] 20 337 ms 336 ms 337 ms ge-0-1.r1.ams.dnsnode.net [213.53.32.210] 21 338 ms 337 ms 337 ms i.root-servers.net [192.36.148.17]
Trace complete.
Barry
-----Original Message----- From: Andy Linton [mailto:asjl(a)citylink.co.nz] Sent: Tuesday, 1 March 2005 9:44 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] I-Root Server avaiable at the WIX
There is now an instance of an anycast I-Root name server attached to the WIX. Those peering with the WIX route servers should be seeing an announcment for 192.36.148.0/24.
From Wellington I'm seeing RTTs like this:
$ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17) 56(84) bytes of data. 64 bytes from 192.36.148.17: icmp_seq=1 ttl=252 time=3.90 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=252 time=1.12 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=252 time=1.73 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=252 time=2.07 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=252 time=1.18 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=252 time=1.62 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=252 time=1.80 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=252 time=1.92 ms 64 bytes from 192.36.148.17: icmp_seq=9 ttl=252 time=1.43 ms
--- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8080ms rtt min/avg/max/mdev = 1.125/1.867/3.905/0.782 ms
and from a host in Auckland which doesn't see the announcement I see:
$ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17): 56 data bytes 64 bytes from 192.36.148.17: icmp_seq=0 ttl=55 time=257.7 ms 64 bytes from 192.36.148.17: icmp_seq=1 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=55 time=256.8 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=55 time=256.2 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=55 time=257.9 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=55 time=259.5 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=55 time=256.5 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=55 time=257.2 ms
--- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 packets received, 0% packet loss round-trip min/avg/max = 255.9/257.0/259.5 ms
Thanks to InternetNZ who funded this and to Packet Clearing House and Autonomica for making it happen.
Enjoy!
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
I think we've had enough traceroutes today... The I-Root Servers (the NZ versions of them) are only available to WIX connected people (or people who connect peer directly to the I Root Servers.) (ie not advertised to any of the Major National Carriers in NZ). So people on say people on TelstraClear/Telecom Networks without a WIX connection (most of the volume I would think of New Zealand) will use the other closest one overseas, and not connect to the WIX one. Thanks Craig
-----Original Message----- From: Richard Dingwall [mailto:richard(a)bluewire.net.nz] Sent: Tuesday, March 01, 2005 1:27 PM To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] I-Root Server avaiable at the WIX
Equally uninspiring results from my laptop at Canterbury unversity...
traceroute to i.root-servers.net (192.36.148.17), 30 hops max, 40 byte packets 1 172.18.254.254 (172.18.254.254) 17.798 ms 2.545 ms 1.653 ms 2 cantcp.canterbury.ac.nz (132.181.3.233) 22.563 ms 1.846 ms 36.179 ms
Hmmm, so the aberrant nature of peering in NZ rears its ugly head... Seems strange that the telcos would prefer to route offshore at a financial and a performance cost, rather than peer in NZ and give their users faster speeds and cost reductions... Keith Davidson Craig Whitmore wrote:
I think we've had enough traceroutes today...
The I-Root Servers (the NZ versions of them) are only available to WIX connected people (or people who connect peer directly to the I Root Servers.) (ie not advertised to any of the Major National Carriers in NZ).
So people on say people on TelstraClear/Telecom Networks without a WIX connection (most of the volume I would think of New Zealand) will use the other closest one overseas, and not connect to the WIX one.
-----Original Message----- From: Keith Davidson [mailto:keith(a)wise.net.nz] Sent: Tuesday, March 01, 2005 2:19 PM To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] I-Root Server avaiable at the WIX
Hmmm, so the aberrant nature of peering in NZ rears its ugly head... Seems strange that the telcos would prefer to route offshore at a financial and a performance cost, rather than peer in NZ and give their users faster speeds and cost reductions...
I guess now that Paradise high speed customers are paying 10 times the cost now for data to trademe and stuff than they did last week as it goes internationally (TelstraClear don't peer with AT&T ) (but the other Major Telco Telecom do) But it still says on Paradises website: Citylink Traffic is calculated in the same way as JetStart Traffic, with the exception of traffic delivered through the Wellington Internet Exchange (WIX), which is completely free! Thanks Craig Whitmore
And explains why, at the peering workshops at APRICOT in Kyoto last week, that New Zealand was held up as the "laughing stock" of the rest of the world, and the Asia Pacific region in particular, for our peculiarly aberrant peering practices. OK, I admit that Australia did not escape unscathed - but NZ bore the brunt of the laughter and ridicule.... Keith Davidson Craig Whitmore wrote:
I guess now that Paradise high speed customers are paying 10 times the cost now for data to trademe and stuff than they did last week as it goes internationally (TelstraClear don't peer with AT&T ) (but the other Major Telco Telecom do)
But it still says on Paradises website:
Citylink Traffic is calculated in the same way as JetStart Traffic, with the exception of traffic delivered through the Wellington Internet Exchange (WIX), which is completely free!
On Tue, 1 Mar 2005, Keith Davidson wrote:
And explains why, at the peering workshops at APRICOT in Kyoto last week, that New Zealand was held up as the "laughing stock" of the rest of the world, and the Asia Pacific region in particular, for our peculiarly aberrant peering practices. OK, I admit that Australia did not escape unscathed - but NZ bore the brunt of the laughter and ridicule....
What did they find so funny? That we have provider-neutral peering for the cost of the access circuit? Or that the two largest ISP/telco organisations in the country are playing silly buggers with it? -- Matthew Poole "Don't use force. Get a bigger hammer."
Matthew Poole wrote:
On Tue, 1 Mar 2005, Keith Davidson wrote:
And explains why, at the peering workshops at APRICOT in Kyoto last week, that New Zealand was held up as the "laughing stock" of the rest of the world, and the Asia Pacific region in particular, for our peculiarly aberrant peering practices. OK, I admit that Australia did not escape unscathed - but NZ bore the brunt of the laughter and ridicule....
What did they find so funny? That we have provider-neutral peering for the cost of the access circuit? Or that the two largest ISP/telco organisations in the country are playing silly buggers with it?
Definitely the latter, not the former... Keith Davidson
Craig Whitmore wrote:
I think we've had enough traceroutes today...
The I-Root Servers (the NZ versions of them) are only available to WIX connected people (or people who connect peer directly to the I Root Servers.) (ie not advertised to any of the Major National Carriers in NZ).
So people on say people on TelstraClear/Telecom Networks without a WIX connection (most of the volume I would think of New Zealand) will use the other closest one overseas, and not connect to the WIX one.
Well those on TelstraClear networks will access the F-root server attached to the APE. And remember this applies to all of you who are connected to other ISPs who peer with the APE route servers or who have negotiated a bilateral peering agreement with ISC. You can check which I-root server you're talking to using: dig +norec @I.ROOT-SERVERS.NET HOSTNAME.BIND CHAOS TXT Expect to see the string "s1.wlg" in the result if you're getting the WIX connected server. and which F-root server using: dig +norec @F.ROOT-SERVERS.NET HOSTNAME.BIND CHAOS TXT Expect to see the string "akl1b.f.root-servers.org" in the result if you're getting the APE connected server. I don't think there's any need to post a whole raft of results from these to the NZNOG. If you think your path is suboptimal, talk to your ISP/Telco - they're the ones who can fix this for you!
On 1 Mar 2005, at 00:25, Andy Linton wrote:
Well those on TelstraClear networks will access the F-root server attached to the APE. And remember this applies to all of you who are connected to other ISPs who peer with the APE route servers or who have negotiated a bilateral peering agreement with ISC.
In case it's useful to anybody, the bilateral peering negotiations usually go something like this: ISP: We would like to peer with you. ISC: OK then. [I once heard that the original dark-fibre interconnect agreement between Citylink and Saturn involved Michael Newbery and Richard Naylor looking down a manhole for about two minutes and then saying "OK then". It's a bit like that.] At the APE we have a huge preference for peering with people over the APE. We send the F-root prefixes (v4 and v6) to the very excellent Citylink route servers, and we are very happy to send them to other APE participants directly as well. For people who really, truly, honestly have tremendous difficulties connecting to the APE for some reason (technical or otherwise) and who prefer to connect directly, we will absolutely consider a direct interconnection. For most (almost all) people, connecting directly makes no sense, and using the APE is cheaper and better. Joe
Joe Abley wrote:
In case it's useful to anybody, the bilateral peering negotiations usually go something like this:
ISP: We would like to peer with you. ISC: OK then.
At APRICOT last week, some leading international advocates were suggesting that foreign language guidebooks need updating, and that the 4 critical phrases required in each language are: 1. Hello 2. Yes 3. Will you peer with me 4. Thank you
At the APE we have a huge preference for peering with people over the APE. We send the F-root prefixes (v4 and v6) to the very excellent Citylink route servers, and we are very happy to send them to other APE participants directly as well.
For people who really, truly, honestly have tremendous difficulties connecting to the APE for some reason (technical or otherwise) and who prefer to connect directly, we will absolutely consider a direct interconnection. For most (almost all) people, connecting directly makes no sense, and using the APE is cheaper and better.
But you could be charging so much more for "transit" for that, couldn't you? :-> Keith Davidson
participants (9)
-
Andy Linton -
Barry Murphy -
Craig Spiers -
Craig Whitmore -
Dan Clark -
Joe Abley -
Keith Davidson -
Matthew Poole -
Richard Dingwall