Re: joe, turn it off!

2002-07-14 Thread Joe Touch



Randy Bush wrote:
 joe touch and crew, please turn it off
 
 Jul 15 13:01:45 roam /kernel: arp: unknown hardware address format (0x0800)

As I said at 10:30, and will repeat, this is the result of an arp cache 
that hasn't been flushed. An arp cache that we don't control, most 
likely on a router that has decided to proxy arp.

Randy - if you have evidence to the contrary, we've been waiting since 
10:30.

Joe




Re: joe, turn it off!

2002-07-14 Thread Randy Bush

 joe touch and crew, please turn it off
 Jul 15 13:01:45 roam /kernel: arp: unknown hardware address format (0x0800)
 As I said at 10:30, and will repeat, this is the result of an arp cache 
 that hasn't been flushed. An arp cache that we don't control, most 
 likely on a router that has decided to proxy arp.
 Randy - if you have evidence to the contrary, we've been waiting since 
 10:30.

this is an engineering group.  we are seeing problems on a production
network.  your experiment has been shown to once be part of the problem.
please turn from lawyer into an engineer and turn that thing off so we
can see if part of the problems go away

from draft-ymbk-termroom-op-07.txt

   While it is tempting for a host/vendor to show off fancy
   technology at an IETF, this audience runs and uses the most
   arcane assortment of services, and is a very poor place to find
   out that your fancy new switch breaks when someone tries to run
   IPv42 through it.  Run a simple production network.  If one must
   run a technology demo, isolate it onto a separate network segment
   so that it is unable to interfere with the production network.

randy




Re: joe, turn it off!

2002-07-14 Thread Joe Touch



Randy Bush wrote:
joe touch and crew, please turn it off
Jul 15 13:01:45 roam /kernel: arp: unknown hardware address format (0x0800)

As I said at 10:30, and will repeat, this is the result of an arp cache 
that hasn't been flushed. An arp cache that we don't control, most 
likely on a router that has decided to proxy arp.
Randy - if you have evidence to the contrary, we've been waiting since 
10:30.
 
 
 this is an engineering group.  we are seeing problems on a production
 network.  your experiment has been shown to once be part of the problem.
 please turn from lawyer into an engineer and turn that thing off so we
 can see if part of the problems go away

We did (at 9:30am, minutes after the problem was detected). It didn't go 
away. Now be an engineer and show us a trace.

 from draft-ymbk-termroom-op-07.txt
 
While it is tempting for a host/vendor to show off fancy
technology at an IETF,

The routers have a bug in their implementation of ARP. Yes, we tripped 
it, at 9:45am. We have no idea who is still jabbering. It is definitely 
possible that our 9:45am bug tripped the jabbering of our IP address by 
one of the routers. They are not ours to shut off, however.

ARP, and our use of it, isn't experimental. We aren't running anything now.

Joe




Re: joe, turn it off!

2002-07-14 Thread Joe Touch



Randy Bush wrote:
We did (at 9:30am, minutes after the problem was detected). It didn't go 
away. Now be an engineer and show us a trace.
 
 a bit hard when it is broken arp packets
 
 Jul 15 11:47:27 roam /kernel: arp: unknown hardware address format (0x0800)
 Jul 15 11:47:27 roam /kernel: arp: unknown hardware address format (0x0800)
 Jul 15 13:01:45 roam /kernel: arp: unknown hardware address format (0x0800)
 Jul 15 13:49:08 roam /kernel: arp: unknown hardware address format (0x0800)

That totals 4 packets that are ill-formed in a period of 2 hours, 
packets which are causing the router to crash. That's a bug, period.

This has nothing to do with what happened this morning - those were 
incorrect source addresses.

The routers have a bug in their implementation of ARP.

 yet to be known

A router that doesn't drop an ill-formed address in an ARP packet has a 
bug. A router that crashes due to this has a fatal bug.

Let's replace that router, and debug THAT offline.

ARP, and our use of it, isn't experimental.
 
 your use of it was clearly demonstrated to have broken things this
 morning.  we're just asking you to turn your stuff off so we can
 isolate the problem.

If you had bothered to ask, it isn't even my stuff. It's Lars'. I'm 
running (still, since this morning, and haven't stopped)- WinXP (gasp).

Joe