An article from CNN on IPV6 and how the US will be hurt because its falling behind http://money.cnn.com/2006/11/03/technology/fastforward_ipv6_networking.fortu...
On Fri, 3 Nov 2006, Roy wrote:
An article from CNN on IPV6 and how the US will be hurt because its falling behind
http://money.cnn.com/2006/11/03/technology/fastforward_ipv6_networking.fortu...
yes, the internet died just a while ago from this, oh wait, that was my IP access at starbucks, nevermind.
Herb Leong wrote:
Hi,
Anyone being impacted by UUNET?
Nothing unusual here, we are AS4927 connecting to AS701 in Los Angeles. -- Jay Hennigan - CCIE #7880 - Network Administration - jay@west.net NetLojix Communications, Inc. - http://www.netlojix.com/ WestNet: Connecting you to the planet. 805 884-6323 - WB6RDV
Two different transits here as well and nothing out of the norm. ---------------------------------------------------------------------- Elijah Savage | AOL IM:layer3rules Senior Network Engineer | When it has to be switched or routed. http://www.digitalrage.org | The Information Technology News Center ----- http://www.digitalrage.org/?page_id=46 for pgp public key-------- On Nov 4, 2006, at 7:54 PM, Herb Leong wrote:
Hi,
Anyone being impacted by UUNET?
/herb
On Nov 4, 2006, at 7:54 PM, Herb Leong wrote:
Hi,
Anyone being impacted by UUNET?
I'm fairly sure I'm not the only one who's said this in the last (pick a months long period of time, I'll guess 6): "Could you be any less descriptive of the problem you are seeing?" Also, did you contact customer support? (I'mm guessing yoyu aren't a uunet customer based on email/mx locations only though)
On Sat, 4 Nov 2006 22:55:46 -0800 Michael Smith <mksmith@adhost.com> wrote:
On Nov 4, 2006, at 10:51 PM, Randy Bush wrote:
"Could you be any less descriptive of the problem you are seeing?" the internet is broken. anyone know why? Did you ping it?
is that what broke it?
Please. That's how you *know* it's broken.
With the prevalence of firewalls, I've found broken traceroutes to be a much more reliable indicator of broken Internettedness. -- "Sheep are slow and tasty, and therefore must remain constantly alert." - Bruce Schneier, "Beyond Fear"
Speaking on Deep Background, the Press Secretary whispered:
On Nov 5, 2006, at 1:51 AM, Randy Bush wrote:
"Could you be any less descriptive of the problem you are seeing?" the internet is broken. anyone know why? Did you ping it?
is that what broke it?
I'm sure it just needs to be rebooted.
Is this the day we disconnect everything and blow all the dirt out? -- A host is a host from coast to coast.................wb8foz@nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433
David Lesher wrote:
Speaking on Deep Background, the Press Secretary whispered:
On Nov 5, 2006, at 1:51 AM, Randy Bush wrote:
"Could you be any less descriptive of the problem you are seeing?" the internet is broken. anyone know why? Did you ping it? is that what broke it? I'm sure it just needs to be rebooted. Is this the day we disconnect everything and blow all the dirt out?
You only *think* you are joking. I still remember the Day of the Great Restart when everyone on the ARPAnet had to shut down the IMPs and TIPs, and reload the control software. Why? There were literally thousands of rogue packets flying around the net, eating up bandwidth (and in those days, we are talking 56 kbps links!) and boy were those tubie-thingies plugged up! Shortly after that cusp event, per-packet TTL field was added to the NTP protocol, which is why TCP/IP has the TTL field in the IP packet. The network had added to it a self-cleaning function. Think of it as one long continuous sneeze.
On Sun, 05 Nov 2006 07:16:07 -0800, Stephen Satchell <list@satchell.net> wrote:
David Lesher wrote:
Speaking on Deep Background, the Press Secretary whispered:
On Nov 5, 2006, at 1:51 AM, Randy Bush wrote:
> "Could you be any less descriptive of the problem you are seeing?" the internet is broken. anyone know why? Did you ping it? is that what broke it? I'm sure it just needs to be rebooted. Is this the day we disconnect everything and blow all the dirt out?
You only *think* you are joking. I still remember the Day of the Great Restart when everyone on the ARPAnet had to shut down the IMPs and TIPs, and reload the control software. Why? There were literally thousands of rogue packets flying around the net, eating up bandwidth (and in those days, we are talking 56 kbps links!) and boy were those tubie-thingies plugged up!
Shortly after that cusp event, per-packet TTL field was added to the NTP protocol, which is why TCP/IP has the TTL field in the IP packet.
I assume you mean NCP rather than NTP. Anyway, I don't think that would have helped if you're talking about the same incident I'm thinking of. There were application-level retransmissions of (corrupted) packets, complete with building new bad packets from bad data structures, all over the net The problem is documented in RFC 789 It and "The Bug Heard 'Round the World" are two of my favorite "how complex systems fail" papers; all system designers should read, memorize, and undertand both.
The network had added to it a self-cleaning function. Think of it as one long continuous sneeze.
--Steven M. Bellovin, http://www.cs.columbia.edu/~smb
Anyway, I don't think that would have helped if you're talking about the same incident I'm thinking of. There were application-level retransmissions of (corrupted) packets, complete with building new bad packets from bad data structures, all over the net
The problem is documented in RFC 789 It and "The Bug Heard 'Round the World" are two of my favorite "how complex systems fail" papers; all system designers should read, memorize, and undertand both. I actually asked Stephen if he was referring to the LSA corruption problem and he said he was referring to an earlier issue (circa 1972).
As for the LSA issue- rebooting would have fixed the problem, assuming it was done by all nodes at the same time. All of the Link State tables would have been rebuilt from scratch by the IMPs and the corrupt announcements would have been gone. As I recall the IMP software was actually patched to ignore the problematic announcements from IMP 51. -Don
As for the LSA issue- rebooting would have fixed the problem, assuming it was done by all nodes at the same time. All of the Link State tables would have been rebuilt from scratch by the IMPs and the corrupt announcements would have been gone. Turns out this is actually mentioned on page 14 of RFC 789.
As I recall the IMP software was actually patched to ignore the problematic announcements from IMP 51. Not that it matters- but it was IMP 50 not 51.
-Don
I've got a client looking to upgrade their edge routers and they want to consider all of their options. Right now we're looking at Cisco, Juniper and Foundry. I'd like to hear what other people have to say about the vendors, their offerings and their support. Do their products have particular strengths or weaknesses? Also, if anyone has another vendor we should be considering- we are open to suggestions. In this case the router requirements are small- 5 GigE interfaces, BGP, OSPF, VRRP and the ability to handle as many PPS as possible so as to avoid a router DoS in the event of an attack (10 Mpps minimum). I have my own opinions about each vendor but I'd like another perspective this time around. Thanks in advance, -Don
I'm fairly sure I'm not the only one who's said this in the last (pick a months long period of time, I'll guess 6): "Could you be any less descriptive of the problem you are seeing?"
Ya know ... this whole descriptiveness thing has to be my biggest pet peeve. I have a couple of things going at any given time and I just *love* when I get an email entitled "can you fix this?" Bad enough when its a customer, worse when its the guys I work with - the best response to these sorts of things coming from an internal address is "maybe" and don't elaborate :-) They either take the hint and put a proper title on it with a cc: to our project manager, or they fix it themselves.
On Sun, Nov 05, 2006 at 03:39:57AM +0000, Chris L. Morrow wrote:
On Nov 4, 2006, at 7:54 PM, Herb Leong wrote:
Hi,
Anyone being impacted by UUNET?
I'm fairly sure I'm not the only one who's said this in the last (pick a months long period of time, I'll guess 6): "Could you be any less descriptive of the problem you are seeing?"
Perhaps he should see a dentist? "Wisdom Teeth are impacted, people are affected by the effects of events." from Rick Jones sig... --bill
<Perhaps he should see a dentist? I just had my impacted Cogent taken care of last week with a Sprint... :) ------------------------------------------------------------- This mail was scanned by BitDefender For more informations please visit http://www.bitdefender.com -------------------------------------------------------------
participants (17)
-
bmanning＠karoshi.com -
Chris L. Morrow -
David Lesher -
Donald Stahl -
Ed Ray -
Elijah Savage -
Herb Leong -
Jay Hennigan -
Mark Smith -
Marshall Eubanks -
Matthew Petach -
Michael Smith -
nealr -
Randy Bush -
Roy -
Stephen Satchell -
Steven M. Bellovin