- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 18 Dec '05

18 Dec '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: AS9560:RS-ROUTES:AS2687 descr: Route set advertised to AS9560 by AT&T - AS2687 members: 152.158.254.0/23^23-29, 203.163.70.0/23^23-29, 152.158.213.0/24^24-29, 202.14.141.0/24^24-29, 202.14.142.0/24^24-29, 202.36.80.0/24^24-29, 202.36.195.0/24^24-29, 202.37.28.0/24^24-29, 202.37.93.0/24^24-29, 202.37.254.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.38.0/24^24-29, 202.135.48.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.86.0/24^24-29, 202.135.112.0/24^24-29, 202.135.115.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.98.0/24^24-29, 219.88.103.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: Mark.Crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050503 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.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: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051219 source: NZRR

1 0

Update: Systems Administration Miniconf, linux.conf.au 2006.
by Simon Lyall 17 Dec '05

17 Dec '05

The Systems Administration Miniconf which will be part of the linux.conf.au conference to be held in Dunedin, New Zealand in January 2006 We are pleased to announce that our programme is 95% finalised and is available online at: http://sysadmin.miniconf.org/program.html and more details of each presentation are on this page: http://sysadmin.miniconf.org/presentations.html Please note that for now the actual times of each presentation have not been finalized while we work with other miniconfs to avoid clashes. While we are no longer accepting full length talks we still have space for Lightning talks, please contact us if you are interested: http://sysadmin.miniconf.org/lightning.html Contact and Questions --------------------- Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf. If you have any questions please feel free to email the organisers at: contact @ sysadmin.miniconf.org

1 0

Re: [nznog] NZ Security Notifications
by John Martin 16 Dec '05

16 Dec '05

Brendan Murray wrote: > > > If you think there would be some value in this, please email me. > > You can find information about the nsp-security mailing list at > https://puck.nether.net/mailman/listinfo/nsp-security) > > I believe such a closed security mailing list would have a great deal of value, not only to Universities and ISP's within New Zealand (re: aka Russell Fulton) but also to Critical Infrastructure Providers, financial services too. With a great number of sources from Phishing, Pharming attacks being reported with USA and EMEA from APAC, this could also provide an early warning system and possibly assist in shutting down such activity via the participating ISP's. However, in terms of running a script through various snort databases, the issue of privacy looms and authorisation, a better answer might be to use the New Zealand nominated CERT for such operations i.e. Centre for Critical Infrastructure Protection (CCIP) locally as a central collection point etc.. To ensure anonymity etc. It would also be good to add ISC (sans.org) logs to the collective.. With compliance issues only around the corner, New Zealand is relatively unscathed by regulatory/legislation within USA, EMEA, Australia, which statistically looks like it will take a hold within the next 1-2 years. Such a group may provide guidance to organisations, not prepared for the ongoing associated issues of compliance. John Martin Security Practice Leader IBM NZ

1 0

NZ Security Notifications
by Brendan Murray 15 Dec '05

15 Dec '05

(apologies to members of members-discuss(a)internetnz.net.nz for duplication) Yesterday the topic of AusCERT came up on nznog. Many of you probably know that InternetNZ has formed a small group to look at the need/feasibility of a NZ based CERT. It is all in early days yet, but it might be a good time to start looking at some ways of improving security awareness here. We hope to raise some ideas for discussion at the nznog conference next year, but the recent email suggests we could start on some practical matters now. We would like to suggest creating a NZ security community with a nz-sec mailing list, for example. This would have the same sort of intent as the nsp-security mailing list, bringing in people with a genuine interest in security practice and incident handling. We feel that the CCIP list, while valuable, is informative rather than collaborative. The nznog list has been used for security issues where relevant, but network operations is the reason for nznog, not security management. Ultimately the list and list membership, or some variant, would become associated with a NZ CERT if one were to happen, but in the meantime InternetNZ would be happy to host and advertise a moderated list. If you think there would be some value in this, please email me. You can find information about the nsp-security mailing list at https://puck.nether.net/mailman/listinfo/nsp-security) Brendan Murray Chairing the InternetNZ NZCERT Task Force.

7 7

Re: [nznog] NZ Security Notifications
by Barry Greene (bgreene) 14 Dec '05

14 Dec '05

For those who are interested, I've got a draft of some guidelines that can be used to create a group like nsp-sec-nz. Pop me a note and I'll send it. > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Wednesday, December 14, 2005 8:16 AM > To: Joe Abley > Cc: NZNOG List > Subject: Re: [nznog] NZ Security Notifications > > ] While an nsp-sec-nz list sounds like it could be lots of > fun, maybe ] it's also worth mentioning that it's perfectly > possible (and ] reasonable) for operators in nz who fit the > target demographic to ] become subscribers to the existing > nsp-sec list. > > Agreed! The mix of both nsp-sec and nsp-sec-nz would be > quite complimentary and useful. > > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Hotmail
by Jeremy Strachan 14 Dec '05

14 Dec '05

Probably B52 bombers and cruise missiles. -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Thursday, 15 December 2005 12:47 p.m. To: Simon Lyall Cc: nznog Subject: Re: [nznog] Hotmail Simon Lyall wrote: > Violations will result in use of equipment located in California and > other states. Ouuchhhh... that'll stop spammers for sure! Wonder what equipment located in California and other states it is that MSN/Hotmail will use though? -- Juha _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

6 7

Hotmail
by Simon Lyall 14 Dec '05

14 Dec '05

$ telnet mx2.hotmail.com smtp Trying 65.54.244.168... Connected to mx2.hotmail.com. Escape character is '^]'. 220 bay0-mc6-f18.bay0.hotmail.com Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited. Other restrictions are found at http://privacy.msn.com/Anti-spam/. Violations will result in use of equipment located in California and other states. Wed, 14 Dec 2005 15:39:37 -0800 helo 250 bay0-mc6-f18.bay0.hotmail.com (3.1.0.17) Hello [202.27.185.139] Mail from:<simon(a)darkmere.gen.nz> 452 Out of memory Connection closed by foreign host. $ -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

Re: [nznog] NZ Security Notifications
by Dean Pemberton 13 Dec '05

13 Dec '05

>Would this list have the same sort of policy for membership as nsp-sec? >i.e. an invite only list for people who actually have to do the work >with a policy of kicking out people who don't meet the membership >criteria on an ongoing basis. > >If that's the case then I can see value in such a list but if it's >going to be similar to NZNOG with an "anybody can join" policy then I'm >less interested. > >andy I agree with Andy here. The only list I would be interested in is one which subscribes to the nsp-sec policy. No lurking. You have to be the person who is able to make the changes. Change jobs and you unsub. And some others. It's the only way. An "anyone can join" list will degrade into.... well my opinions here should remain to myself =) I would suggest that people look at joining nsp-sec rather than re-inventing the wheel. Or at the very least getting Rob to host an nsp-sec-nz list with the same policy around it. If you are a large provider, then there is probably already content on nsp-sec that you should know about. Dean.

1 0

Fwd: King Kong streaming tomorrow
by Paul Adshead 13 Dec '05

13 Dec '05

It may be good for someone in Telecom to let their front line staff know about (de-)peering at some point. After spending 15 minutes on the phone, it was quite amusing when they came back from putting me on hold: "I have talked to our tech guys and no-one in Xtra can get to the page either. They think it is a problem with the routing of data for the site at the far end. You could try power-cycling your router though"... Then when I asked for confirmation by email: "We suspect that there has been some stringent ip filtering and this is what could be causing the problem. We can not confirm this the best source of action would be to contact the host of the website for further information." Obviously either highly qualified in providing BS responses or just stupid. It's still annoying that I can't get to see it though... Paul -----Original Message----- From: Mike [mailto:mike(a)nzbox.com] Sent: Wednesday, 14 December 2005 17:20 To: NZNOG Subject: Re: [nznog] King Kong streaming tomorrow Hi Rich and Si Can I suggest you mention which streams will be available internationally in your announcements. Cant see either of these from Seattle ;-) good message for TCL and TNZ though.... Kia ora! You've reached the Citylink anycast node located in San Francisco, California. If you are in NZ, you should ring your ISP and ask them why your traffic is coming to the USA, rather than staying in New Zealand. Useful phone numbers are at TelstraClear (try the wholesale number if you get no joy from residential/business) and the best number for Telecom would appear to be 0800 CALL XTRA [22 55 98]. If you're feeling particularly cussed, ask them what's changed in the two years between the RoTK (when you could reach these streams nationally) and now. International users, we're sorry, sadly, our non-existent budget means that we can't make the Courtenay Place webcam available internationally. Such is life. Mike On Dec 12, 2005, at 8:10 PM, Simon Blake wrote: > Hi all > > A belated notice that the red carpet TV coverage and Courtenay Place > webcam will be streaming tomorrow as part of the King Kong premiere. > The mms stream will be on ac1-all.r2.co.nz (202.7.7.90), the webcam > from > embassy.citylink.co.nz (202.7.6.10), both anycast at the major > exchanges. The webcam is running now, informal MMS streams will start > about midday, TV coverage about 3pm. > > We're not expecting the same sorts of loads as RoTK, but who can tell. > > Cheers > Si > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

King Kong streaming tomorrow
by Simon Blake 13 Dec '05

13 Dec '05

Hi all A belated notice that the red carpet TV coverage and Courtenay Place webcam will be streaming tomorrow as part of the King Kong premiere. The mms stream will be on ac1-all.r2.co.nz (202.7.7.90), the webcam from embassy.citylink.co.nz (202.7.6.10), both anycast at the major exchanges. The webcam is running now, informal MMS streams will start about midday, TV coverage about 3pm. We're not expecting the same sorts of loads as RoTK, but who can tell. Cheers Si

5 4