Messages in this thread | | | Subject | Re: Arp expire/timeout 2.1.132/2.2pre1 | From | Andi Kleen <> | Date | 02 Jan 1999 03:51:02 +0100 |
| |
In article <19990101180821.B19906@mini.gt.owl.de>, flo@rfc822.org (Florian Lohoff) writes:
> If you statically hardcode the arp entry via arp -s it works > perfectly. Has recently something changed in the arp state machien etc ?
ARP has been completely rewriten. You can configure the ARP timeout using the /proc/sys/net/ipv4/neigh/<interface>/base_reachable_time interface.
The problem with tftp is that it is not handled by the kernel. For kernel connection oriented protocols (TCP) the kernel signals forward process for any successfull ack to the neighbouring cache, which will restart the neighbour entry expiry time. The user level tftp code has no way to do this, so the neighbour expires rather quickly.
-Andi
- 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/
| |