Anyone else noticed this since 12 this afternoon, traffic to some telstra
ip ranges going international even though they appear in my national
routing table supplied by orcon... I've confirmed this from one other host
(tr.meta.net.nz) on orcon, anyone else?
Telstra DSL customers, their web hosting division and a few others are
going international then back into the country, however some clear sites
are fine as per below:
traceroute to karma.clear.net.nz (203.97.32.100), 64 hops max, 40 byte
…
[View More]packets
1 primary (60.234.66.129) 0.635 ms 0.624 ms 0.586 ms
2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.523 ms 0.638 ms
0.681 ms
3 60.234.9.8 (60.234.9.8) 0.735 ms 1.384 ms 0.837 ms
4 203.97.2.161 (203.97.2.161) 3.436 ms 3.243 ms 3.865 ms
5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 3.546 ms 7.114 ms
3.424 ms
6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 6.000 ms 3.777 ms
5.136 ms
7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.288 ms 15.050 ms
14.254 ms
8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 15.076 ms 42.059 ms
14.670 ms
9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.554 ms 11.333 ms
11.358 ms
10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.270 ms 12.990
ms 13.572 ms
11 front1-clix.clear.net.nz (203.167.243.212) 13.052 ms 13.249 ms
12.983 ms
12 karma.clear.net.nz (203.97.32.100) 13.143 ms 13.142 ms 13.069 ms
traceroute to 121-72-28-16.dsl.telstraclear.net (121.72.28.16), 64 hops
max, 40 byte packets
1 primary (60.234.66.129) 0.642 ms 0.590 ms 0.557 ms
2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.549 ms 1.177 ms
0.944 ms
3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 7.836 ms 6.838 ms
5.536 ms
4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 5.077 ms
3.406 ms 1.778 ms
5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 1.274 ms 2.696
ms 1.902 ms
6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 23.995 ms 29.158 ms
35.145 ms
7 gi1-3.gw2.syd1.asianetcom.net (202.147.40.190) 31.912 ms 24.378 ms
26.212 ms
8 61.88.133.205 (61.88.133.205) 27.267 ms 28.816 ms 28.926 ms
9 GigabitEthernet1-4.ken12.Sydney.telstra.net (139.130.65.145) 33.790
ms 30.153 ms 26.487 ms
10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 30.889 ms
28.365 ms 26.615 ms
11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 30.871 ms
28.709 ms 27.337 ms
12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 26.592 ms
27.205 ms 28.404 ms
13 unknown.net.reach.com (134.159.126.33) 27.117 ms 27.875 ms 30.866 ms
14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.229 ms 52.308 ms
58.073 ms
15 203.167.233.14 (203.167.233.14) 52.988 ms 54.358 ms 53.908 ms
16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 29.688 ms 27.061 ms
29.254 ms
17 218.101.61.163 (218.101.61.163) 29.570 ms 29.038 ms 36.667 ms
18 *^C
traceroute to www.paradise.net.nz (203.96.152.127), 64 hops max, 40 byte
packets
1 primary (60.234.66.129) 0.624 ms 0.638 ms 0.571 ms
2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.426 ms 0.446 ms
0.426 ms
3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 2.177 ms 1.786 ms
2.296 ms
4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 2.946 ms
2.431 ms 1.834 ms
5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 0.990 ms 2.633
ms 2.567 ms
6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 25.366 ms 25.566 ms
25.068 ms
7 gi1-2.gw2.syd1.asianetcom.net (202.147.40.182) 25.462 ms 24.029 ms
23.939 ms
8 61.88.133.205 (61.88.133.205) 27.373 ms 26.260 ms 28.539 ms
9 gigabitethernet4-3.ken12.sydney.telstra.net (139.130.2.65) 28.342 ms
31.793 ms 28.448 ms
10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 27.120 ms
28.729 ms 34.028 ms
11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 34.244 ms
28.564 ms 29.506 ms
12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 197.367 ms
204.040 ms 200.955 ms
13 unknown.net.reach.com (134.159.126.33) 26.861 ms 31.010 ms 29.032 ms
14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.340 ms 50.991 ms
50.760 ms
15 203.167.233.14 (203.167.233.14) 56.734 ms 51.162 ms 52.239 ms
16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 26.802 ms 25.833 ms
27.581 ms
17 218.101.61.162 (218.101.61.162) 27.050 ms 26.124 ms 31.480 ms
18 218.101.61.42 (218.101.61.42) 43.502 ms 44.411 ms 46.399 ms
^C
traceroute to www.clear.net.nz (203.97.33.220), 64 hops max, 40 byte packets
1 primary (60.234.66.129) 0.607 ms 0.610 ms 0.575 ms
2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.467 ms 0.833 ms
0.523 ms
3 60.234.9.8 (60.234.9.8) 0.537 ms 0.489 ms 0.495 ms
4 203.97.2.161 (203.97.2.161) 19.630 ms 9.418 ms 6.234 ms
5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 11.222 ms 6.493 ms
3.908 ms
6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 4.781 ms 5.040 ms
3.573 ms
7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.362 ms 15.289 ms
13.767 ms
8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 14.173 ms 15.508 ms
14.625 ms
9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.188 ms 11.102 ms
11.259 ms
10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.479 ms 12.812
ms 12.576 ms
11 front1-clix.clear.net.nz (203.167.243.212) 12.714 ms 12.948 ms
13.112 ms
^C
Cheers
Barry
[View Less]
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS24025
descr: advertised to AS9560 by Helix - AS24025
members: 202.49.240.0/22^22-29,
202.14.217.0/24^24-29,
202.49.59.0/24^24-29,
202.50.176.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)helix.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060119
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS24025
descr: advertised to AS9560 by Helix - AS24025
members: 202.14.217.0/24^24-29,
202.37.179.0/24^24-29,
202.49.59.0/24^24-29,
202.50.176.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)helix.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080131
source: NZRR
------------------------------------------------------------
[View Less]
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9889
descr: advertised to AS9560 by Maximum Internet Ltd - AS9889
members: 123.100.64.0/18^18-29,
124.198.128.0/18^18-29,
202.89.32.0/19^19-29,
203.89.160.0/19^19-29,
202.55.96.0/20^20-29,
202.189.160.0/21^21-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
117.53.150.0/23^23-29,
210.54.142.0/23^23-29,
192.138.251.0/24^24-29,
202.6.5.0/24^24-29,
202.27.8.0/24^24-29,
202.27.204.0/24^24-29,
202.36.70.0/24^24-29,
202.36.227.0/24^24-29,
202.37.72.0/24^24-29,
202.37.162.0/24^24-29,
202.37.181.0/24^24-29,
202.150.102.0/24^24-29,
203.12.15.0/24^24-29,
203.97.42.0/24^24-29,
210.54.13.0/24^24-29,
210.55.169.0/24^24-29,
210.55.214.0/24^24-29,
210.55.230.0/24^24-29,
203.167.219.56/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)maxnet.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080115
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9889
descr: advertised to AS9560 by Maxium Internet Ltd - AS9889
members: 123.100.64.0/18^18-29,
124.198.128.0/18^18-29,
202.89.32.0/19^19-29,
203.89.160.0/19^19-29,
202.55.96.0/20^20-29,
202.189.160.0/21^21-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
117.53.150.0/23^23-29,
210.54.142.0/23^23-29,
192.138.251.0/24^24-29,
202.6.5.0/24^24-29,
202.27.8.0/24^24-29,
202.27.204.0/24^24-29,
202.36.70.0/24^24-29,
202.36.227.0/24^24-29,
202.37.72.0/24^24-29,
202.37.162.0/24^24-29,
202.37.181.0/24^24-29,
202.150.102.0/24^24-29,
203.12.15.0/24^24-29,
203.97.42.0/24^24-29,
210.54.13.0/24^24-29,
210.55.169.0/24^24-29,
210.55.214.0/24^24-29,
210.55.230.0/24^24-29,
203.167.219.56/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)maxnet.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080131
source: NZRR
------------------------------------------------------------
[View Less]
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS64546
descr: Route set for Intelligroup - AS64546
members: 210.48.106.48/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: cam(a)intelligroup.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20040311
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS64546
descr: advertised to AS9439 by Soltius New Zealand Limited - AS64546
members: 210.48.106.48/29,
210.48.106.160/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: Paul.Trainor(a)soltius.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080131
source: NZRR
------------------------------------------------------------
[View Less]
Anyone else got power issues at the Sky Tower.....
We're getting an interesting story from an upstream about the status
of the electricity.
Call this me double-checking.
--
cheers, Sid
Hi guys,
A short questionnaire for those of you who sell Internet services, if
I may:
1) How many users (as a percentage) on your network use peer to peer?
2) Can you break that down in to:
- Users that use p2p 1-3 days per month on average
- Users that use p2p 1-6 days per week on average
- Users that use p2p 6-7 days per week on average
3) What percentage of your network traffic is peer to peer? (by
bitrate /and/ by packetrate, if possible)
4) What percentage of your users are …
[View More]users that do more than say, 80%
of their traffic as peer to peer
5) Do you have a histogram available of % of users for various
different amounts of data per month?
If you reply, please do it offlist, I won't tell anyone your secrets,
etc. I'm only after percentages.
I don't work for any competing ISPs right now, so can't use your info
competitively, this is for some Internet research work I'm doing -
believe it or not in the IPv6 area. Findings will be publicly
available and based on an aggregate of all ISPs who give me data, and
I'll likely talk about my findings at the next NZNOG meeting. For the
good of the Internet community and all that.
If you have some kind of p2p shaping boxes, they tend to have these
sorts of stats available.
If you can only provide one or two of these stats, that's still really
useful.
Cheers!
--
Nathan Ward
[View Less]
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.53.176.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
116.90.128.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.6.116.0/23^23-29,
202.124.106.0/23^23-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.20.97.0/24^24-29,
202.36.33.0/24^24-29,
202.36.119.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20071221
changed: rpsl-admin(a)nzix.net 20080102
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.53.176.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
116.90.128.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.59.4.0/22^22-29,
202.89.4.0/22^22-29,
202.6.116.0/23^23-29,
202.124.106.0/23^23-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.20.97.0/24^24-29,
202.36.33.0/24^24-29,
202.36.119.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080129
source: NZRR
------------------------------------------------------------
[View Less]
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS9503
descr: advertised to AS9439 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.53.176.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
116.90.128.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.6.116.0/23^23-29,
202.124.106.0/23^23-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.20.97.0/24^24-29,
202.36.33.0/24^24-29,
202.36.119.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20071221
changed: rpsl-admin(a)nzix.net 20080102
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS9503
descr: advertised to AS9439 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.53.176.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
116.90.128.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.59.4.0/22^22-29,
202.89.4.0/22^22-29,
202.6.116.0/23^23-29,
202.124.106.0/23^23-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.20.97.0/24^24-29,
202.36.33.0/24^24-29,
202.36.119.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080129
source: NZRR
------------------------------------------------------------
[View Less]
are the presentations from the conference up on the web page yet?
--
Mark Smith
E mark.smith(a)endace.com
P +64 7 957 0540
W http://www.endace.com
Endace Technologies, Limited
85 Alexandra Street
Hamilton
Endace delivers absolute performance for monitoring and intervention
over the widest range of network types and software applications.
A Mac mini-DIV to DVI and 3-pin to cloverleaf mains lead where behind
at NZNOG last week.
Let me know if they belong to you, and I'll send them off.
Cheers,
Jonny.