- NANOG - lists.nanog.org

Router too busy???
by Mark J. Scheller 02 Apr '03

02 Apr '03

This last Saturday (29 Mar 2003), about 4pm Eastern time my router -- for lack of a better term -- wigged out. I was able to ping to & through it, however any attempt to get a TCP connection (specifically ssh and http) was almost immediately terminated. I think DNS was working fine, which would hint that UDP was getting through as well, but I won't swear to that in court. After convincing someone to drive to its location and do a power cycle, it rebooted happily and has run fine since. My mrtg graphs show that the CPU was pegged at 100% during the time it was acting up; memory was fine; traffic was (not surprisingly) very low -- and no spike prior to the CPU getting pegged. I've been running this version of IOS since it was released as a response to the flaw found in SNMP.... and the router has been rock solid! CPU is normally 15-20% with occasional spikes, but never for long. Memory erodes slowly, but never dropping below 20MB. Has anyone seen anything like this before? Basically, I'm wondering whether this may be an IOS bug or whether I may have hardware on its way out or whether this was some kind of new crafty DoS attack. TIA! Mark J. Scheller (scheller(a)u1.net)

5 4

RE: AOL---
by McBurnett, Jim 02 Apr '03

02 Apr '03

Thanks to those that responded off-list I believe the issue has been handled... Jim -----Original Message----- From: McBurnett, Jim Sent: Wednesday, April 02, 2003 8:24 AM To: nanog(a)merit.edu Subject: AOL--- Is there anyone lurking out there from the AOL NOC? I have an issue I need to discuss with you without the voice mail roulette or number extension jeopardy.. Please respond off-list. Jim

1 0

Re: [Re: Semi-OT: solicitations to nanog]
by Joshua Smith 02 Apr '03

02 Apr '03

i seem to remember other similar 'solicitations' by nanog members seeking to join up with fellow networkers in their local community, at the next arin/nanog/sushi/etc meeting...i don't think that this is really that much different. granted, i don't know how 'tasteful' it was, but i am sure that jeff has been sufficiently spammed^W informed about the situation. (maybe he was trying to pull some of the noise from the list to a social organization, thereby increasing the signal level for us to discuss more valid things like the comparing pe^H^Hego^H^H^Hrouter size) now is shall step back to let the next nanoger forth to desperately flail the pulpy carcass or this thing that used to be a fine equine Jack Bates <jbates(a)brightok.net> wrote: > > Joe wrote: > > So as not to cluter up the list, I've posted the response/thread > > of email I received regarding this, complete with the "explaination" > > so to speak. I don't buy it, but perhaps I'm missing something. > > http://www.rocknyou.com/nanogspam.html > > I was surprised to get a response none the less. > > > > In this particular case, reguardless of the Friendster TOS (which I > don't believe supported the action), it is (if I'm not mistaken) the > list maintainer's call concerning whether it was appropriate or not and > what action (if any) is needed. > > My personal opinion is that the list is designed to "bring people > together" and its membership is, I'm sure, aware that there are other > ways of communications which are often handled on a case by case basis > off-list (or perhaps the off-topic list depending on it's charter?). > > > -Jack > > "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

Semi-OT: solicitations to nanog
by Dan Hollis 02 Apr '03

02 Apr '03

Just curious if anyone feels that jeff wheeler's friendster solicitation[1] was appropriate content for the nanog ml? -Dan -- [1]http://www.merit.edu/mail.archives/nanog/msg08799.html

3 2

AOL---
by McBurnett, Jim 02 Apr '03

02 Apr '03

Is there anyone lurking out there from the AOL NOC? I have an issue I need to discuss with you without the voice mail roulette or number extension jeopardy.. Please respond off-list. Jim

1 0

RE: Curing the BIND pain
by Michael.Dillon＠radianz.com 02 Apr '03

02 Apr '03

>Michael - one of the things that I am sure of is that this >life and in fact things on this earth are moving targets. >And what I see you saying here is "leave us alone - I want >it to stay the way it was"... Am I wrong and if so how? Uhh, do I have to say it again? If you want to change the world, create new protocols or build an working group on some topic or other, you really shouldn't try to do it on NANOG because it just ain't gonna work. What I want is irrelevant. NANOG is what it is and it isn't going to change much unless and until it fails to meet the needs of its "members". --Michael Dillon

1 0

RE: RFC3514
by Tomas Daniska 02 Apr '03

02 Apr '03

now that we have first implementation i think it's time for rob thomas to start monitoring who has deployed it and who not :))))) -- deejay > -----Original Message----- > From: bmanning(a)karoshi.com [mailto:bmanning@karoshi.com] > Sent: 1. apríla 2003 19:40 > To: nanog(a)nanog.org > Subject: Re: RFC3514 > > > > > > > Well, you weren't taking it seriously, I hope. lol > > > > > > -Jack > > ------------------------- > get it while its hot.... > ----------------- > > Subject: cvs commit: src/sbin/ping ping.8 ping.c src/share/man/man4 > inet.4 ip.4 src/sys/netinet in.h in_pcb.h ip.h ip_input.c > ip_output.c ip_var.h src/usr.bin/netstat inet.c > Date: Tue, 1 Apr 2003 00:21:44 -0800 (PST) > To: src-committers(a)FreeBSD.org, cvs-src(a)FreeBSD.org, > cvs-all(a)FreeBSD.org > > mdodd 2003/04/01 00:21:44 PST > > FreeBSD src repository > > Modified files: > sbin/ping ping.8 ping.c > share/man/man4 inet.4 ip.4 > sys/netinet in.h in_pcb.h ip.h ip_input.c ip_output.c > ip_var.h > usr.bin/netstat inet.c > Log: > Implement support for RFC 3514 (The Security Flag in the > IPv4 Header). > (See: ftp://ftp.rfc-editor.org/in-notes/rfc3514.txt) > > This fulfills the host requirements for userland support by > way of the setsockopt() IP_EVIL_INTENT message. > > There are three sysctl tunables provided to govern system behavior. > > net.inet.ip.rfc3514: > > Enables support for rfc3514. As this is an > Informational RFC and support is not yet widespread > this option is disabled by default. > > net.inet.ip.hear_no_evil > > If set the host will discard all received > evil packets. > > net.inet.ip.speak_no_evil > > If set the host will discard all > transmitted evil packets. > > The IP statistics counter 'ips_evil' (available via > 'netstat') provides > information on the number of 'evil' packets recieved. > > For reference, the '-E' option to 'ping' has been provided > to demonstrate > and test the implementation. > > Revision Changes Path > 1.47 +4 -2 src/sbin/ping/ping.8 > 1.92 +13 -1 src/sbin/ping/ping.c > 1.21 +11 -0 src/share/man/man4/inet.4 > 1.29 +9 -0 src/share/man/man4/ip.4 > 1.75 +2 -0 src/sys/netinet/in.h > 1.59 +1 -0 src/sys/netinet/in_pcb.h > 1.22 +1 -0 src/sys/netinet/ip.h > 1.232 +14 -0 src/sys/netinet/ip_input.c > 1.181 +28 -1 src/sys/netinet/ip_output.c > 1.72 +1 -0 src/sys/netinet/ip_var.h > 1.57 +1 -0 src/usr.bin/netstat/inet.c > > > ----- End forwarded message: >

2 1

Global Crossing right now
by Peter Salus 02 Apr '03

02 Apr '03

Is anyone seeing peering problem with GBLX? We've seen peering problems on GBLX across NA. It's being felt by many of their peering partners and, in turn, being felt by many of our customers. We're sending a generic report to the effected customers and will try to get more info on the problem. The perf. losses started at approx 16:00 GMT and are ongoing. Peter --- "There is no way to peace, peace is the way." -- A.J. Muste ----------------------------------------------------------- Peter H. Salus Chief Knowledge Officer, Matrix NetSystems Ste. 300 5001 Plaza on the Lake Austin, TX 78746 +1 512 697-0613 -----------------------------------------------------------

4 3

Cogent?
by Deepak Jain 01 Apr '03

01 Apr '03

I haven't seen anyone mention this today, and I don't remember if this discussion was considered taboo, but oh well. Flame away. http://www.carrierhotels.com/news/April2003/cogent0401.shtml DJ

1 0

RFC3514
by Scott Francis 01 Apr '03

01 Apr '03

Comments? (Nice to see Mr. Bellovin keeping up the holiday tradition ... :)) -- Scott Francis || darkuncle (at) darkuncle (dot) net illum oportet crescere me autem minui

8 10