- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 06 Mar '05

06 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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 all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: Notification of NZRR Database changes (fwd) - Date: Mon, 7 Mar 2005 14:29:34 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503071427520.4454(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: WIX peering at '202.7.0.123' descr: see Citylink RT job #2009 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050307 source: NZRR REPLACED BY: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: WIX peering at '202.7.0.123' descr: see Citylink RT job #2009 descr: PNIX peering at '218.100.21.10' descr: see Citylink RT job #1487 descr: APE peering at '192.203.154.17' descr: see Citylink RT job #1552 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17705 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS17705 import: from AS9281 accept ANY AND NOT fltr-bogons export: to AS9281 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050307 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 06 Mar '05

06 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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 all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: PNIX peering at '218.100.21.10' descr: see Citylink RT job #1487 descr: APE peering at '192.203.154.17' descr: see Citylink RT job #1552 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS17705 import: from AS9281 accept ANY AND NOT fltr-bogons export: to AS9281 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR REPLACED BY: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: WIX peering at '202.7.0.123' descr: see Citylink RT job #2009 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050307 source: NZRR --- PREVIOUS OBJECT: route: 203.96.157.0/24 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR REPLACED BY: route: 203.96.157.0/24 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050307 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS17705 descr: Route set advertised to AS9439 by Inspire Net - AS17705 members: 203.79.88.0/24^24-29, 203.79.89.0/24^24-29, 203.96.157.0/24^24-29, 203.114.128.0/18^18-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)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050307 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 06 Mar '05

06 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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 all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: RE: [CityLink #2003] AutoReply: Routing updates for APE Route Servers (fwd) - Date: Mon, 7 Mar 2005 11:42:37 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503071141330.4454(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 210.55.230.0/24^24-29, 210.55.214.0/24^24-29, 210.55.169.0/24^24-29, 210.55.155.0/24^24-29, 210.55.104.0/22^22-29, 210.55.100.0/22^22-29, 202.37.181.0/24^24-29, 202.37.72.0/24^24-29, 202.36.70.0/24^24-29, 202.27.204.0/24^24-29, 202.89.32.0/19^19-29, 202.6.5.0/24^24-29, 202.49.141.0/24^24-29, 203.89.160.0/19^19-29, 202.7.5.32/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 210.55.230.0/24^24-29, 210.55.214.0/24^24-29, 210.55.169.0/24^24-29, 210.55.155.0/24^24-29, 210.55.104.0/22^22-29, 210.55.100.0/22^22-29, 202.37.181.0/24^24-29, 202.37.72.0/24^24-29, 202.36.70.0/24^24-29, 202.27.204.0/24^24-29, 202.89.32.0/19^19-29, 202.6.5.0/24^24-29, 202.49.141.0/24^24-29, 203.89.160.0/19^19-29, 202.7.5.32/29, 202.7.6.32/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050307 source: NZRR

1 0

telstra clear
by Garrett Stoupe 06 Mar '05

06 Mar '05

Has anyone experienced network / internet related problems since Telstra clear de peered itself from wix? We are using a woosh wireless business connection, and we are experiencing some slowness, even with google. The problems started happening when Telstra clear de peered from wix It would be interesting to see if anyone else is experiencing any problems Garrett Stoupe Network And Database Administrator Cabbage Tree Press garretts(a)te.co.nz www.te.co.nz www.jobzone.co.nz www.nzcarbuys.co.nz

2 2

OT: Seeking a Book
by Anaru Hartley 05 Mar '05

05 Mar '05

Hello All, I have been looking for a way to progress my career in the Telecommunications Industry and a good friend of mine suggested that I read this particular book. I was hoping one of you individuals would be able to put me in the direction of one or might be able to lend me a copy of it. Here is a picture of the books cover: http://www50.brinkster.com/photochopnz/top.jpg Thanks in advance!

2 2

Cisco 2600 LNS help.
by Neil Fincham 05 Mar '05

05 Mar '05

Hi all, On of my clients has had a bit of a disaster and lost their config for a Cosco 2600 that they were using as an LNS for telstraclear's network, I have put the basic information back in (IP, Routes etc) but my cisco speek for LNS and Radius is non existant. Could someone cut and paste the relevent bits out of one of their routers (minus passwords and such) and send it to me. As you can imagine this is quite urgent and help would be greatly appreiciated, this is what I have at the moment;- L2TP#write terminal Building configuration... Current configuration : 1642 bytes ! version 12.3 service timestamps debug uptime service timestamps log uptime service password-encryption ! hostname L2TP ! boot-start-marker boot-end-marker ! ! voice-card 0 dspfarm no local-bypass ! aaa new-model ! ! aaa authentication login default local aaa authentication ppp default local aaa authentication ppp vpdn group radius aaa authorization network default group radius aaa accounting network default start-stop group radius aaa session-id common ip subnet-zero ! ! ! ! ip name-server 203.97.37.1 vpdn enable ! vpdn-group 1 accept-dialin protocol l2tp virtual-template 1 terminate-from hostname sp_lac ! no ftp-server write-enable ! ! ! ! ! ! ! ! ! ! ! ! syscon password XXX syscon community XXX ! ! controller E1 0/1 ! ! ! interface FastEthernet0/0 ip address XXX.XXX.XXX.XXX 255.255.255.248 speed auto half-duplex no mop enabled ! interface Serial0/0 no ip address shutdown ! interface FastEthernet0/1 description connected to EthernetLAN ip address XXX.XXX.XXX.XXX 255.255.255.248 duplex auto speed auto ! interface Virtual-Template1 ip unnumbered FastEthernet0/1 peer default ip address pool default ppp authentication chap vpdn ppp multilink ! ip classless ip route 0.0.0.0 0.0.0.0 XXX.XXX.XXX.XXX permanent ip route 203.98.24.0 255.255.255.0 XXX.XXX.XXX.XXX permanent ip route 203.98.25.0 255.255.255.0 XXX.XXX.XXX.XXX permanent no ip http server ! ! snmp-server community public RO snmp-server enable traps tty snmp-server manager ! radius-server host XXX.XXX.XXX.XXX auth-port 1812 acct-port 1813 radius-server key XXXXXXXXXX ! control-plane ! ! ! ! ! ! ! ! line con 0 line aux 0 line vty 0 4 ! ! ! end Thanks for any help. No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.6.2 - Release Date: 4/03/2005

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 03 Mar '05

03 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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 all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS24347 as-name: NZRR-AS24347 descr: Intergen descr: WIX peering at '202.7.0.121' descr: see Citylink RT job #1990 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24347 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dwayne.bace(a)intergen.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050304 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24347 descr: Route set advertised to AS9439 by Intergen - AS24347 members: 202.126.80.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dwayne.bace(a)intergen.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050304 source: NZRR

1 0

tradme etc
by Simon Lyall 03 Mar '05

03 Mar '05

Interestign wee article: http://www.nzherald.co.nz/index.cfm?c_id=5&ObjectID=10113474 Somebody might know this fior sure but doesn't AT&T (trademe's upstream) connect to APE? Just I can't see trademe's routes being advertised there. -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

7 6

How fair practice is this; is it spam? - Orcon Response
by Craig Whitmore 03 Mar '05

03 Mar '05

This has been posted on Behalf of Orcon MD by Craig Whitmore --- There appears to have been a serious mis-understanding between Barry and Orcon on this matter Orcon has NOT spammed Barry's customers, and Barry's post is very mis-leading. I will clarify Orcon's position, and lay out the facts, and then I suggest that Barry and Orcon take this matter offline as it is not something that needs to be discussed in NZNOG. Orcon has not, and never will: a) Spam potential customers seeking to provide them services b) Poach customers deliberately from wholesale customers, as a significant portion of our revenue comes from wholesale. What has happened is that our marketing department has been in MUTUAL contact with the owner of a single website, and came to an arrangement whereby we would receive free advertising on the person's website in return for providing free web-hosting and domain name registration. Our marketing department was not aware that this website owner was actually a customer of a customer of Barry's. The website owner has contacted their provider (a customer of a Barry's), and told them that they were moving to us, and the provider and Barry have come to the knee-jerk reaction that we are trying to poach customers. This is absolutely NOT the case. Once Barry made us aware of the issue, Barry's account manager tried to point out that end users are free to choose whichever web hosting provider they want, and that sometimes we lose customers to our wholesale hosting customers and vice-versa - this does NOT mean we are poaching customers or spamming people. However, our account manager communicated this to Barry in a less than elegant manner, and via email, after I had specifically asked that Barry be called so that the situation could be discussed and explained rationally. It is NOT our desire that Barry be upset, This is a SINGLE website owner who had prior discussions with our marketing department, and this conflict has only just been brought to our attention. Thanks for reading NZNOGer's - thanks for your time. Regards Seeby Woodhouse MD Orcon Internet -----Original Message----- From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Friday, March 04, 2005 2:23 PM To: nznog(a)list.waikato.ac.nz Subject: [nznog] How fair practice is this; is it spam? ok.... how fair is this... I purchase telehousing from orcon and register domains through them. They have spammed one of my customers offering to host their website free of charge in return for advertising space on their website. After hearing this I emailed my account manager at orcon and this was his response. "As Im sure you are aware, Orcon also runs hosting, and as such, from a marketing perspective we have to treat other web hosting companies as competition, even if they are buying wholesale services from us. All other ISP's do the same - Telecom actively market to our customers for all ISP services even though we purchase a massive amount of wholesale services off them. " Is this spam/fair practice? Seeing as they could obtain a list of these domains in their database (as they're the registrar for this domain) Kindest Regards Barry Murphy _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

problems with NTP on bigben?
by Simon Blake 03 Mar '05

03 Mar '05

Anybody else observed that bigben gained about 19 years at about 1:25pm this arvo? $ date Tue Jan 1 14:54:33 NZDT 2002 $ /usr/sbin/ntpdate -q truechimer.waikato.ac.nz server 130.217.76.32, stratum 2, offset -0.001089, delay 0.04276 1 Jan 14:49:38 ntpdate[17537]: adjust time server 130.217.76.32 offset -0.001089 sec $ /usr/sbin/ntpdate -q bigben.clix.net.nz server 203.167.224.60, stratum 1, offset 619315199.998172, delay 0.03613 1 Jan 14:49:55 ntpdate[17540]: step time server 203.167.224.60 offset 619315199.998172 sec - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

13 20