Re: [lwip-users] broken DHCP/ARP interaction

2014-05-30 Thread Radouch, Zdenek
15, 2014 2:04 AM To: Mailing list for lwIP users Subject: Re: [lwip-users] broken DHCP/ARP interaction Radouch, Zdenek wrote: However, in this case the ARP does something that is outright wrong - - it answers an ARP query for an IP address that has not been assigned yet -- the DHCP

Re: [lwip-users] broken DHCP/ARP interaction

2014-05-15 Thread Simon Goldschmidt
Radouch, Zdenek wrote: However, in this case the ARP does something that is outright wrong -- it answers an ARP query for an IP address that has not been assigned yet -- the DHCP client is still trying to ensure that it is OK to use the address (hence the ARP query). So the behavior is

Re: [lwip-users] broken DHCP/ARP interaction

2014-05-14 Thread Radouch, Zdenek
, 2014 12:17 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] broken DHCP/ARP interaction I also have had a problem similar to this. I have lwip running in a wifi device and I was having problems because my router was echoing packets back to me. I can’t remember if this interfered

Re: [lwip-users] broken DHCP/ARP interaction

2014-05-14 Thread Sergio R. Caprile
Hi, Quickdirty workaround: disable ARP checking by defining DHCP_DOES_ARP_CHECK to 0 Analysis: I'm no expert in DHCP nor ARP, but I don't see anything similar to what you are experiencing. I've setup three scenarios: 1- different IP (static) prior to DHCP 2- same IP (static) prior to DHCP 3-

Re: [lwip-users] broken DHCP/ARP interaction

2014-05-14 Thread Radouch, Zdenek
-users] broken DHCP/ARP interaction Hi, Quickdirty workaround: disable ARP checking by defining DHCP_DOES_ARP_CHECK to 0 Analysis: I'm no expert in DHCP nor ARP, but I don't see anything similar to what you are experiencing. I've setup three scenarios: 1- different IP (static) prior to DHCP 2- same IP

Re: [lwip-users] broken DHCP/ARP interaction

2014-05-14 Thread Sergio R. Caprile
I suggested the QD workaround as a way to check if that was really the problem. I guess your problem is that you are seeing your own messages, something that may not be the case in standard Ethernets (you mentioned Wi-Fi, didn't you?) I suggest to follow the code execution and help the developers,