November 2002 - Test - lists.nanog.org

What? : Delivery Status Notification (Failure) (fwd)
by Stephen J. Wilcox 18 Nov '02

18 Nov '02

anyone else receiving a large number of bounces from nanog deliveries to the below address dated over the past 3 months? anyone at shure.com care to stop it as they're still coming! ---------- Forwarded message ---------- Date: Fri, 11 Oct 2002 20:01:45 -0500 From: postmaster(a)shure.com To: steve(a)telecomplete.co.uk Subject: Delivery Status Notification (Failure) This is an automatically generated Delivery Status Notification. Unable to deliver message to the following recipients, due to being unable to connect successfully to the destination mail server. Administrator(a)shure.com

6 5

Re: PAIX
by nstratton＠hushmail.com 18 Nov '02

18 Nov '02

You should move to the Atlanta NAP. It is designed to withstand a plane crashing into the building. BTW, Netrail still owes me money. - Nathan Stratton On Mon, 18 Nov 2002, Daniel Golding wrote: > Paul, > > Not sure if you are currently in a position to answer this... > > With the impending S&D buyout of some of PAIX's assets, do you see PAIX > Atlanta as a going concern? I know S&D owns an adjacent floor at 56 > Marieta. Do you think they will hold on to both? I am curious, as my > company has a POP in PAIX Atlanta, and we are starting to do some > contigency planning. > > Thanks, > Daniel Golding > > On 17 Nov 2002, Paul Vixie wrote: > > > > > speaking of paix, for those of you in atlanta (ietf) this week, i'm > > going to do a couple of site walkthroughs. send me e-mail if interested. > > -- > > Paul Vixie > > > > Get your free encrypted email at https://www.hushmail.com

3 2

Re: PAIX
by Paul Vixie 18 Nov '02

18 Nov '02

daniel wrote: > With the impending S&D buyout of some of PAIX's assets, do you see PAIX > Atlanta as a going concern? I know S&D owns an adjacent floor at 56 > Marieta. Do you think they will hold on to both? until the bankruptcy court's auction runs its course, we don't know who the new owner of PAIX will be. in any case, i can't speak for S&D at this time. > I am curious, as my company has a POP in PAIX Atlanta, and we are > starting to do some contigency planning. it's very likely that S&D would like to talk you about those plans, and that with appropriate NDA's in place, they would tell you more about PAIX-ATL1's likely future under their ownership. paul re: > > speaking of paix, for those of you in atlanta (ietf) this week, i'm > > going to do a couple of site walkthroughs. send me e-mail if interested. > > -- > > Paul Vixie

1 0

Re: Next NANOG meeting/stats
by Johnny Eriksson 18 Nov '02

18 Nov '02

> > and it butts right against nordnog, essentially preventing attendance > > at both. > > > As Nordnog organizer I agree. And the new date for nordnog is? > - kurtis - --Johnny

2 1

Re: Simulated disaster exercise? Re: PAIX
by sgorman1＠gmu.edu 18 Nov '02

18 Nov '02

It should also be noted that the CAIDA study only examined the core "giant cluster" of the Internet. In other words they only looked at the most interconnected part of the Internet not the whole Internet. While you could argue only the core matters, the methodological approach gives you much different results. You are ignoring the places that were disconnected or balkanized in other studies (Albert et al 2000, Cohen et al 2002...etc.) CAIDA are the data gurus, so I'm sure there is good justification for this, it is just not outline in their paper - http://www.caida.org/analysis/topology/resilience/ ----- Original Message ----- From: Sean Donelan <sean(a)donelan.com> Date: Monday, November 18, 2002 0:55 am Subject: Re: Simulated disaster exercise? Re: PAIX > > On Sun, 17 Nov 2002, Richard A Steenbergen wrote: > > > The usual response was it only affected the public exchange > fabric, not > > > any private point-to-point circuits between providers through > the same > > > facility. > > > > But if we're going to compare this to MAE Gigaswitch failures, > shouldn't> we be talking apples to apples and oranges to oranges? > > No. The world has changed. If people are buying tangerines and > grapefruitnow, that's what we should be talking about, not apples > and oranges. If > most of today's Internet exchange is via private connections, > those are > the connections we should be looking at. > > The fine folks at Caimis and Caida have done some analysis, and > identifiedthe nodes which make up the "core" of the Internet. > They've also > identified the most connected "core" nodes. The good news is the > networkdoesn't go non-linear until more than 25% of the nodes are > removed. > > >

1 0

RE: free network monitoring/management tools
by Gustavus, Wayne 18 Nov '02

18 Nov '02

Joshua, Hate to give the std answer, but I suggest a review of the archives over the past 2 months--this thread was just recently re-hashed. Also, there was a presentation on "Managing IP Networks with Free Software" at NANOG 26. Check it out here: http://www.nanog.org/mtg-0210/ppt/stephen.pdf -Wayne -----Original Message----- From: Joshua Smith [mailto:joshua.ej.smith@usa.net] Sent: Wednesday, November 13, 2002 10:56 AM To: nanog(a)merit.edu Subject: free network monitoring/management tools hello to all, i would appreciate your your knowledge and experiences regarding freely available tools for network monitoring and management (all cisco now, some other stuff later). i would prefer free tools as i have no budget :) i am looking for the following (it will be running on either freebsd or redhat): AAA - i have been trying to find a tacacs+ daemon/program that doesn't require me to also learn *sql to set up the backend database (if this is the only choice, then i can learn it) config monitoring/management - rancid or rtrmon are the two that i have found. any preferences on one over the other in terms of ease of use, ability to modify/improve, efficiency, etc? network/syslog monitoring - some of the likely candidates i have found are nagios or netsaint, jffnms, nmis, opennms, or maybe snip (formerly nocol) - i need something that is fairly easy to setup and use, and it doesn't have to do a whole lot (just some basic notifications for now). decent documentation is also necessary, and a pretty map would be nice for my noc, but this isn't a prereq. my scripting/programming skills are rudimentary, so it would be ideal if it was at least partially plug-and-play (i know i know, sorry). i would appreciate any input (i am still reading through the archives for useful tidbits), and i, of course, will gladly summarize for the list. thanks in advance joshua "Walk with me through the Universe, And along the way see how all of us are Connected. Feast the eyes of your Soul, On the Love that abounds. In all places at once, seemingly endless, Like your own existence." - Stephen Hawking -

1 0

PM3's crashing
by Mark Radabaugh 16 Nov '02

16 Nov '02

Anyone seeing odd crashes on Lucent PM3's tonight? We have boxes dying all over the network with hard lockups. The machines are in different physical locations with different telcos. It smells alot like a DOS of some sort. Mark Radabaugh Amplex (419) 720-3635

5 4

Re: IP backbone numbering/naming
by Jahowering＠aol.com 16 Nov '02

16 Nov '02

The DOS attack should be a real concern when using RFC 1918. A (distributed) smurf attack, or one of it's derivatives, can cause the icmp echo replies to be sent to that src. address. Since the attackers just use blocks and blocks of spoofed addresses, you could become the sourced address victim. Of course, ingress and egress rfc 1918 filtering will prevent this...it's just something else to think about... -jake In a message dated 11/16/2002 12:19:36 AM Eastern Standard Time, mike(a)rockynet.com writes: > haesu(a)towardex.com wrote: > > >You could also use RFC1918 numbers for your point-to-point /30 > >aggregation blocks with the customers.. But.. since that would have > >effect on customer's premise equipment, it would be better to give > >them globally unique space as well, who knows if your customer comes > >back and yells at you for not being able to get to his router's serial > >interface IP. > > > > This practice was implemented here in the early days, before I came > along. There have been almost no requests to change by clients, and > very, very few who even noticed/cared enough to ask why. > > But as more VPNs are deployed, I've seen this break some > implementations. So for two reasons we've begun the (large) task of > renumbering all the /30 ptp links either public or unnumbered: > > 1) Ensures all clients who decide to implement VPN don't run into > frustration because of this practice. We want to encourage better > security practices, and VPN can be an integral part of that. > > 2) The script kiddies won't mistakenly assume that we're not doing > source address filtering. I'm sure that seeing a private address in > traceroute probably makes you a more desirable target in certain circles. > > There is only one case where I would recommend using a private address > on a public link. We have a client periodically attacked, and in some > cases the attackers have simultaneously attacked our own infrastructure. > They now have only one path to them here, and every hop past the border > is RFC1918. >

2 1

disconnected autonomous systems
by Ralph Doncaster 16 Nov '02

16 Nov '02

I've found there are many providers that have completely disconnected autonomous systems. For example Yipes (6517) uses L3 on the west coast and Williams on the east coast. 66.7.129.0/24 is advertised under their AS through WCG and 209.213.209.0/24 is advertised under their AS through L3. And the number of connected autonomous systems with de-aggregated prefixes appears to be even more common than a disconnected AS. It would seem that many (most?) network operators are just ignoring the more vocal opinions on NANOG. -Ralph

10 18

ASN VoIP Phones
by Feger, James 16 Nov '02

16 Nov '02

Does anyone have the URL documenting the ASN VoIP phone project that was talked about in Eugene? Thanks, James

2 1