Messages in this thread | | | Date | Sun, 3 Jan 1999 00:36:54 +0100 | From | Florian Lohoff <> | Subject | Re: Arp expire/timeout 2.1.132/2.2pre1 |
| |
On Sat, Jan 02, 1999 at 06:31:35PM +0100, Andi Kleen wrote: > > Wouldnt this work when: > > - Restart neighbour entry expiry time on receive of an packet which matches > > the correct IP/MAC address pair ? > > Only good fix would be to add a new socket command/option that signals > forward process for a specific address to the kernel, and change tftp to use > that.
> When the neighbour entry expires the kernel first tries to send an ARP > probe directly to the other end (ucast_solicit). Is your Ultrix box > dumb enough to not answer to these probes?
Thank god - no more ulrix on that box :) - Trying to netboot Linux/Mips but the Prom seems to be mega-dumb ... Once it starts TFTP it seems not to answer arp requests anymore :(
Doesnt this new Arp timing mechanism increase Arp-Request heavily ?
I have a look at the Arp State machine - maybe ill get the clue ...
Flo -- Florian Lohoff flo@rfc822.org +49-5241-470566 Good, Fast, Cheap: Pick any two (you can't have all three). (RFC 1925)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |