- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '05

31 Jul '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: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS24385 announce AS23754 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 20050801 source: NZRR REPLACED BY: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS7657 announce AS23754 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 20050801 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '05

31 Jul '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: AS23754 as-name: NZRR-AS23754 descr: CityLink descr: SMARTLINX3 peering at '218.100.26.3' descr: see Citylink RT job #1927 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 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 20050331 source: NZRR REPLACED BY: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS24385 announce AS23754 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 20050801 source: NZRR

1 0

The New Zealand Network Operators' Group
by Donald Neal 31 Jul '05

31 Jul '05

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference We're in the early stages of planning our next conference, which is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 850 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search With site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '05

31 Jul '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:AS7657 descr: advertised to AS9439 by Ihug - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 198.32.71.0/24^24-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR

1 0

NASA TV Query...
by Clint Jeffrey 30 Jul '05

30 Jul '05

Thanks to all whom responded.Wally has been in contact.. Ta Thanks. Clint - VK3CSJ.

1 0

NASA TV Feed on OPTUS B1...query
by Clint Jeffrey 29 Jul '05

29 Jul '05

Hello to anyone that maybe still using this forum.I'm trying to get in contact with Wally ZL1VWM about the question below:- Hi Wally I saw your call sign on the LygnSat site in regards to "NASA TV", for a long time now I have wished for the powers that be to place a feed on one of our Optus Satellites, in fact I'd even take a subscription to Foxtel if they'd organized a feed for NASA TV. So far nothing has come through, as member of "The Planetary Society" I have even emailed messages requesting someone to organize a NASA TV feed here in Australia. I've just discovered that Optus B1 has a feed albeit on New Zealand, I'm wondering if you would know if I can see this feed here in Melbourne? Currently I have a 90cm dish on a small motor control using a Humax 5400 receiver, I tried a quick look for Optus B1 the other night with out any luck though. Also I see the feed seems to be off the internet rather than any actual feed from a live NASA source so to speak, is that true? If so how good a quality are the images, at least what I'm try to say, it that I currently look at NASA TV off the internet, it's pretty horrible to say the least, picture keeps updating and then digitizes and then comes good for a few seconds and goes all horrible again, I have ADSL at 512 download, it's probably my computer that needs the upgrading, but if there is finally a feed off a Satellite visible in our own sky then bloody fantastic!....I'll go for that! Any thoughts on this Wally. Many Thanks Clint Jeffrey - VK3CSJ P.S I'm on my work computer at present, if you can, you can also reply to my home email address which is vk3csj(a)netspace.net.au

2 1

RE: [nznog] NASA TV Feed on OPTUS B1...query
by Jeremy Strachan 29 Jul '05

29 Jul '05

Done. ________________________________ From: Clint Jeffrey [mailto:vk3csj(a)netspace.net.au] Sent: Saturday, 30 July 2005 8:51 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] NASA TV Feed on OPTUS B1...query Hello to anyone that maybe still using this forum...I'm trying to get in contact with Wally ZL1VWM about the question below:- Hi Wally I saw your call sign on the LygnSat site in regards to "NASA TV", for a long time now I have wished for the powers that be to place a feed on one of our Optus Satellites, in fact I'd even take a subscription to Foxtel if they'd organized a feed for NASA TV. So far nothing has come through, as member of "The Planetary Society" I have even emailed messages requesting someone to organize a NASA TV feed here in Australia. I've just discovered that Optus B1 has a feed albeit on New Zealand, I'm wondering if you would know if I can see this feed here in Melbourne? Currently I have a 90cm dish on a small motor control using a Humax 5400 receiver, I tried a quick look for Optus B1 the other night with out any luck though. Also I see the feed seems to be off the internet rather than any actual feed from a live NASA source so to speak, is that true? If so how good a quality are the images, at least what I'm try to say, it that I currently look at NASA TV off the internet, it's pretty horrible to say the least, picture keeps updating and then digitizes and then comes good for a few seconds and goes all horrible again, I have ADSL at 512 download, it's probably my computer that needs the upgrading, but if there is finally a feed off a Satellite visible in our own sky then bloody fantastic!....I'll go for that! Any thoughts on this Wally. Many Thanks Clint Jeffrey - VK3CSJ P.S I'm on my work computer at present, if you can, you can also reply to my home email address which is vk3csj(a)netspace.net.au

1 0

Anti Spam Legislation vs Spam realities and ISP staffing
by Mark Foster 29 Jul '05

29 Jul '05

http://www.nzherald.co.nz/index.cfm?c_id=5&ObjectID=10338203 My review of this article noted this paragraph: --8<-- Internet users will complain in the first instance to their internet provider about spam email, and the Department of Internal Affairs will act as an internet watchdog if the matter is taken further. --8<-- Now did I get the wrong end of the stick here, or is this saying that the onus of the ISP that provides connectivity to the Spam Receiver to act on complaints - or the DIA will be hounding them? Shouldn't the source ISP, and not the destination, be the people responsible for dealing with their own spam sources? I wrote a bit of a commentary of my own: http://www.blakjak.net/node/view/261 However wonder if this has come to the attention of anyone else yet... The first thing that jumps into my head is that ISPs are going to wind up having to do all the investigative legwork on the complaints they receive - and not many ISPS I know of are staffed to support this. Antispam costs for all providers going up - and probably going up in relation to the size of their customer base. Hmmm.... Mark.

3 3

RE: [nznog] Multi-point VPN around NZ to a central location ( Wellington)
by Kerry Milestone 28 Jul '05

28 Jul '05

Mmmmm....... Chrome bits...... Yes. Realistically though... Nissan350z. ________________________________ From: Drew Broadley [mailto:drew(a)corrupt.co.nz] Sent: Friday, 29 July 2005 2:19 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Multi-point VPN around NZ to a central location ( Wellington) Hi all, I'm representing a company where the requirements are going to need a large amount of nodes around the country where they will all require (at least) a dedicated 128kbps connection to a central "nerve" located on WIX and additional redundancy on the central system at another location, ultimately somewhere on the APE. We would ideally not approach Telecom directly at the moment through a buzz-word junkie sales person at the moment as I want a realistic perspective on this, not someone who will just say yes so they can afford to chrome more parts on their Audi. If you have any available options, could you please contact me off list. Cheers, Drew

2 1

Multi-point VPN around NZ to a central location (Wellington)
by Drew Broadley 28 Jul '05

28 Jul '05

Hi all, I'm representing a company where the requirements are going to need a large amount of nodes around the country where they will all require (at least) a dedicated 128kbps connection to a central "nerve" located on WIX and additional redundancy on the central system at another location, ultimately somewhere on the APE. We would ideally not approach Telecom directly at the moment through a buzz-word junkie sales person at the moment as I want a realistic perspective on this, not someone who will just say yes so they can afford to chrome more parts on their Audi. If you have any available options, could you please contact me off list. Cheers, Drew

1 0