- NZNOG - lists.nznog.org

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

08 Dec '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. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 9 Dec 2004 12:48:25 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0412091247560.28480(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo - AS64597 members: 202.53.189.128/29, 210.48.101.64/27^27-29, 210.48.109.224/27^27-29, 202.174.161.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: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo - AS64597 members: 202.53.189.128/29, 210.48.101.64/27^27-29, 210.48.101.112/29, 210.48.109.224/27^27-29, 202.174.161.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: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041209 source: NZRR

1 0

[Apnic-announce] Protecting historical records in the APNIC database (fwd)
by John Tran 05 Dec '04

05 Dec '04

Hi all, Just following from last week emails. Here is an announcement that could be interested to some of you. If you wish to know what happening in the APNIC community please subscribe to apnic-annouce mailing list which is available at: http://www.apnic.net/community/lists/index.html Regards son ---------- Forwarded message ---------- Date: Mon, 06 Dec 2004 14:56:11 +1000 From: APNIC Secretariat <secretariat(a)apnic.net> Reply-To: apnic-talk(a)apnic.net, secretariat(a)apnic.net To: apnic-announce(a)apnic.net Subject: [APNIC Members] [Apnic-announce] Protecting historical records in the APNIC database Dear colleagues, The APNIC Secretariat will implement a policy on 14 December 2004 to protect historical records in the APNIC database from unverified transfers, abuse, and unauthorised use. The proposal document, presentation, minutes, and discussion are available at: http://www.apnic.net/docs/policy/proposals/prop-018-v001.html Please note, after 14 December 2004, the maintainer of all historical resource registrations will be changed to "APNIC-HM". To ensure the integrity of information in the APNIC Whois Database, APNIC will not update historical information in the APNIC Whois Database unless the resource holder can establish its right to the resources and enters a formal agreement with APNIC, either as a member or as a non-member account holder. Further details and all supporting documentation will be available on 14 December. If you have any questions regarding this policy, please contact the APNIC helpdesk at: E-mail: helpdesk(a)apnic.net Phone: +61-7-3858-3188 Fax: +61-7-3858-3199 Regards ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ---------------------------------------------------------------------- See you at APNIC 19 Kyoto, Japan, 21 - 25 February 2005 www.apnic.net/meetings ----------------------------------------------------------------------

1 0

APRICOT 2005
by Neil Fenemor 05 Dec '04

05 Dec '04

Can anyone who is going to be attending the next APRICOT in Kyoto, Japan, please drop me a message off list. I wish to discuss beer (just to keep this somewhat near being on topic) Cheers neil

1 0

Viruses originating from Xtra network
by Lesley Walker 05 Dec '04

05 Dec '04

Please forgive me if this is off-topic, I don't know anywhere else to ask for help. How does one get the attention of the abuse people at Xtra? A mailing list that I administer is being attacked by viruses that originate at a Jetstream address (details below). I sent email to abuse(a)xtra.co.nz a couple of days ago and have not had the courtesy of a response, not even a "sod off" answer, or even a bounce. The viruses come in batches from a consistent IP address - the address has changed a couple of times but I think it's the same infected machine because the messages have a consistent "look and feel". The received header looks like this: Received: from srunjn.com (210-86-89-213.jetstream.xtra.co.nz [210.86.89.213]) by [munged] with SMTP id iB1CGab26947; Thu, 2 Dec 2004 01:16:36 +1300 (NZDT) The envelope "from" appears to be randomly generated nonsense as it is different every time, but the originating IP address is consistent for each batch. The messages are designed to look like bounces from various ISPs and companies but in fact contain virus attachments. The latest originating address is 210.86.90.246, as at Sat, 4 Dec 2004 08:36:21 +1300 (NZDT) -- Lesley Walker, Wellington, New Zealand LRW(a)clear.net.nz http://home.clear.net.nz/pages/lrw http://walkinguphills.blogspot.com/

11 12

Re: [nznog] Viruses originating from Xtra network
by Lesley Walker 04 Dec '04

04 Dec '04

Glen wrote: >As one would expect, Xtra get a fair few notifications and I must admit that >I was more than a little surprised to find that their 'abuse team' are the >most responsive of all the ISPs in NZ !! They acknowledge the notifications >by automated return mail and as each incident is closed we get a closure >report. I spoke with them by phone when we were getting the system setup and >they were very supportive and helpful. Then I have to conclude that my email didn't actually get through. But I haven't received a bounce, so it must have been dropped into the bit-bucket somewhere along the way. I must admit it's easy to fall into the trap of treating email as if it were a guaranteed-delivery system so if I've maligned them unfairly I apologise, and I'll try again and see what happens. >Most of the ISPs we send the notifications to are taking them seriously and >do do something. Private companies that have no abuse, no postmaster >address etc are proving to be a pain and there are quite a few of them. I can relate to that! Thanks for your comments. Lesley.

1 0

Re: [nznog] Viruses originating from Xtra network
by Lesley Walker 03 Dec '04

03 Dec '04

Thanks to all who have commented. I will try again when I have time to wait out the infinite hold, and I may try that "Complex" number. I do understand about the need for the IVR to do the right thing for the company's needs, it just bugs the hell out of me that it keeps trying to send me to a sales dude when I'm trying to reach support people. I'm prepared for coping with call centre helpdesk people, if only I can get through to them. I know I sent them enough information to track the user when I emailed them, but what I don't know is whether anyone is paying any attention to the email. A response with a trouble ticket number would be nice, but even an auto-responder would let me know for sure that the mail got through. In the absence of a bounce, I would expect at least an auto-response. Mark Foster wrote: >Noone you talk to over the telephone is going to give you real time >support on a virus infection issue. Of course not. All I want them to do is log a trouble ticket and send it to someone who can (a) understand it, and (b) do something about it. >Their security team do deal with all valid emails to abuse@ even if they >don't acknowledge them directly. Also please bear in mind that nomatter >what ISP is involved, all customers need time to be warned, and get fixed, >before theyll have their accounts nuked. Its a tough call to take someone >off the internet when their only hope is software that needs to be >downloaded _from_ the internet... Sure. But someone who is sufficiently Internet-enabled to have Jetstream probably either has a clue or knows somebody who does, and I would hope that they just need to to be told about it. >Disclaimer: I don't represent Xtra or Telecom or anyone else except yours >truly. This is based on my experiences as an Xtra customer and someone who >has reported virus to Xtra Abuse Team many times! Accepted. >PS: The 'Dial 0' trick is a cop out. With a company as big as Xtra, you >can't realistically expect them to leave a Dial 0 option in there _and >then_ expect to keep call durations down - you wont get the answer you >want from a receptionist, will you? No, but if the IVR doesn't provide appropriate options, I expect a receptionist to be able to put me through to somebody appropriate. They're supposed to know who does what in their organisation. > If their support staff are busy, >theyre busy. Sit on hold, try again later, or email them. (And hope that >they realise their Queues are busy (and they will, theres enough software >there tracking their Queue stats) and modify staffing levels as a result >(also standard callcentre practise.) I hope I don't have to keep waiting while they go out and hire more staff. That'd be a pretty long call! :-) (The batteries in my phone woulf go flat) Thanks again. Lesley.

1 0

Broadband connectivity
by Andy Linton 03 Dec '04

03 Dec '04

While we debate the merits (?) of DSL connectivity and how to handle modem pools here's an example of a service available in Japan. The last couple of pictures tell the story! > Got my 100Mb fiber optic installed yesterday...the connection is > humming. I found the whole process very interesting and think that it > is just amazing. The actual fiber is thinner than a human hair and its > just fantastic. > free install, free for two months, unlimited traffic and no more than > $100 NZD/month. > > I am one happy man : ) > > http://www.jesse-taylor.com/new/misc_images/100mb_install/index.htm

8 8

APRICOT 2005 in Kyoto, Japan
by Philip Smith 03 Dec '04

03 Dec '04

Hi everyone, This is to let you know that the registration for APRICOT 2005 in Kyoto, Japan, from 18th to 25th February 2005 is now open. APRICOT is the Asia Pacific region's Internet operations and technology conference, and consists of workshops, tutorials, conference, as well as the 6 monthly APNIC meeting. Full information about APRICOT 2005 can be had at www.2005.apricot.net. Registration and accommodation information is at: www.2005.apricot.net/registration.html www.2005.apricot.net/accommodation.html You are encouraged to register as soon as possible as the early bird registration discount finishes on the 12th of January. Hope to see you in Kyoto early next year! philip --

1 0

Dialup / Radius
by Blair Harrison 02 Dec '04

02 Dec '04

Hi People, After all the hubbub of DSL activity of late, has anyone been having any issues with Dialup? If you are, are your upstream dialup providers putting priority into solving any dialup issues? I've talked to a few people and it seems that Telecom's IPNet dialup service seems to suffer missing RADIUS Stop records and that this activity seems to have been going on for a long time.. Has anyone ever managed to get an answer out of Telecom as to why this occurs? I'm also wondering how many missing records we're talking about here, does anyone have any actual numbers? Has it increased over the last couple of months? Missing RADIUS records seem to have been just a "fact of life" for most ISPs I know of for some time now, but I'm just wondering to what extent this occurs elsewhere.. Lately we've been noticing a somewhat increased number of missing stop records- to the point that some of our RADIUS-dependant services are suffering a few "errors" .. requiring some extra "fixes" to get around the issue.. One would think that being such a core service, every RADIUS issue ever concieved should have been eliminated years ago.. Obviously some of our national providers think otherwise.. Comments? Please feel free to reply to me offlist. Regards, Blair Harrison Systems Administrator WISE Net | http://wise.net.nz

5 5

[Fwd: IOS and Growing BGP tables]
by Andy Linton 02 Dec '04

02 Dec '04

I've not seen this discussed on nznog. ---------- Forwarded message ---------- Date: Thu, 2 Dec 2004 14:39:01 +1000 From: David J. Hughes <bambi(a)Hughes.com.au> To: Oz-ISP Mailing list <aussie-isp(a)aussie.net>, isp-australia(a)isp-australia.com Subject: [Oz-ISP] IOS and Growing BGP tables Hi, I'm posting this in an attempt to raise a bit of support. I've been arguing for a feature enhancement for IOS that will prolong the life of most Cisco routers that take a full BGP table. The growth of the table is causing concern for many major providers who can see the RAM on their lower end 7200's running out in the near future. Their default solution is not to upgrade the boxes, but to filter out the /24 advertisements. However, for many years in Australia, a /24 was the normal allocation. If they blindly filter out all the /24's then lots of networks in Australia (and other countries) will become unreachable. The proposed features allows you to filter a prefix if there is a less specific prefix already in your table (with various tuneable knobs with respect to next hop etc). Some guys at Cisco have taken this on and filed a bug / feature request for this. The more people that open a TAC case and have it linked to this bug ID the higher the priority of this request will become. It's being supported on the Cisco-NSP mailing list but I thought it worth "rattling the cage" on these lists as well. The more voices the better. The Cisco Bug ID is "CSCsa45474 : Ability to block overlapping BGP prefixes from being installed in RIB". Some history of the discussions is included below. If you have a TAC account and are so inclined, please open a new case and ask the engineer to link it to this bug ID. Thanks Bambi ... Begin forwarded message: > From: David J. Hughes <bambi(a)Hughes.com.au> > Date: 1 December 2004 10:26:18 AM > To: 'cisco-nsp' <cisco-nsp(a)puck.nether.net> > Subject: Re: [c-nsp] Growing BGP tables > > > I hope that most people on this list would open a case to try to get a > feature like this included in upcoming IOS releases. It's about the > only thing that will extend the life of your "RAM limited" routers > without breaking connectivity to historically legitimate /24 > allocations. > > > David > ... > > > On 01/12/2004, at 9:40 AM, Rodney Dunn wrote: > >> For those that have the ability to open a TAC case and they think >> this is something they could use, open a case and have the TAC >> engineer attach the case to this bug: >> >> CSCsa45474 >> Externally found enhancement defect: New (N) >> Ability to block overlapping BGP prefixes from being installed in RIB > ------ Begin forwarded message: Anything that reduces the consumption of RIB and FIB resources as a result of de-aggregation etc would be a very welcome step in the right direction. Thanks for looking into this Rodney. David ... On 24/11/2004, at 3:33 AM, Rodney Dunn wrote: > My point was that you can't do it with BGP > because you don't have a way to request a > re-advertisement from a peer when the > less specific goes away. > > There is a possiblity we could keep the > more specifics out of the RIB which would > save memory there and in the FIB. > > That being said the best that can > be done currently appears to block > the routes from going in the RIB. > We are looking to see how complex that > would be to do. > > Rodney > > > On Tue, Nov 23, 2004 at 11:11:52AM -0600, Brian Feeny wrote: >> >> >> I like this, basically all your doing is getting rid of the redundant >> information which serves no purpose other than taking up space in the >> RIB/FIB anyways. And if someone should further deaggregate or make a >> change, then the new update is going to run its algorithm against the >> current RIB all over again. >> >> >> On Nov 22, 2004, at 4:16 PM, David J. Hughes wrote: >> >>> >>> Hey Rodney, >>> >>> How about ... >>> >>> for each prefix received in update >>> for each more specific prefix in RIB >>> if RIB prefix ge /24 and same next hop as update prefix >>> drop RIB prefix >>> if update prefix ge /24 >>> for each less specific prefix in RIB >>> if RIB next hop same as update next hop >>> drop update prefix >>> >>> something like that would filter during the update and wouldn't >>> require another full copy of the table to be held. I'm sure you >>> guys could come up with something more efficient but the basic idea >>> would work wouldn't it? >>> >>> >>> David >>> ... ---- email "unsubscribe aussie-isp" to majordomo(a)aussie.net to be removed.

1 0