Mason <[email protected]> wrote: > > the fastest way for you would probably > > be to just intercept ARP responses where they are passed to DHCP and > > handle them yourself. > > If I write a detection routine, it can't be in dhcp.c, because that > file might not even be compiled (LWIP_DCHP == 0). > > I think the detection routine has to be in etharp.c, in the handling > of ARP_REPLY packets. Do you disagree?
That's what I said: "where they are passed to DHCP", not "in dhcp.c" (i.e. add a call to your own function in etharp_arp_input() just after/before the call to dhcp_arp_reply() - in this function, check if the ARP response handles your IP address and react appropriately). I'd be happy if you could even provide a patch that does this check and calls an external function (e.g. etharp_address_collision(netif)) if such a packet has been received. We could then easily integrate that into the stack. Simon -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
