- NZNOG - lists.nznog.org

Any Telecom mail admins here?
by Juha Saarinen 01 May '06

01 May '06

Getting SORBS-induced message bounces from Telecom's mail servers due to that erroneous dial-up listing. I'm probably not the only one. -- Juha Saarinen www.geekzone.co.nz/juha www.computerworld.co.nz

3 4

Re: [nznog] Sorbs blocking addresses
by Matthew Sullivan 01 May '06

01 May '06

Craig Humphrey wrote: >Thanks Matthew. > > As an update because of the problems I have just caused new zonefiles for the DUHL zone to be created with only the test entry until the update is complete. (Why I didn't think of that before I'll never know). Regards, Mat

1 0

Re: [nznog] Sorbs blocking addresses
by Craig Box 01 May '06

01 May '06

> I'm assuming this means that all customers sending their own mail will > now have to use the xtra smtp servers? On that subject, I notice that etrn.iconz.co.nz has (probably recently) started using SORBS's dynamic DNS blacklist, and I've had reported e-mail complaints from Xtra and TelstraClear DSL customers today. Generally, when we find this happening, we contact the sysadmin on the remote end and advise them that they are likely blocking a whole set of e-mail they want to receive - harder when it's an ISP. With Xtra's Port 25 push, it could be that ICONZ have decided to have a flag day, forcing everyone wishing to communicate with them, running a (small business) mail server on a DSL connection, to now use their upstream ISP's mail server - losing the ability to diagnose mail routing after it disappears "into the black box". Is this the future? Craig

4 3

Sorbs blocking addresses
by Kerry 01 May '06

01 May '06

Hello, would seem that there is an issue here... We are now getting Xtra based customers with perminant mail delivery failures. Netblock: 210.55.172.0/23 (210.55.172.0-210.55.173.255) Record Created: Mon May 1 13:22:39 2006 GMT Record Updated: Mon May 1 13:22:39 2006 GMT Netblock: 210.55.170.0/23 (210.55.170.0-210.55.171.255) Record Created: Mon May 1 13:22:39 2006 GMT Record Updated: Mon May 1 13:22:39 2006 GMT Netblock: 210.55.174.0/24 (210.55.174.0-210.55.174.255) Record Created: Mon May 1 13:22:40 2006 GMT Record Updated: Mon May 1 13:22:40 2006 GMT $ nslookup 210.55.174.1 Server: . Address: 172.20.0.2 Name: 210-55-174-1.ipnets.xtra.co.nz Address: 210.55.174.1 I'm assuming this means that all customers sending their own mail will now have to use the xtra smtp servers? Cheers, kerry

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 May '06

01 May '06

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: AS37999 as-name: NZRR-AS37999 descr: TVNZ descr: APE peering at '192.203.154.22' descr: see Citylink RT job #5301 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS37999 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)tvnz.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060502 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS37999 descr: Route set advertised to AS9560 by TVNZ - AS37999 members: 202.89.4.0/22^22-29, 202.36.33.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)tvnz.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060502 source: NZRR

1 0

The New Zealand Network Operators' Group
by Donald Neal 01 May '06

01 May '06

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. The group is intended to facilitate discussion among operators of networks in New Zealand, as described in the list's Acceptable Use Policy, which appears later in this posting. Conference Work is just beginning towards our annual conference for 2007. 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://www.nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 900 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

Steaming Event
by Webmaster 30 Apr '06

30 Apr '06

Operators may be interested to know that Radio NZ is running a large streaming event this Saturday 6 May. Music 101 (www.radionz.co.nz/music101) will be broadcast live from Bar Bodega in Wellington, and we'll be providing enhanced audio and video for the event as it also includes live music performances. We'll be offering the following Video: 56 K, 128K, 384K, 768K at all our servers (US and local) 2M will only be offered locally (customers whose ISPs do not peer will not havce access to this). And for Audio: 256K stereo (this is not a typo). This is addition to our usual 48 K stream. As is usual for these events the best performance for your customers can be obtained by peering with the servers located at the NZ exchanges. Limited NZ bound capacity will be available from the US server. Radio NZ will peer with anyone who has connectivity where we do - at APE, PNIX or WIX. We do not charge peers for access to our content. regards, Richard Hulse

2 1

Re: [nznog] QSI / "industry" DSL problems caused by3.5mbit upgrades?
by Simon Allard 27 Apr '06

27 Apr '06

> With this service limitation I can easily see how Quicksilver could > potentially be affected more than Ihug, Iconz, Xtra and Orcon. I would > guess that the average user profile on Quicksilver would tend towards > higher bandwidth usage whereas the typical Xtra (etc) user would > probably use less bandwidth. > > Unfortunately if this view I have is correct then I don't see an end to > problems unless either the average Quicksilver user profile changes -or- > Telecom changes the PVC limitation. I am curious to know what effect offering free national traffic has on the QSI DSL Network. In my experience offering free anything in this environment Telecom has created causes nothing by problems.

5 6

Re: [nznog] QSI / "industry" DSL problems caused by 3.5mbit upgrades?
by Regan Murphy 26 Apr '06

26 Apr '06

>>Just curious if any other ISPs are suffering from supposed "industry wide" >>throughput issues on the Telecom DSL network caused by telecom "upgrading too >>many customers to 3.5mbit without upgrading their network"? Well for me the problem started before any customers were upgraded and the problem has continued well through the upgrade - I now have an automatically upgraded 3.5Mbps connection and speeds are no better/worse. I have been suffering poor performance on QSI for quite some time now. My initial post to the helpdesk via their webpage was submitted on March 14 - I had been having problems for weeks before that though. This is the response I received: "I have spoken to the network staff and they let me know that a 2Mb connection can drop as low as 24Kbps especially at peak times as this is the nature of the UBS service that telecom offers." I was, at that time, on the 2Mbps service and I was having problems even running terminal sessions to my office (which is five hops away on a 10 Mbps connection via APE). Attempting a download resulted in speeds between 7KB/sec and 30KB/sec typically. This was only noticed during peak times - 6pm to 11pm. I tried a download at 5am one morning and it ran almost at full speed. A friend of mine recently changed from Orcon to QSI. He is on an exchange on the other side of AKL from me. On the Thursday (with Orcon) he was sustaining a 220KB/sec download from the linux mirror at citylink. On the Friday when he was changed over to QSI he couldn't get better than 80KB/sec from the same source and he has had speed problems since. He changed about 2-3 weeks ago. I initially assumed that the problems were due to oversubscription cause by the Telecom changes to the DSL (I figured they bought the changes in early) and this is the line I have been given talking to the QSI helpdesk. As changing providers is a painful (and expensive) process I've been reluctant to switch without knowing for sure where the problem lay. -- Regan

8 8

Re: [nznog] QSI / "industry" DSL problems caused by3.5mbit upgrades?
by Regan Murphy 26 Apr '06

26 Apr '06

Yes, thanks to Mark for replying. This additional information makes me less likely to attribute the blame to Quicksilver for these problems. > 1) We currently have a project underway to increase our Private > Virtual Circuit (PVC) size from Telecom to manage future forecasted growth. > Telecom > controls the dimension of this PVC and constrains its size to 24kbit/s > per customer. >>Yet at the same time, customers of Ihug, Iconz, Orcon and Xtra are all able to get much higher rates... With this service limitation I can easily see how Quicksilver could potentially be affected more than Ihug, Iconz, Xtra and Orcon. I would guess that the average user profile on Quicksilver would tend towards higher bandwidth usage whereas the typical Xtra (etc) user would probably use less bandwidth. Unfortunately if this view I have is correct then I don't see an end to problems unless either the average Quicksilver user profile changes -or- Telecom changes the PVC limitation. -- Regan

1 0