- NZNOG - lists.nznog.org

Cisco 3550 replacement
by Jacky Lam 19 Feb '06

19 Feb '06

Hi all, I'm currently looking for a CPE that can replace the Cisco 3550 we currently deploy in our network. Key features that I'm looking for are as follows: Hierarchical QOS Traffic shaping/policing L3VPN functionality(VRF-lite) BGP OSPF dot1q some sort of spanning tree Any help would be really appreciated, Jacky

2 1

Help: Questionaire...
by Mark Foster 18 Feb '06

18 Feb '06

Hi Team, I'm doing some legwork in aid of my presentation at NZNOG06 Conference. If the reader is what you might call 'Helpdesk' and would be interested in answering a brief questionaire about your job, please drop me an email off list. All information collected will be used in aid of the presentation, noones details will be disclosed to anyone else, it'll remain anonymous, etc. I'm particularly after perspective from those who work in tech support, either for ISPs or larger companies. I may have something for 'NOC type people' at a later stage, too. Thanks for your help Mark.

1 0

Re: [nznog] NZNOG Digest, Vol 38, Issue 12
by ganda y situmorang 17 Feb '06

17 Feb '06

On Sat, 18 Feb 2006 12:00:04 +1300 nznog-request(a)list.waikato.ac.nz wrote: > Send NZNOG mailing list submissions to > nznog(a)list.waikato.ac.nz > > To subscribe or unsubscribe via the World Wide Web, >visit > http://list.waikato.ac.nz/mailman/listinfo/nznog > or, via email, send a message with subject or body >'help' to > nznog-request(a)list.waikato.ac.nz > > You can reach the person managing the list at > nznog-owner(a)list.waikato.ac.nz > > When replying, please edit your Subject line so it is >more specific > than "Re: Contents of NZNOG digest..." > > > Today's Topics: > > 1. Notification of NZRR Database changes > (NZRR Database Notifications) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 17 Feb 2006 16:01:02 +1300 >From: NZRR Database Notifications <rpsl-admin(a)nzix.net> > Subject: [nznog] Notification of NZRR Database changes > To: nznog(a)list.waikato.ac.nz > Message-ID: <E1F9vri-0007kB-LU(a)zidane.citylink.co.nz> > > > > 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:AS24005 > descr: advertised to AS9560 by SafeNZ Networks >Limited - AS24005 > members: 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20051125 > source: NZRR > > > REPLACED BY: > > route-set: AS9560:RS-ROUTES:AS24005 > descr: advertised to AS9560 by SafeNZ Networks >Limited - AS24005 > members: 202.56.32.0/20^20-29, > 202.56.48.0/21^21-29, > 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20060217 > source: NZRR > > --- > PREVIOUS OBJECT: > > route-set: AS9439:RS-ROUTES:AS24005 > descr: advertised to AS9439 by SafeNZ Networks >Limited - AS24005 > members: 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20051125 > source: NZRR > > > REPLACED BY: > > route-set: AS9439:RS-ROUTES:AS24005 > descr: advertised to AS9439 by SafeNZ Networks >Limited - AS24005 > members: 202.56.32.0/20^20-29, > 202.56.48.0/21^21-29, > 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20060217 > source: NZRR > > > > ------------------------------ > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > End of NZNOG Digest, Vol 38, Issue 12 > ************************************* ======================================================================================== Ikuti Lomba Puisi Online Jawa Timur, dapatkan hadiah menarik setiap bulannya dan hadiah total senilai 60 juta rupiah hanya di http://www.plasa.com (Khusus Jawa Timur) ========================================================================================

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 16 Feb '06

16 Feb '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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060217 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060217 source: NZRR

1 0

SMTP Greylisting
by Craig Whitmore 15 Feb '06

15 Feb '06

I have been playing around with greylisting recently on a couple of test domains and it works pretty well (reduces the number of spam coming from malwared machines who don't retry sending their spam by over 90% before any spam checkers get to it), but I've noticed a number of real mail NZ servers not knowing what a 451 SMTP message is, and they treat it like a fail and they don't send the message again. (Yes I know I can whitelist good known NZ SMTP Serversto not Greylist from them) If anyone else has tried greylisting before , or has any comments on it, let me know. Thanks Craig

10 12

Providers located at Northcote DC
by Barry Murphy 15 Feb '06

15 Feb '06

Hey there beer drinkers, Is anyone here hosting equipment at Vectors Data Center on Northcote Road, Auckland? I currently use Orcon as my bandwidth provider (both national & international) but am looking for backup routes, so if you have connectivity to either Telstra or direct to APE at the facility, please give me a hola offlist. Cheers Barry

1 0

Re: [nznog] SMTP Greylisting
by Ewen McNeill 14 Feb '06

14 Feb '06

In message <20060214230142.GZ26689(a)citylink.co.nz>, Simon Blake writes: >We've been using greylisting here for the last six months, and it's made >a huge difference to the amount of noise [.... through other filters ....] >I would set your timeout to be really low - 15 seconds would be as >effective as 30 minutes, as far as I can see. I can't help wondering how long this beneficial effect of greylisting will last. It's not _that_ difficult for a spammer to ask their purchased botnet to run its spam list twice. Worst case they need twice as many bots. It's not like it's hard to buy 0wn3d machines these days. Those with greylisting enabled get the message once; those without may well get it twice. Bonus. If greylisting becomes relatively common that's exactly what I'd expect spammers to do. And viruses to do. (Viruses can simply follow the same PRNG or discovered list twice. Perhaps 30-60 minutes apart. Not much extra work, for much more effectiveness.) So what do we do next? Defer twice before accepting? Give up on greylisting? And then get two copies (or three copies)? Seems to me that the end result of this particular "arms race" is that mail delivery gets permanently delayed (since no one can "safely" turn off greylisting without getting multiple copies of the junk), and we end up no further forward on the spam/virus problem. Not that I really see an option which doesn't end up "email becomes even more useless" over a relatively short period of time. Frankly I'm amazed it's lasted this long. We've had 5+ years of what is effectively a sustained denial-of-service attack on email. Ewen

2 1

Webcasting Heads Up
by Richard Naylor 13 Feb '06

13 Feb '06

(Wearing my R2 hat) It appears we will be webcasting the 2nd reading of the NZ Sign Language Bill on 23 Feb 06 at around 3pm (after Parliament's Question Time). This will last for approximately 1 hour and has a reasonable audience in the low hundreds. (they packed the House last reading as well and overflowed into two rooms). For those who are unaware, the NZ Sign Language Bill will establish NZ Signing as the third Official Language of NZ, so the passage of the legislation is of interest to the Hearing Impaired community both in NZ and internationally. As before we will run 2 sets of streams - the main camera mix plus a fixed shot of the sign language interpreters. As we are not bandwidth constrained, we will also be running a full set of streams (56kbps, 128kbps, 384kbps and 2Mbps) and they will be served off servers at the main NZ IX points, plus the USA. CityLink advise me that anyone wanting help with a quick peering session with my routers should speak to Andy Linton. I'm happy to set up short duration/temp sessions. In addition, tomorrow we will be making Bloomberg TV available on our servers. This premiere news service will be of interest to the financial community. At the moment the streams are limited to 256kbps, but please note the "at the moment". The streams are available across all servers without restriction. For those interested, the link is http://www.r2.co.nz/meta/bloombergtv.asx Thanks and happy viewing. Rich

1 0

Re: [nznog] SMTP Greylisting
by Jeremy Strachan 13 Feb '06

13 Feb '06

I'm ignoring your email, if its an important topic you'll send beer to grab my attention first. -----Original Message----- From: Simon Lyall [mailto:simon(a)darkmere.gen.nz] Sent: Tuesday, 14 February 2006 1:41 p.m. To: nznog Subject: Re: [nznog] SMTP Greylisting On Tue, 14 Feb 2006, Craig Whitmore wrote: > If anyone else has tried greylisting before , or has any comments on > it, let me know. Personally I find greylisting a pain. I am subscribed to a couple of lists that use it and it's annoying when my reply to the list takes half an hour to get through instead on 2 minutes. One important thing to watch for is that for larger sites the server that first tries to send your email might not be the one that tries to resend it later. Greylisting sites will thus block the email for a while until the sending site gets lucky and uses the same machine twice in a row. Generating random error messages to sending sites is just asking for trouble IMHO. You really can't determine exactly they will act and how long they will take to retry to send the message. Any delay is 100% your fault although most people using greylisting seem keen to push the blame to the sending site. It's the equivalent of ignoring someone when they first email/call you and saying "If it's important they'll ring back" . Not very polite and possibly not providing the best service to customers. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Feb '06

12 Feb '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: route-set: AS9439:RS-ROUTES:AS9236 descr: advertised to AS9439 by AMP - AS9236 members: 203.118.136.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jimi.wallace(a)ampcapital.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060213 source: NZRR

1 0