[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [task #1551] Make ARP more independent of interface hardwar
[lwip-devel] [task #1551] Make ARP more independent of interface hardware type
Wed, 09 May 2007 09:32:13 +0000
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:126.96.36.199) Gecko/20070309 Firefox/188.8.131.52
Follow-up Comment #10, task #1551 (project lwip):
>It seems to me that we can reuse etharp.c with some modifications.
As far as I can see it, what can be reused is
- finding an arp entry
- the calling structure (netif->input calls arp_output which calls
But since the arp table (and maybe some functions as entrypoints), I think it
would be best to create another ARP module and link it instead of etharp.
>A specific arp.c module for each interface where entry points are set in the
If used simultaneously, I think this would be the best solution as I don't
see much code can be reused. (If we make it clear etharp.c is only for
ethernet, we can also have some speedup by defining hwaddr_len to always be
>I work on it when I have time.
Take your time, I don't see this as a pressing issue as long as nobody uses
it (aside from you :)
Reply to this item at:
Nachricht geschickt von/durch Savannah