- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 13 Mar '05

13 Mar '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: RE: [CityLink #2073] AutoReply: Routing updates for APE Route Servers (fwd) - Date: Mon, 14 Mar 2005 16:30:40 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503141630100.13184(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 210.55.230.0/24^24-29, 210.55.214.0/24^24-29, 210.55.169.0/24^24-29, 210.55.155.0/24^24-29, 210.55.104.0/22^22-29, 210.55.100.0/22^22-29, 202.37.181.0/24^24-29, 202.37.72.0/24^24-29, 202.36.70.0/24^24-29, 202.27.204.0/24^24-29, 202.89.32.0/19^19-29, 202.6.5.0/24^24-29, 202.49.141.0/24^24-29, 203.89.160.0/19^19-29, 202.7.5.32/29, 202.7.6.32/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050307 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 210.55.230.0/24^24-29, 210.55.214.0/24^24-29, 210.55.169.0/24^24-29, 210.55.155.0/24^24-29, 210.55.104.0/22^22-29, 210.55.100.0/22^22-29, 202.37.181.0/24^24-29, 202.37.72.0/24^24-29, 202.36.70.0/24^24-29, 202.27.204.0/24^24-29, 202.89.32.0/19^19-29, 202.6.5.0/24^24-29, 202.49.141.0/24^24-29, 203.89.160.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050314 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Mar '05

13 Mar '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: RE: [CityLink #2072] AutoReply: Routing updates for APE Route Servers (fwd) - Date: Mon, 14 Mar 2005 13:20:22 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503141320030.12596(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17474 descr: Route set advertised to AS9560 by ConceptNET - AS17474 members: 202.49.250.0/24, 202.50.176.0/24, 202.127.8.0/22, 202.150.96.0/20, 203.97.44.0/24, 203.21.31.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: craig(a)concept.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040304 changed: rpsl-admin(a)nzix.net 20040325 changed: rpsl-admin(a)nzix.net 20040617 changed: rpsl-admin(a)nzix.net 20040625 changed: rpsl-admin(a)nzix.net 20040813 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17474 descr: advertised to AS9560 by Craig Spiers - AS17474 members: 202.150.96.0/20^20-29, 202.127.8.0/22^22-29, 203.97.44.0/24^24-29, 202.50.176.0/24^24-29, 202.7.6.32/29, 202.7.5.32/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050314 source: NZRR --- PREVIOUS OBJECT: route: 202.150.96.0/20 descr: Route for ConceptNET - AS17474 origin: AS17474 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040908 source: NZRR REPLACED BY: route: 202.150.96.0/20 descr: Route for Craig Spiers - AS17474 origin: AS17474 notify: rpsl-admin(a)nzix.net notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050314 source: NZRR --- PREVIOUS OBJECT: route: 202.127.8.0/22 descr: Route for ConceptNET - AS17474 origin: AS17474 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040908 source: NZRR REPLACED BY: route: 202.127.8.0/22 descr: Route for Craig Spiers - AS17474 origin: AS17474 notify: rpsl-admin(a)nzix.net notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050314 source: NZRR --- PREVIOUS OBJECT: route: 203.97.44.0/24 descr: Route for ConceptNET - AS17474 origin: AS17474 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040908 source: NZRR REPLACED BY: route: 203.97.44.0/24 descr: Route for Craig Spiers - AS17474 origin: AS17474 notify: rpsl-admin(a)nzix.net notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050314 source: NZRR --- PREVIOUS OBJECT: route: 202.50.176.0/24 descr: Route for ConceptNET - AS17474 origin: AS17474 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040908 source: NZRR REPLACED BY: route: 202.50.176.0/24 descr: Route for Craig Spiers - AS17474 origin: AS17474 notify: rpsl-admin(a)nzix.net notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050314 source: NZRR

1 0

Cisco 2948G-L3...... I wonder if I could trouble someone out there.........
by Joe Gilliam 11 Mar '05

11 Mar '05

Well, I need some help. I found your list by googling and what I saw seemed to be pretty good. First of all, I am not a Cisco person. I don't know enough to do what I really want to do with this switch. My side of the world is the Administration of a large PACS System. I am not a part of the Network admin. Just the Apps side. But I am an MCSE and I can usually get myself out of trouble. UNTIL I GOT THIS DARN SWITCH....... I know enough to get in the switch, log in as the exec from the console and maybe change a few things here and there. I know this is an older CatOS type switch. But, I don't know many of the serious commands. OK, All I want is to change the setup so this switch will be a basic Layer 2 switch with all ports active, set to 10/100 Auto. And I want to configure an uplink port. And I want to turn on and off DHCP, like a light switch. I want to use this little jewel for lan parties. (FOR FUN, NOT FOR WORK!) Does someone out there have a place where I can get example configs, or even a manual so I can learn the CatOs or maybe even give me some pointers of how to configure the thing? This is the first time I have posted here, and haven't seen any traffic from the site. I just subscribed. So if this request is something you guys don't like to see, I won't bug you again. I am just looking for a little guidence. I can't seem to find anyone around here in Kansas that admits to knowing anything about this switch. Thanks in advance......... Joe Gilliam Wichita, Kansas

2 1

Re: [offlist] Re: [nznog] Ispmap / wix / ape - Slightly OT
by neil gardner 10 Mar '05

10 Mar '05

>>>> Jeremy Brooking <godfather(a)mafia.org.nz> 11/03/2005 10:44:58 a.m. >>Mark Foster wrote: >> Any ISPs who have run semi-transparent caching like to stick up their >> hands as to the sheer _volume_ of logging data collected relative to their >> customer base? And indicate exactly how long they archive those logs for, >> and how accessible they are??? > >Lots. > >No long. Ah, this is obviously some strange use of the word exactly that I wasn't previously aware of. (Apologies to Arthur Dent) Cheers - N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

Re: [offlist] Re: [nznog] Ispmap / wix / ape - Slightly OT
by Mark Foster 10 Mar '05

10 Mar '05

On Wed, 9 Mar 2005 11:34:09 +1300 (NZDT), "Alastair Johnson" <aj(a)sneep.net> wrote : > Nathan Ward wrote: > > > Simon Lyall wrote: > > >>It breaks a few places that use the IP address to auth http sessions, > >>apparently some sites don't believe these weird cookie thingies are ready > >>for prime time. > >> > >> > > Hmm. This would be a problem if your requests for the same site were > > going to different proxy servers. > > I don't think that happens with Foundys, by default. If it does, it's > > easily 'fix'-able. > > We had an issue at Maxnet that was a site which broke in this manner. > Essentially they 'authenticated' the customer off the IP address of the > proxy, which using WCCP was reasonably static unless a proxy failed. > However, after the initial authentication, it then redirected them to an > SSL site on 443/tcp, which obviously was not going through the transparent > cache farm, and the customer was (correctly) not configured to use a > cache. > > So the request suddenly came from the customer's IP address. Result: The > site would refuse to allow them in. > > A stupid way of doing it, and we solved the problem by excluding the site > from the cache. For the life of me, I can't remember what it was, but I > recall the site was black and popular. I think it might have been some > games thing. > The other negative of Non-Transparent-Proxying that this brings to mind is the relative difficulty that ISPs have identifying persons who abuse web based services (websites, forums, et al) - The logs which collect 'cache?.xyz.co.nz' aren't exactly going to give the ISP information used to resolve user accounts and specific individuals. And most ISPs with the above issue don't log their proxies either, or if they do, can only log for a short period of time due to the sheer volume of log data created. So TransProxying, or none at all, would be my personal choice. (I hear that in at least one cases the amount of $ saved by transproxying was being re-spent in maintaining the boxes themselves - so they were pulled out due to lack of value vs inconvenience. And theyre now saving money.) Mark. All IMHO, as usual.

4 6

Re: [offlist] Re: [nznog] Ispmap / wix / ape - Slightly OT
by Nathan Ward 08 Mar '05

08 Mar '05

David Robb wrote: > On Wed, 9 Mar 2005, Nathan Ward wrote: > >> IMO, using cache's in fully transparent mode is a rather broken thing >> to do, unless you cache on your entire border.. > > Ever tried to architect a network to do that? :) > We tried. It's easier to deal with the occasional network that breaks. Really? I imagine that there would be lots of breakage in this area, especially during failures (your's, or other's) or routing that lacks clue. When you are caching fully transparently, do the Foundry's only send the HTTP return packets to the caches if they are part of a cached session? That would limit some problems, but obviously not all, and wouldn't fix this one. How do you detect that there is a problem network? That relies on customers, right? Do they really call and complain enough? I know my Mother would just put any failures like that down to "The Internet is broken again". Why don't you cache semi-transparently? (IE, connections to web servers come from the external IP address of the proxy server). I'm not aware of any real life cases of that breaking things, and as far as I am aware, it's what most NZ providers do.. Feel free to prove me wrong here, of course. -- Nathan Ward

4 4

A good reliable local NTP server to use?
by Simon Buchanan 08 Mar '05

08 Mar '05

Can anyone let me know of a good reliable local(NZ) NTP server to use? We are connected to APE... Thanks Simon -- Operations Manager - Networker. Creative Broadband Services. Web: www.networker.co.nz Eml: simon(a)networker.co.nz Tel: +64-21-348884

2 1

Ispmap / wix / ape - Slightly OT
by Barry Murphy 08 Mar '05

08 Mar '05

Hey guys, I've added some extra details (AS, APE, WIX) to ispmap on page: http://www.ispmap.co.nz/searchisp.php . I was going to gather the data off www.ape.net.nz and www.wix.net.nz however through Telstra Clear I cannot load these sites as they go international. So I ask if people can submit their ISP (if you peer at WIX / APE). ISPNAME: WIX: Yes/No APE: Yes/No If you work for the provider: YES/NO Thanks Barry

4 4

Telecom ADSL Testing equipment
by neil gardner 07 Mar '05

07 Mar '05

Hi there - if there's anyone on this list that can perform ADSL line testing at a pretty low level, please urgently get in touch with me via email. I am looking to monitor _exactly_ what is going on between our wall jack and the DSLAM. I have tried channels and not gotten very far. This is to troubleshoot an issue (Line condition) which may be able to hang a certain DSL chipset. Thanks - Neil Gardner Senior Tester Allied Telesyn Research NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

WorldxChange Prefix List Update
by Gordon Smith 07 Mar '05

07 Mar '05

Would all direct peers please update their prefix lists as follows: ip prefix-list wxnz-networks permit 202.182.192.0/19 le 24 ip prefix-list wxnz-networks permit 58.28.0.0/16 le 24 Added: ip prefix-list wxnz-networks permit 58.28.0.0/16 le 24 For those who are not direct peering and wish to, email peering(a)wxnz.net IPv6 national peering is also available Cheers, Gordon

1 0