-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Everybody, I'm trying to get a better understanding of how the DSL network is integrated together in New Zealand. I'm hoping someone can help explain to me why their is such big latency gaps in some of the connections. Below is the output from a traceroute between me on Ihug Jetstart DSL and an Xtra Jetstream connection with a Static IP. 1 192.168.1.2 (192.168.1.2) 0.299 ms 0.148 ms 0.142 ms 2 203-118-173-1.adsl.ihug.co.nz (203.118.173.1) 56.506 ms 57.695 ms 60.022 ms Is 203.118.173.1 an Ihug router or a Telecom router? 3 192.168.253.225 (192.168.253.225) 66.866 ms 58.911 ms 61.027 ms 4 192.168.254.42 (192.168.254.42) 70.011 ms 69.028 ms 59.954 ms 5 v-93-tig-nz-akl-core-1.ihug.net (203.109.156.145) 70.147 ms 69.346 ms 68.020 ms 6 203-109-156-98.ihug.net (203.109.156.98) 69.904 ms 67.363 ms 71.046 ms 7 a5-0-0-40.akcr5.global-gateway.net.nz (202.37.245.165) 210.854 ms 203.399 ms 185.586 ms This is my real question... why is this such a big lag between 6 & 7. 140ms seems to be very high? Is there some type of bandwidth gap between Ihug and Global Gateway? Everything below this point is irrelevant.... Cheers, Jon -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/uGYITV0Xs0S7UB4RAg8zAJ4yB4wn5iqCWgzhQpljznjnyeTiSQCfaDAu INl9jjcMXNgPbWST7gHB5kE= =qECf -----END PGP SIGNATURE-----
On Mon, 17 Nov 2003, Jon Dean wrote:
I'm trying to get a better understanding of how the DSL network is integrated together in New Zealand. I'm hoping someone can help explain to me why their is such big latency gaps in some of the connections.
Below is the output from a traceroute between me on Ihug Jetstart DSL and an Xtra Jetstream connection with a Static IP.
1 192.168.1.2 (192.168.1.2) 0.299 ms 0.148 ms 0.142 ms 2 203-118-173-1.adsl.ihug.co.nz (203.118.173.1) 56.506 ms 57.695 ms 60.022 ms
Is 203.118.173.1 an Ihug router or a Telecom router?
No. That is a RAN (Radius Access Node) within the telecom IPNet network.
3 192.168.253.225 (192.168.253.225) 66.866 ms 58.911 ms 61.027 ms 4 192.168.254.42 (192.168.254.42) 70.011 ms 69.028 ms 59.954 ms 5 v-93-tig-nz-akl-core-1.ihug.net (203.109.156.145) 70.147 ms 69.346 ms 68.020 ms 6 203-109-156-98.ihug.net (203.109.156.98) 69.904 ms 67.363 ms 71.046 ms 7 a5-0-0-40.akcr5.global-gateway.net.nz (202.37.245.165) 210.854 ms 203.399 ms 185.586 ms
Firstly, you can disregard how it is working right now. If you'd checked the MOTD page, you'd see there are national traffic issues at the moment.
This is my real question... why is this such a big lag between 6 & 7. 140ms seems to be very high? Is there some type of bandwidth gap between Ihug and Global Gateway?
There isn't. Global Gateway isn't out normal national peering circuit. Again, refer MOTD. -- Gavin Grieve Systems Administrator Phone: +64 9 359 2708 Ihug Ltd, Auckland, New Zealand. Email: noc(a)ihug.co.nz <#seattle/weezel> This End-User License is an agreement between Microsoft Corporation (hereafter referred to as "Microsoft") and you, the end-user (hereafter referred to as "our bi$%^$"). - http://www.bash.org/?6107
On Mon, 17 Nov 2003, Gavin Grieve wrote:
No. That is a RAN (Radius Access Node) within the telecom IPNet network.
Sorry, I forgot to check this before ^X, I think that should be Remote Access Node. -- Gavin Grieve Systems Administrator Phone: +64 9 359 2708 Ihug Ltd, Auckland, New Zealand. Email: noc(a)ihug.co.nz <#seattle/weezel> This End-User License is an agreement between Microsoft Corporation (hereafter referred to as "Microsoft") and you, the end-user (hereafter referred to as "our bi$%^$"). - http://www.bash.org/?6107
participants (2)
-
Gavin Grieve -
Jon Dean