- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '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: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '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: route: 202.154.128.0/19 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 202.154.128.0/19 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR --- PREVIOUS OBJECT: route: 203.96.16.0/20 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 203.96.16.0/20 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR --- PREVIOUS OBJECT: route: 203.96.48.0/20 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 203.96.48.0/20 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '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: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

MX2 with SPF
by Joel van Velden 29 Oct '05

29 Oct '05

Hi all I've been having a problem lately of getting far too much spoofed email being sent with my email address directly to our secondary mx which tries delivering it to our primary which 550's it (unknown user) and thus I get the bounce. To solve this I thought about doing the SPF thing for our domains, but this wouldn't solve the above problem unless the secondary mx does SPF as well. Because of various reasons we are using an ISPs seconday mx server for our domains, and thus have no control of that servers configuation. What i'm really asking is, does anybody know of someone selling a secondary mx service with SPF enabled? Cheers Joel van Velden

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '05

27 Oct '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: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '05

27 Oct '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: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR

1 0

NZNOG 2006 - October Update.
by Simon Lyall 26 Oct '05

26 Oct '05

1. Dates. The conference is now less than 5 months away, from 22 March to 24 March, just before the Wellington ICANN meeting Call for Papers close next week, if you wish to have your talk given full consideration then please send us something before then. Squeezing in after that date will be much harder. http://www.nznog.org/cfp.html Even if you only send us a brief description then your presentation will still be considered. 2. Sponsorship. We wish to apologise to those people who have emailed us and not heard back. Due to various factors we have not got back to you yet, this is being worked on and should hopefully be sorted out soon. :( 3. General. We are in the process of finalizing venues for the main conference, dinners and the like. Most of it is looking fairly promising if not always as cheap as we would hope. We have had several good talk proposals, however there is still some room in the programme especially for lightning talks. Wednesday is looking more and more like becoming a full or half day of normal conference. Finally if you have any general, off the wall or other ideas please email us now as things will start being settled soon. We have had a couple of good suggestions already. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Re: [nznog] Voip response
by chris＠archnetnz.com 26 Oct '05

26 Oct '05

Anyone want to tell him, or can I???? Callplus, own iTalk and slingshot.. so yes, they most likly do use the same ISDN's as iTalk... $9.95 a month is quite a good deal for an Auckland number, I would just like a Wellington number.. but who knows when that will be avilable... > Sipserve doesn't use the same PRI's, they have their own, provided by > callplus (afaik). > > The standard italk prefix of 974 is assigned to callplus in all area codes > except 06, where it is taken by TelstraClear. > > iTalk told everyone in September that it would be ready in 2 or 3 months, > yet people are still sending typical "where the hell is it" emails/forum > posts, and also have the nerve to go "oh btw, we want to pay less." > > People are assholes. > > > ________________________________________ > From: Barry Murphy > Sent: Thursday, 27 October 2005 4:20 p.m. > To: will(a)excom.net.nz > Subject: [nznog] Voip response > > Hi, > > Many of you (over 30 people) were interested in a response to my VoIP > DDI's question to the NZNog. I should have responded earlier but I was > hoping more providers would email me back, plus I've been on holiday the > last week (wahoo!). > > Well unfortunately I only had 2, unless I missed any, but it would seem > italk.co.nz and sipserve.co.nz are the only 2 providers and with number > ranges in 09 & 04. > > Italk - well they not yet selling 04 numbers from what I understand, they > working on the billing platform still. I'm currently using their 09 > service and it's great, call quality is perfect, fax over IP works, prices > aren't bad. > > Sipserve - these guys say they doing 04, however I know someone that > emailed them a week ago to get some and they still haven't + their support > is a bit slow and their system doesn't support fax over IP. > > One other thing to think about is sipserve don't offer free Auckland > dialing, this costs 0.05c p/m I believe, plus their DDI ranges are > delivered over the same PRI's as the slingshot italk service. > > Well that's it, if anyone has any further details, please advise. > > Thanks > Kindest Regards > Barry Murphy > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

2 1

Re: [nznog] Voip response
by Will Steele 26 Oct '05

26 Oct '05

Both of you misread what I said - I said Sipserve. Barry said Sipserve used the same PRI's as slingshot/italk/callplus, which, I apologize if I'm wrong, but I'm pretty sure that that is not the case. And as I said, they said 2 or 3 months, so give them that at least :) Will -----Original Message----- From: chris(a)archnetnz.com [mailto:chris(a)archnetnz.com] Sent: Thursday, 27 October 2005 5:00 p.m. To: Will Steele Subject: Re: [nznog] Voip response Anyone want to tell him, or can I???? Callplus, own iTalk and slingshot.. so yes, they most likly do use the same ISDN's as iTalk... $9.95 a month is quite a good deal for an Auckland number, I would just like a Wellington number.. but who knows when that will be avilable... > Sipserve doesn't use the same PRI's, they have their own, provided by > callplus (afaik). > > The standard italk prefix of 974 is assigned to callplus in all area codes > except 06, where it is taken by TelstraClear. > > iTalk told everyone in September that it would be ready in 2 or 3 months, > yet people are still sending typical "where the hell is it" emails/forum > posts, and also have the nerve to go "oh btw, we want to pay less." > > People are assholes. > > > ________________________________________ > From: Barry Murphy > Sent: Thursday, 27 October 2005 4:20 p.m. > To: will(a)excom.net.nz > Subject: [nznog] Voip response > > Hi, > > Many of you (over 30 people) were interested in a response to my VoIP > DDI's question to the NZNog. I should have responded earlier but I was > hoping more providers would email me back, plus I've been on holiday the > last week (wahoo!). > > Well unfortunately I only had 2, unless I missed any, but it would seem > italk.co.nz and sipserve.co.nz are the only 2 providers and with number > ranges in 09 & 04. > > Italk - well they not yet selling 04 numbers from what I understand, they > working on the billing platform still. I'm currently using their 09 > service and it's great, call quality is perfect, fax over IP works, prices > aren't bad. > > Sipserve - these guys say they doing 04, however I know someone that > emailed them a week ago to get some and they still haven't + their support > is a bit slow and their system doesn't support fax over IP. > > One other thing to think about is sipserve don't offer free Auckland > dialing, this costs 0.05c p/m I believe, plus their DDI ranges are > delivered over the same PRI's as the slingshot italk service. > > Well that's it, if anyone has any further details, please advise. > > Thanks > Kindest Regards > Barry Murphy > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Voip response
by Will Steele 26 Oct '05

26 Oct '05

Sipserve doesn't use the same PRI's, they have their own, provided by callplus (afaik). The standard italk prefix of 974 is assigned to callplus in all area codes except 06, where it is taken by TelstraClear. iTalk told everyone in September that it would be ready in 2 or 3 months, yet people are still sending typical "where the hell is it" emails/forum posts, and also have the nerve to go "oh btw, we want to pay less." People are assholes. ________________________________________ From: Barry Murphy Sent: Thursday, 27 October 2005 4:20 p.m. To: will(a)excom.net.nz Subject: [nznog] Voip response Hi, Many of you (over 30 people) were interested in a response to my VoIP DDI's question to the NZNog. I should have responded earlier but I was hoping more providers would email me back, plus I've been on holiday the last week (wahoo!). Well unfortunately I only had 2, unless I missed any, but it would seem italk.co.nz and sipserve.co.nz are the only 2 providers and with number ranges in 09 & 04. Italk - well they not yet selling 04 numbers from what I understand, they working on the billing platform still. I'm currently using their 09 service and it's great, call quality is perfect, fax over IP works, prices aren't bad. Sipserve - these guys say they doing 04, however I know someone that emailed them a week ago to get some and they still haven't + their support is a bit slow and their system doesn't support fax over IP. One other thing to think about is sipserve don't offer free Auckland dialing, this costs 0.05c p/m I believe, plus their DDI ranges are delivered over the same PRI's as the slingshot italk service. Well that's it, if anyone has any further details, please advise. Thanks Kindest Regards Barry Murphy

1 0

Voip response
by barry＠unix.co.nz 26 Oct '05

26 Oct '05

Hi, Many of you (over 30 people) were interested in a response to my VoIP DDI's question to the NZNog. I should have responded earlier but I was hoping more providers would email me back, plus I've been on holiday the last week (wahoo!). Well unfortunately I only had 2, unless I missed any, but it would seem italk.co.nz and sipserve.co.nz are the only 2 providers and with number ranges in 09 & 04. Italk - well they not yet selling 04 numbers from what I understand, they working on the billing platform still. I'm currently using their 09 service and it's great, call quality is perfect, fax over IP works, prices aren't bad. Sipserve - these guys say they doing 04, however I know someone that emailed them a week ago to get some and they still haven't + their support is a bit slow and their system doesn't support fax over IP. One other thing to think about is sipserve don't offer free Auckland dialing, this costs 0.05c p/m I believe, plus their DDI ranges are delivered over the same PRI's as the slingshot italk service. Well that's it, if anyone has any further details, please advise. Thanks Kindest Regards Barry Murphy

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Oct '05

26 Oct '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: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.36.205.128/27^27-29, 202.68.87.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Oct '05

26 Oct '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: AS24181 as-name: NZRR-AS24181 descr: TheLoop descr: WIX peering at '202.7.0.140' descr: see Citylink RT job #3454 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24181 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24181 descr: Route set advertised to AS9439 by TheLoop - AS24181 members: 202.49.20.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Oct '05

25 Oct '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: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050624 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051026 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Oct '05

24 Oct '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: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 218.101.56.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-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)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 218.101.56.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-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)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051025 source: NZRR

1 0

New phish for Ebay
by Drew Broadley 23 Oct '05

23 Oct '05

It suggests you have a product that someone is interested in, and requests you to login to Ebay. It's quite comical as it mentions at the top "Your registered name is included to show this message originated from eBay. Learn more.", yet my 'registered' name isn't anywhere in the message. Second comical part, is the hosting produces a http://home.ro/ popup advert. Not the best i've seen but the idea is quite different. Just a heads up. - Drew

2 1

IP multicast redundancy support
by Roger Hicks 21 Oct '05

21 Oct '05

Does anyone have knowledge of a device for supporting IP multicast redundacy; arbitrating between multiple producers so that only one IP stream is being output I'm not sure of the correct terminology (or even if such a device exists) but it should have 2 or more inputs and multicast out one of the inputs. If that input goes away, it should switch to another input. Pls email me directly Thanks for your help Roger

1 0

Re: [nznog] Anyone know anything about fitnessgear.co.nz ?
by Regan Murphy 21 Oct '05

21 Oct '05

from returns page: http://www.fitnessgear.co.nz/page.aspx?code=returns Returns can delivered to the following address during normal business hours: FitnessGear.co.nz Product Returns, C\- Concept Fitness 39 Sir William Ave, East Tamaki Auckland search on concept fitness: http://www.fitforever.co.nz/ -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Friday, 21 October 2005 10:24 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Anyone know anything about fitnessgear.co.nz ? Hi there Does anyone have any information about fitnessgear.co.nz? I can't find the company on Companies Offfice (Can't even find the registered owner anywhere) Whois details gives invalid phone number Number on Website is a call centre and all they can give me is an email address to email and can't help me any further they say. Website gives me no help, no legal company name or anything. When ordering no GST Number, and if you choose to send in a Cheque it gives no details where to send it to And.. they sent 1000's of advertising spams this morning with 1/2 of them to invalid email accounts/addresses to lots of .NZ email addresses. Thanks Craig

5 4

Anyone know anything about fitnessgear.co.nz ?
by Craig Whitmore 20 Oct '05

20 Oct '05

Hi there Does anyone have any information about fitnessgear.co.nz? I can't find the company on Companies Offfice (Can't even find the registered owner anywhere) Whois details gives invalid phone number Number on Website is a call centre and all they can give me is an email address to email and can't help me any further they say. Website gives me no help, no legal company name or anything. When ordering no GST Number, and if you choose to send in a Cheque it gives no details where to send it to And.. they sent 1000's of advertising spams this morning with 1/2 of them to invalid email accounts/addresses to lots of .NZ email addresses. Thanks Craig

2 1

Re: [nznog] um, whats wrong with whois?
by Tim John 20 Oct '05

20 Oct '05

Hi Andy, I posed the same question to NZRS the other day and they have confirmed that 'working as intended' means the WhoIs service is operating normally. The issue with the 404 error is due to limiting restrictions enforced by the Registry on received WhoIs requests and the effect it is having on Domainz, means they are exceeding these restrictions in a particular timeframe. Again, it's worth pointing out that this is the Public WhoIs Interface and anyone using it is subject to the same restrictions. NZRS - please feel free to shoot me down if this is the wrong interpretation .... Tim -----Original Message----- From: Andy Linton [mailto:asjl(a)citylink.co.nz] Sent: Friday, 21 October 2005 11:55 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] um, whats wrong with whois? David Zanetti wrote: > On Thu, 2005-10-20 at 11:53 +1300, Simon Byrnand wrote: > > >>I'm getting the same 440 error doing lookups through the Domainz >>website.... surely they count as a registrar ? Very annoying... > > > Working as intended. Would it be possible from someone at NZRS to clarify what "Working as intended" means? Thanks, andy _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

4 3

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '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: route-set: AS9439:RS-ROUTES:AS64544 descr: advertised to AS9439 by Ecentric - AS64544 members: 202.135.231.0/28^28-29, 202.135.231.32/28^28-29, 202.135.231.176/28^28-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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050928 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64544 descr: advertised to AS9439 by Ecentric - AS64544 members: 210.48.103.144/28^28-29, 202.126.87.128/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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '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: route-set: AS9439:RS-ROUTES:AS18400 descr: Route set advertised to AS9439 by Xtreme - AS18400 members: 218.101.2.0/23^23-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18400 descr: advertised to AS9439 by Xtreme Networks Limited - AS18400 members: 203.171.32.0/20^20-29, 218.101.2.0/23^23-29, 202.36.162.0/24^24-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: soa(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Re: [nznog] xtra
by VeNoMouS 20 Oct '05

20 Oct '05

if you really need to pump the email out setup a smtp for xtra.co.nz to mta5-rme.xtra.co.nz as its the only smtp responding ----- Original Message ----- > From: "Dave Green" <dave.green(a)paradise.net.nz> > To: <nznog(a)list.waikato.ac.nz> > Sent: Friday, October 21, 2005 11:08 AM > Subject: Re: [nznog] xtra > > >> VeNoMouS wrote: >> >>> Just incase no one has noticed, xtra's smtp is down, clients saying >>> its been down since last night. >> >> Hard not to really. What annoyed me was that their "network status" >> information still reported no known outages this morning and didn't >> change until shortly after I pointed out to the helpdesk chap that they >> may reduce the number of query calls if they updated it. >> >> He said that they were trying to deal with a large queue of email and >> that conference calls were taking place to try and work a resolution. >> >> Dave >> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> >> >

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '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: AS23959 as-name: NZRR-AS23959 descr: DTS descr: WIX peering at '202.7.0.143' descr: see Citylink RT job #3531 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23959 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '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 DELETED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0