- NZNOG - lists.nznog.org

Re: [nznog] Unbudled Bitstream
by J S Russell 12 Aug '04

12 Aug '04

On Thu, 12 Aug 2004, Dave - Dave.net.nz wrote: > not really wanting to say this but... thats assuming that you use it > 24hrs a day, the average user(not my average use, or probably yours > but...) doesnt use their net connection 24hrs a day, assuming the > average user does 8 hrs a day(a fairly high average I'd have throught), > thats 12kbytes a second, which is just about fine. I'd have throught the > average user would be somewhere nearer to 4 or maybe 6 hours a day, but > anyway. Well, see now, my home machines actually tend to keep doing things via the internet, even when I'm not physically sitting in front of them and looking at stuff in a browser. In fact, I (and most of the people reading this list) tend to be use _less_ traffic at home than "power users" - because all our personal high-bandwidth p2p apps and audio/video streams and suchlike live on servers which tend to be connected to ISP core networks, or live in ISP co-location space. 12K/sec is "fine"? Great! I think I'd like to listen to Twisted Radio's high-quality web stream, and also .... oh, wait, I was going to talk about some other common internet stuff there, but I've pretty much already used up most of 12K/sec. Well, perhaps I'll turn all that stuff off, plunk myself down on the couch, fire up the xbox and pull up one of r2's high-quality video streams to watch on ... oh, no, I guess I sure as hell won't be doing that. And neither will anyone else at 256Kbits/sec, flat rate or not-flat rate. Because 256Kbits/sec is obscenely slow. A key point here is not to think about what most people currently do with their internet connection, it's to think about what they _could_ be doing if they had _real_ broadband. The lost opportunities from this lack of connectivity is the thing that people ought to really be mad about. A 256Kbits/sec bit rate, of which you will be allowed to sustain a fraction thereof, on a service which can do _8Mbits/sec_ is frankly, a load of ass. There are test residential FTTP installations in prodution elsewhere_right now_. True optical to the home - not science fiction, if you live in the right place you can just Go Buy One. I can see that from Telecom if it gets here - 10GBits/sec to the home, and you get a full 10Gbits/sec if you connect to Telecoms content server domains or gaming realms, and if you go anywhere else ... well, as you've pointed out, 12K/sec is "fine" isn't it? Speaking of which, I must point out yet again, The Telecom ADSL product somehow can do a full 8Mbits/sec speed flat-rate _FREE_ connection to one national platform (Jetstreamgames) yet somehow is "not provisioned" to do more than 10GB/month to another national platform (Any Non-Telecom ISP). Hell, TCNZ, I'll just run some optical cable over to wherever your JSG servers are, and .. oh, no, can't do that either. Why? "Policy", last time I asked. As I said in an earlier post to NZNOG, it's just Business As Usual. And you can't blame Telecom for it, they're just trying to protect their stock price and dividend, it's what they're legally obliged to do! It is, however, the job of the government to point at corporate interests and say "Oi! You're in a monopolistic position with regards to this resource, and we're _ordering_ you to do something that you naturally wouldn't do and open it up to others!" That didn't happen, though, did it? I am beginning to agree with other users on this thread. Let's put some alternate infrastructre in place and get some competition going. Woosh wireless manage to offer a flat-rate 256Kbits/sec connection over _cellular_ equipment for chrissakes! No cables AND it's portable! ICONZ Wireless on Waiheke offers 2Mbits/sec symmetical wireless connections, the largest of which offer 10GB of _international_ access for less than $99/month and throws in free totally unmetered line-speed flat-rate domestic access and that's _RETAIL_, not a pretend wholesale product. Sod this ADSL thing - it's damage - route around it. JSR -- John S Russell | Big Geek | Doing geek stuff.

2 1

Telecom a Joke
by Terence 12 Aug '04

12 Aug '04

Three weeks ago I put an order in for Jetstream, for our Richmond Office. Just thought I would call to find out what was happening with the connection. Xtra said that they have run out of ports at the exchange and that I am in a waiting queue for one to come available. They will give no time or date, or if they are going to upgrade the exchange. How much profit did they make last year ?. What about some re investment. Disclaimer : These figures could be wrong 795 mil profit 4 mil people. Annoyed Terence Blyth Managing Director Computer Technologies Ltd 19 Alma Street Box 584, Nelson New Zealand Phone ++ 643 545 9001 Fax ++ 643 545 9002 www.ctec.co.nz PRIVILEGED - PRIVATE AND CONFIDENTIAL This email and any files transmitted with it are intended solely for the use of the addressee(s) and may contain information, which is confidential or privileged. If you receive this email and you are not the addressee (or responsible for delivery of the email to the addressee), please disregard the contents of the email, delete the email and notify the author immediately.

1 0

Re: [nznog] Unbudled Bitstream
by Hamish MacEwan 12 Aug '04

12 Aug '04

Hurrah JSR! > A key point here is not to think about what most people currently do > with their internet connection, it's to think about what they _could_ > be doing if they had _real_ broadband. The lost opportunities from > this lack of connectivity is the thing that people ought to really be > mad about. Exactly. I've met a number of people who deny they have even a Claytons broadband connection in ADSL, since they are unable to use it for fear of exceeding their capacity to enrich Telecom. The 10GB cap on the leisurely 256K we are to be doled out amounts to about a 14% duty-cycle. And I'm bemused as to the location of the "unbundling" in UBS? It looks more and more like it it well and truly bundled to avoid the inconvenience of competition for Telecom. > I am beginning to agree with other users on this thread. Let's put some > alternate infrastructre in place and get some competition going. You ever disagreed with that? Hope truly springs eternal... > Sod this ADSL thing - it's damage - route around it. <grin>, a line from a Digital Strategy response I'm working on: "The Internet was designed for resilience and its ability to route around damage is legend. This ability has often been interpreted to indicate that whatever the Internet routes around is damage, as in the classic, "The Internet interprets censorship as damage and routes around it." The Internet may provide a way to route around the legacy "Last mile," and the closed proprietary Central Office." > JSR Hamish. -- The world isn't worse. It's just that the news coverage is so much better.

1 0

Unbudled Bitstream
by Steve Schmidt 11 Aug '04

11 Aug '04

I heard that TCNZ have changed the details of the UBS service and that now it will be a capped 10gb service. Anyone else know anything about this. Regards Steven Schmidt. CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it.

9 8

RE: [nznog] Unbudled Bitstream
by Seeby Woodhouse 11 Aug '04

11 Aug '04

Although the 'new' UBS DSL deal is not as good as the original deal, nor as flexible, I should point out that the traffic limit of 10GB that Telecom has imposed is an AGGREGATE traffic limit across all the users, not a 10GB limit PER user. Currently our JetStream Starter customer base does not use anywhere near 10GB of traffic on average, so hopefully this isn't something that we'll have to worry about. (crosses my fingers that we don't ever go over our limit, and that the overage fees don't get set at 20c/meg) Cheers Seeby -----Original Message----- From: Keith Davidson [mailto:keith(a)wise.net.nz] Sent: Thursday, August 12, 2004 2:32 PM To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Unbudled Bitstream Certainly appears to be the case. See www.orcon.co.nz/company/press/54318/ text follows below. Keith Davidson ________________ "11th August 2004 - New Bitstream plans to remain unchanged On the 27th of July 2004, Orcon released a new, truly affordable 256k Flat rate residential broadband service for $49.95/mth based on the released 'Bitstream' wholesale DSL specification from Telecom. Two week's after Orcon's product release, Telecom have decided to change the specification by imposing a 10GB average traffic limit per user, and an agreement not to promote static IP addresses with the service. Orcon will honor the initial plans offered to customers at our cost, despite the changes that have been made. Orcon is currently the second largest provider of JetStream DSL in NZ, and was the first company to negotiate a Wholesale Services Agreement (WSA) with Telecom for a broad range of services. Orcon has been eagerly awaiting the wholesale DSL portion of the WSA to be finalised, as we believe that we can offer the consumer significantly better deals than are currently available. The moment Telecom told us of their planned Wholesale DSL (UBS) product in early July, we created pricing plans for our own DSL product (based on the Wholesale DSL components we would purchase from Telecom) and set about launching an advertising campaign based on these initial figures - taking a bet that Telecom's final wholesale pricing to us would either be the same or better than the initial figures. The supposed 'final' UBS specification was released by Telecom on 26th July, and as we had guessed, was slightly better than their initial proposal. Our ads for flat rate 256k DSL with a static IP address at the all-inclusive price of $49.95 started to come out a day later. As far as we were concerned, Telecom had finalised the wholesale deal for DSL that they would offer to us, and we had successfully launched our product. After a couple of weeks, with many thousands of advertising dollars already spent, and several hundred new DSL customer signed up, Telecom told us that the UBS specification they had come up with was going to be changed. Specifically, the 'flat-rate' nature of the product and the ability to advertise static IP addresses. We don't know whether the fact that Orcon came out with our flat-rate and static IP address product had anything to do with Telecom changing the specification to withdraw these capabilities, however no other ISPs had come out with any other offering, and therefore our product was seen as a 'reference' product in the market. However - As a champion for affordable broadband, Orcon has decided to wear the 10GB excess traffic charges at our cost so that we can continue to offer a flat rate product, and we will also honor the static IP address for users who have already signed up from an existing promotion wherever possible. We believe that it should the ISPs choice whether to offer Static IP addresses or provide a truly flat-rate service. Seeby Woodhouse MD Orcon Internet Limited" ----- Original Message ----- From: "Steve Schmidt" <sschmidt(a)compass.net.nz> To: "nznog" <nznog(a)list.waikato.ac.nz> Sent: Thursday, August 12, 2004 11:58 AM Subject: [nznog] Unbudled Bitstream > > I heard that TCNZ have changed the details of the UBS service and that > now it will be a capped 10gb service. Anyone else know anything about > this. > > Regards > Steven Schmidt. > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Orcon Internet Prefix List Updaet (2004-08-11)
by Craig Whitmore 10 Aug '04

10 Aug '04

For all those peering with Orcon Internet (AS17746) nationally, please update your prefix lists with the following networks (also in attached file). Added: ip prefix-list orcon-national permit 60.234.0.0/16 le 24 Regards, Craig Whitmore Orcon Internet Network Operations

2 1

6509 Chassis
by J S Russell 09 Aug '04

09 Aug '04

Does anyone on this list have access to a bare Cisco 6509 chassis (preferably also with at least one 240V PSU module installed if possible, but it's not necessary) which they'd be willing to part with in exchange for some combination of dollars and/or a populated Cisco 5513 chassis (Sup2, three 24x10/100 planes, spare Sup1) and/or a lot of beer? If you have one, or could help me at all, please do let me know. JSR -- John S Russell | Big Geek | Doing geek stuff.

1 0

nzWireless peering update
by Andrew Tipton 09 Aug '04

09 Aug '04

For those peering with us on WIX, we have added a new prefix (203.110.28.0/23). Full list: ip prefix-list nzwireless description nzWireless WIX prefixes <andrew.tipton(a)nzwireless.co.nz> ip prefix-list nzwireless seq 10 permit 210.54.151.0/24 le 29 ip prefix-list nzwireless seq 20 permit 203.110.28.0/23 le 29 -- Andrew Tipton Network Engineer nzWireless Ltd (04) 471-0905 (0211) 595-561

1 0

RE: [nznog] APE Funnys - ISC Peering
by Craig Spiers 09 Aug '04

09 Aug '04

Yep, we do.. They requested we configure it about two months ago.. Actually, That about fits the picture.. Don't think it happened before the passwords were configured.. -----Original Message----- From: Simon Lyall [mailto:simon(a)darkmere.gen.nz] Sent: Tuesday, 10 August 2004 1:08 p.m. To: Craig Spiers Subject: Re: [nznog] APE Funnys - ISC Peering Do you have md5 passwords setup? or perhaps they think you do? On Tue, 10 Aug 2004, Craig Spiers wrote: > Anyone else seeing these errors? Happens every few minutes. Has been for a > couple of months now.. (ISC is the only peer I see these with - both > connections) > > > .Aug 10 12:42:51.304 +1200: %BGP-5-ADJCHANGE: neighbor 192.203.154.99 Down > BGP Notification sent > .Aug 10 12:42:51.304 +1200: %BGP-3-NOTIFICATION: sent to neighbor > 192.203.154.99 4/0 (hold time expired) 0 bytes > .Aug 10 12:43:23.328 +1200: %BGP-5-ADJCHANGE: neighbor 192.203.154.99 Up > > Cheers > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 09 Aug '04

09 Aug '04

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. --- OBJECT BELOW CREATED: aut-num: AS24111 as-name: NZRR-AS24111 descr: NZwireless descr: initially peering at '202.7.1.69' descr: see Citylink RT job #929 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24111 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR --- OBJECT BELOW CREATED: route: 203.110.28.0/23 descr: Route for NZwireless - AS24111 origin: AS24111 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR --- OBJECT BELOW CREATED: route: 210.54.151.0/24 descr: Route for NZwireless - AS24111 origin: AS24111 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24111 descr: Route set advertised to AS9439 by NZwireless - AS24111 members: 203.110.28.0/23^23-29, 210.54.151.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 09 Aug '04

09 Aug '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 10 Aug 2004 10:56:55 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0408101055140.13273(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.27.48.0/21^21-24, 202.49.152.0/21^21-24, 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 changed: rpsl-admin(a)ape.net.nz 20040810 source: NZRR

1 0

TEST - PLEASE IGNORE
by J S Russell 08 Aug '04

08 Aug '04

I've suddenly realised that I haven't seen any NZNOG posts for some time. So this is a test. Please ignore. JSR -- John S Russell | Big Geek | Doing geek stuff.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Aug '04

08 Aug '04

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. --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.27.48.0/21^21-24, 202.49.152.0/21^21-24, 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Aug '04

08 Aug '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Mon, 9 Aug 2004 14:08:39 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0408091401400.8879(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW DELETED: aut-num: AS4768 as-name: NZRR-AS4768 descr: University of Auckland descr: initially peering at '192.203.154.114' descr: see Citylink RT job #752 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS4768 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040731 source: NZRR --- OBJECT BELOW DELETED: route-set: AS9560:RS-ROUTES:AS4768 descr: Route set advertised to AS9560 by University of Auckland - AS4768 members: 130.216.0.0/16^16-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040731 source: NZRR --- OBJECT BELOW DELETED: route: 130.216.0.0/16 descr: Route for University of Auckland - AS4768 origin: AS4768 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040731 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Aug '04

08 Aug '04

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. --- OBJECT BELOW CREATED: aut-num: AS9431 as-name: NZRR-AS9431 descr: University of Auckland descr: initially peering at '192.203.154.114' descr: see Citylink RT job #752 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9431 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR --- OBJECT BELOW CREATED: route: 130.216.0.0/16 descr: Route for University of Auckland - AS9431 origin: AS9431 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS9431 descr: Route set advertised to AS9560 by University of Auckland - AS9431 members: 130.216.0.0/16^16-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR

1 0

Accessing www.symantec.com
by Paul Adshead 04 Aug '04

04 Aug '04

Is anyone else having access problems accessing www.symantec.com? Does anyone know if there is any DOS in progress? Thanks, Paul Adshead.

4 3

The New Zealand Network Operators' Group
by Donald Neal 04 Aug '04

04 Aug '04

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. Meetings We're now working towards our next annual conference, to be hosted by The WAND group in Hamilton on February 2nd to 4th, 2005. See http://www.nznog.org/ for details of this year's conference, which drew something over 120 participants. Also see http://auckland.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.ape.net.nz/ for details of the Auckland Peering Exchange and those connected there. See http://www.wix.net.nz/ for the Wellington Internet Exchange. About This Mailing List This list has around 690 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. 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 ihug Ltd. 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/archives/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 Donald Neal |Diplomacy - Look what Technical Specialist |the university gave me. Operations Engineering | Integration & Services Division +----------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "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." ------------------------------------------------------------------------------

2 1

IANA IPv4 allocations and bogon update: 71/8, 72/8
by Rob Thomas 03 Aug '04

03 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- Hi, team. [ Apologies to those of you who receive this note in multiple forums. ] The numerous Team Cymru bogon projects have been updated as of 02 AUG 2004 to reflect the following IANA allocation made on 02 AUG 2004: 71/8 Aug 04 ARIN 72/8 Aug 04 ARIN IANA allocations change over time, so please check regularly to ensure you have the latest filters if you are not using the bogon BGP feed(s). We do announce updates to the bogon projects to sundry lists, such as the bogon-announce list. We can not stress this point strongly enough - these allocations change. If you do not adjust your filters, you will be unable to access perhaps large portions of the Internet. Worse yet, you may end up blocking access for people who transit through you. Please do not apply any filters or blocks to your network without carefully considering the ramifications of doing so. As a point of reference, the Team Cymru master Bogon Reference Page can be found here: <http://www.cymru.com/Bogons/> A quick summary of the documents and projects that have been updated include the following: HTTP The Bogon List - <http://www.cymru.com/Documents/bogon-list.html> The Text Bogon Lists - <http://www.cymru.com/Documents/bogon-bn-nonagg.txt> - <http://www.cymru.com/Documents/bogon-bn-agg.txt> Secure BIND Template - <http://www.cymru.com/Documents/secure-bind-template.html> Secure IOS Template (Cisco) - <http://www.cymru.com/Documents/secure-ios-template.html> Secure BGP Template (Cisco) - <http://www.cymru.com/Documents/secure-bgp-template.html> Secure JUNOS Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-template.htm> Secure JUNOS BGP Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-bgp-template.htm> Ingress Prefix Filter Templates, Loose and Strict (Cisco) - <ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix-Filter-Templates/> Ingress Prefix Filter Template, Loose (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix-filter-loose.htm> Ingress Prefix Filter Template, Strict (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix-filter-strict.htm> BGP Bogon route-server for AUTOMATED updates of bogon filters - All bogon route-server peers have already received the appropriate BGP prefix updates. - <http://www.cymru.com/BGP/bogon-rs.html> RADb fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#radb> RIPE NCC fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#ripe> DNS Bogon (bogons.cymru.com) zone - <http://www.cymru.com/Bogons/index.html#dns> Monitoring Bogon prefix monitoring - <http://www.cymru.com/BGP/robbgp-bogon.html> Bogus ASN monitoring - <http://www.cymru.com/BGP/asnbogusrep.html> Please feel free to contact Team Cymru <team-cymru(a)cymru.com> with any comments, questions, or concerns. Thanks! Rob, for Team Cymru. - -- Rob Thomas http://www.cymru.com ASSERT(coffee != empty); -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQQ/hFlkX3QAo5sgJAQEV6gP+PRRJozjAEJ180JTE9KQD+kFsd0n2tQOX TNpOiE4BtjaTfwsZhzgKNYtzRsYdAwL1/zLpWOyjK3J+tllUasxQ+lsDKqGjTVii wATUj+2/JV9VGb14AVkkMz4mSEiNw1rNJxDvy+P40yyECPegWS93Em75DQjrUm3X o5SD7dgJPbI= =2ydr -----END PGP SIGNATURE-----

1 0

RE: [nznog] NTP weirdness
by Eustace, Glen 02 Aug '04

02 Aug '04

Just an FYI, I seem to have fixed our problem. I have added restrict 0.0.0.0 mask 0.0.0.0 nopeer nomodify notrust notrap Which probably should have been there all the time. Win 2k3 is announcing itself in such a way that before the 'restrict' we tried peering with it. Not sure why this wasn't an issue with 4.1.1 Now we simply reply and take no further action. 16:13:30.023910 202.50.245.234.2823 > 130.123.2.99.ntp: v3 sym_act strat 0 poll 17 prec -6 16:13:30.023960 130.123.2.99.ntp > 202.50.245.234.2823: v3 sym_pas strat 2 poll 17 prec -17 (DF) [tos 0x10] -- .*. | Glen Eustace, Infrastructure Development Engineer /V\ | Information Technology Services PN460, Turitea, (/ \) | Massey University, Palmerston North, New Zealand. ( ) | Ph: +64 6 356 9099 x 81005, Fax: +64 6 350 5607, Mob: +64 27 450 0321 ^^-^^ |------------------------------------------------------------

1 0

NTP weirdness
by Glen Eustace 02 Aug '04

02 Aug '04

Hi all, I am need of some help with our public ntp setup. We upgraded our servers from RH7.3 ->FC1 (ntp4.1.1->4.1.2) last week and I have now had several reports of people who are seeing our servers apparently port scanning them :-( I didn't change the config for ntp but can confirm that after their server first asks for the time, we start sending them packets on high UDP ports. The complaints that I have been investigating are Windows servers but that may be a red-herring. I have previously treated ntp as a black-box but am obviously going to have to understand things better. Any help would be appreciated. Glen -- .*. | Glen Eustace, Infrastructure Development Engineer /V\ | Information Technology Services PN460, Turitea, (/ \) | Massey University, Palmerston North, New Zealand. ( ) | Ph: +64 6 356 9099 x 81005, Fax: +64 6 350 5607, ^^_^^ | Mob: +64 27 4 500 321 ------+-----------------------------------------------------

1 0

Fw: ISP Details for inclusion inside DSE ADSL Manuals
by Dan Clark 01 Aug '04

01 Aug '04

This may be of interest to some ADSL operators on here. Kind Regards Dan Clark ----- Original Message ----- From: "Chris Day" <chris.day(a)dse.co.nz> To: <adsl(a)lists.unixathome.org> Sent: Monday, August 02, 2004 5:10 PM Subject: ISP Details for inclusion inside DSE ADSL Manuals > Hi all. > > We are in the process of updating the user manuals and quick start guides for our DSE branded ADSL products. If you are an ISP reselling Telecom's (PPPoA) ADSL services and you would like details to be published in our manuals, please respond to chris.day(a)dse.co.nz with the following information: > > Sales Email: > Sales Phone: > Support Email: > Support Phone: > Weblink: > Company Name: > Primary DNS: > Secondary DNS: > Incoming Mail Server: > Outgoing Mail Server: > > As this this data will eventually be reprinted in all DSE branded ADSL Modems, Routers and Filters, we will also need authorization to redistribute it to consumer market. > > Kind Regards, > > > > Chris Day > Senior Buyer - DSE(NZ)Ltd > email: chris.dau(a)dse.co.nz > Physical: 221 Bush Rd, Albany, Auckland, New Zealand > Postal: Private Bag 102-903, N.S.M.C., Auckland, NZ. > Phone: +64-9-414-2844 - Fax: +64-9-414-2801 - Cell: +64-21-745-411 > > -- > This message is part of the NZ ADSL mailing list. > see http://unixathome.org/adsl/ for archives, FAQ, > and various documents. > To unsubscribe: send mail to majordomo(a)lists.unixathome.org > with "unsubscribe adsl" in the body of the message > >

2 1

ConceptNET Limited Peering Update
by Craig Spiers 01 Aug '04

01 Aug '04

To all those peering with ConceptNET Nationally over APE - we have updated our prefix list. Changes: Added 203.21.31.0/24 Full Prefix List: ip prefix-list conceptnet description ConceptNET Domestic Routes <craig(a)concept.net.nz> ip prefix-list conceptnet seq 5 permit 202.150.96.0/20 ip prefix-list conceptnet seq 10 permit 202.127.8.0/22 ip prefix-list conceptnet seq 15 permit 203.97.44.0/24 ip prefix-list conceptnet seq 20 permit 202.49.250.0/24 ip prefix-list conceptnet seq 25 permit 202.50.176.0/24 ip prefix-list conceptnet seq 30 permit 203.21.31.0/24 Regards, Craig Spiers ConceptNET Limited

1 0

[nzlug] Problems connecting to Telstra Broadband service in
by Jo 30 Jul '04

30 Jul '04

Matthew could you reply back to me re your post in nz.general. Have something to same which cant be done publicly. Real knowledge is to know the extent of one's ignorance. ---Confucius

1 0

Update to ihug prefix list.
by Simon Lyall 28 Jul '04

28 Jul '04

Ihug has updated the list of networks we are advertising across APE and elsewhere. We have added several new networks today. The complete prefix list and the changes are below, they are also available from: http://www.ihug.net/ihug-prefix-list Current Prefix list is: ip prefix-list ihug-networks description ihug peering prefix-list contact: noc(a)ihug.co.nz : Updated 2004-07-29 ip prefix-list ihug-networks permit 192.107.113.0/24 ip prefix-list ihug-networks permit 202.21.130.0/24 ip prefix-list ihug-networks permit 202.21.136.0/23 le 24 ip prefix-list ihug-networks permit 202.36.44.0/24 ip prefix-list ihug-networks permit 202.36.94.0/23 le 24 ip prefix-list ihug-networks permit 202.37.136.0/24 ip prefix-list ihug-networks permit 202.37.182.0/24 ip prefix-list ihug-networks permit 202.37.187.0/24 ip prefix-list ihug-networks permit 202.46.160.0/20 le 24 ip prefix-list ihug-networks permit 202.49.33.0/24 ip prefix-list ihug-networks permit 202.49.46.0/23 le 24 ip prefix-list ihug-networks permit 202.49.48.0/24 ip prefix-list ihug-networks permit 202.49.59.0/24 ip prefix-list ihug-networks permit 202.49.63.0/24 ip prefix-list ihug-networks permit 202.49.88.0/23 le 24 ip prefix-list ihug-networks permit 202.49.144.0/24 ip prefix-list ihug-networks permit 202.49.148.0/23 le 24 ip prefix-list ihug-networks permit 202.49.176.0/23 le 24 ip prefix-list ihug-networks permit 202.49.178.0/24 ip prefix-list ihug-networks permit 202.49.180.0/23 le 24 ip prefix-list ihug-networks permit 202.49.186.0/24 ip prefix-list ihug-networks permit 202.49.240.0/22 le 24 ip prefix-list ihug-networks permit 202.49.249.0/24 ip prefix-list ihug-networks permit 202.50.84.0/24 ip prefix-list ihug-networks permit 202.50.103.0/24 ip prefix-list ihug-networks permit 202.50.188.0/22 le 22 ip prefix-list ihug-networks permit 202.50.255.0/24 ip prefix-list ihug-networks permit 203.96.192.0/19 le 24 ip prefix-list ihug-networks permit 203.109.128.0/17 le 24 ip prefix-list ihug-networks permit 203.118.128.0/18 le 24 ip prefix-list ihug-networks permit 203.173.128.0/17 le 24 ip prefix-list ihug-networks permit 210.55.110.0/24 ip prefix-list ihug-networks permit 210.55.184.0/24 ip prefix-list ihug-networks permit 210.55.202.0/23 le 24 ip prefix-list ihug-networks permit 210.55.248.0/21 le 24 The following networks were added on 2004-07-29: ip prefix-list ihug-networks permit 202.49.33.0/24 ip prefix-list ihug-networks permit 202.49.46.0/23 le 24 ip prefix-list ihug-networks permit 202.49.48.0/24 ip prefix-list ihug-networks permit 202.49.63.0/24 ip prefix-list ihug-networks permit 202.49.178.0/24 ip prefix-list ihug-networks permit 202.50.188.0/22 le 22 ip prefix-list ihug-networks permit 203.96.192.0/19 le 24 ip prefix-list ihug-networks permit 210.55.110.0/24 -- Simon Lyall <simon.lyall(a)ihug.co.nz> Senior Engineer, Ihug Ltd, Auckland, NZ

1 0

[nzlug] Problems connecting to Telstra Broadband service in Wellington via a DSE XH1151 Broadband Router? (fwd)
by Matthew Poole 22 Jul '04

22 Jul '04

This is fairly OT, but I figure that the likelihood of someone on here being able to help him is higher than the other lists he posted to. ---------- Forwarded message ---------- Date: Fri, 23 Jul 2004 17:13:00 +1200 From: Chris Day <chris.day(a)dse.co.nz> Reply-To: nzlug(a)linux.net.nz To: adsl(a)lists.unixathome.org, broadband(a)lists.unixathome.org, nzlug(a)linux.net.nz Subject: [nzlug] Problems connecting to Telstra Broadband service in Wellington via a DSE XH1151 Broadband Router? Over the last couple of weeks we have seen an increase in customer calls regarding the use of the DSE XH1151 Broadband Router with the Telstra Wellington Broadband service. For some unknown reason some routers are suddenly dropping the connection. In almost all cases the customer indicates the router has been working fine. It seems to us the properties of the service has somehow changed and we are trying to contact Telstra to resolve the issue but have been unsuccessful in making any meaningful contact. If you work for Telstra or know of anyone in a position of authority that can help us, it would be most appreciated if you could contact ross.hamblin(a)dse.co.nz We are eager to work with Telstra and our manufacturers to resolve this issue. Kind regards, Chris Day Senior Buyer DSE(NZ)Ltd ------------------------------------------------------------------- To remove yourself from this list, email nzlug-request(a)linux.net.nz with "unsubscribe" in the body of the message.

1 0