[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [task #1551] Make ARP more independent of interface hardwar
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [task #1551] Make ARP more independent of interface hardware type |
Date: |
Thu, 19 Apr 2007 08:06:17 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 |
Follow-up Comment #6, task #1551 (project lwip):
I've had a quick look at RFC2734. Ignoring the fact the etharp is used from
dhcp.c (and maybe netif.c and tcpip.c, but that's a define), do you need any
modifications in the rest of the stack (aside from a new module like
1394arp.c and a configurable NETIF_MAX_HWADDR_LEN)?
I'd imagine (if the code in etharp.c cannot be somehow reused) to create a
module 1394.c, make NETIF_MAX_HWADDR_LEN comfigurable (and maybe change
dhcp). Since etharp is otherwise only used from ethernetif.c, that should be
enough. Or am I wrong?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/task/?1551>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/