lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [task #1551] Make ARP more independent of interface hardwar


From: Nicolas Pinault
Subject: [lwip-devel] [task #1551] Make ARP more independent of interface hardware type
Date: Wed, 09 May 2007 12:36:37 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

Follow-up Comment #11, 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
netif->linkoutput)
>
And packet buffering (when sending to an unresolved IP address)

>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 netif structure.
>
>
>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
6.)
>

What about DHCP in this case ?

>>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 :)

Unfortunately, you are right.


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?1551>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]