Thank you for the response. Yes, it seems that the renewing works well, I
just had a wrong understanding what I have to expect. But the LWIP stack
V1.4.1 worked in a different way and when I migrated to 2.0.2 (now 2.0.3) I
had problems with my code. My mistake, sorry...
Now I'm trying to reconnect
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
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 192.168.5.60, but it is his new address... Is that normal?
The
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
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
Hi,
I am currently trying to use LWIP by calling tcp_write() and tcp_output()
once a connection has been established and an incoming request is
generated. I set a variable when an incoming reuest is generate and use a
global tcp_pcb structure to know which connection to send data on
nt
