[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Re: [lwip] RFC: ARP (timing) behaviour
From: |
leon . woestenberg |
Subject: |
[lwip-users] Re: [lwip] RFC: ARP (timing) behaviour |
Date: |
Thu, 09 Jan 2003 01:42:06 -0000 |
Hello Scott,
> While on the subject of ARP, what is the maximum it'll delay the packet?
>
> It seems that I've had UDP packets delayed from transmission for up to 60
> seconds. Seem familiar? ;-)
>
Hmm, this may have been a result of the old etharp.c code. Currently, queued
packets are dropped from pending ARP entries on every call to etharp_tmr(),
as can be seen
in the code below. So, at most 10 seconds if you follow the advice:
Leon.
If you call etharp_tmr() every 10 seconds,
{
...
++ctime;
/* remove expired entries from the ARP table */
...
} else if((arp_table[i].state == ETHARP_STATE_PENDING) &&
(ctime - arp_table[i].ctime >= ARP_MAXPENDING)) {
arp_table[i].state = ETHARP_STATE_EMPTY;
/* remove any queued packet */
pbuf_free(arp_table[i].p);
arp_table[i].p = NULL;
}
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!
[This message was sent through the lwip discussion list.]