Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2018-04-03 Thread simeon.trifonov
: lwip-users <lwip-users-bounces+simeon.trifonov=amk- > drives...@nongnu.org> On Behalf Of goldsi...@gmx.de > Sent: Friday, March 30, 2018 4:10 PM > To: Mailing list for lwIP users <lwip-users@nongnu.org> > Subject: Re: [lwip-users] FW: Problem with renewing DHCP after lin

Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2018-03-30 Thread goldsi...@gmx.de
On 30.03.2018 13:01, simeon.trifo...@amk-drives.bg wrote: I replaced the function dhcp_renew() with dhcp_network_changed(). After power on, the dhcp works fine again (the complete log is attached). The first strange thing for me is the ARPs that follow. The devices askes who has IP address

Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2018-03-30 Thread simeon.trifonov
rg> > Subject: Re: [lwip-users] FW: Problem with renewing DHCP after link > down/up with the new LWIP V2.0.2 > > On 30.03.2018 10:40, simeon.trifo...@amk-drives.bg wrote: > > [..] > > Now I'm trying to reconnect the Ethernet cable to another network > > (diffe

Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2018-03-30 Thread goldsi...@gmx.de
On 30.03.2018 10:40, simeon.trifo...@amk-drives.bg wrote: [..] Now I'm trying to reconnect the Ethernet cable to another network (different address area). The device sends a DHCP request which is a broadcast, but the source is the IP address of the device from the former network and probably as

Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2018-03-30 Thread simeon.trifonov
s-bounces+simeon.trifonov=amk- > drives...@nongnu.org> On Behalf Of goldsi...@gmx.de > Sent: Friday, March 30, 2018 10:50 AM > To: Mailing list for lwIP users <lwip-users@nongnu.org> > Subject: Re: [lwip-users] FW: Problem with renewing DHCP after link > down/up with the new

Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2018-03-30 Thread SciMan
Hi! I have stopped my trials to start-up the DHCP renewing cause it wasn't really required. But now I'm back to this task and I still cannot find a solution. After power on, the device received a new address and all is fine. When I disconnect and connect the Ethernet cable, I get the following

Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2017-10-06 Thread goldsi...@gmx.de
Could you please stop quoting over 80kb per mail? Thanks. simeon.trifo...@amk-drives.bg wrote: I also set the IP address and mask to 0 when I detect link down. Ehrm, why do you do that? When DHCP is enabled, DHCP has control over the IP addresses. If you mess with them manually while DHCP is

Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2017-10-06 Thread simeon.trifonov
, 2017 11:16 AM To: 'Mailing list for lwIP users' <lwip-users@nongnu.org> Subject: Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2 Hi Simeon, Do you use an OS ?... if you do, you are not supposed to call dhcp_start etc... but rather netif_dhcp

Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2

2017-10-06 Thread simeon.trifonov
-users@nongnu.org Subject: Re: [lwip-users] FW: Problem with renewing DHCP after link down/up with the new LWIP V2.0.2 Hi Simeon, I am out of my office till next week so I cannot send any code. I am working with LwIP 2.02 and my DHCP works fine. There were a few small changes in using