On 11/28/18 10:02 AM, goldsimon wrote:
Niklas Gürtler" wrote:
[..]
When I restart my WiFi access point, the link is reconnected as
desired,
and lwIP performs a DHCP reboot and receives the same address as
before.
Unfortunately, in this case, the status callback is never called after
a
dhcp
Niklas Gürtler" wrote:
> [..]
>When I restart my WiFi access point, the link is reconnected as
>desired,
>and lwIP performs a DHCP reboot and receives the same address as
>before.
>Unfortunately, in this case, the status callback is never called after
>a
>dhcp reboot. I think this is because
Hi,
i am using lwIP 2.1.2 on an embedded device with a WiFi connection in
NO_SYS mode using DHCP and the raw API. I need my application to
initiate a TCP connection immediately after a completed DHCP
negotiation, i.e. as soon as possible. This also needs to happen when
the link is
Hi Simon,
Thank you very much for your reply.
I found what is the reason of my problem. It was because of MEMP_NUM_UDP_PCB
value.
by default the value of MEMP_NUM_UDP_PCB is 4 and I need 6 socket. so I
changed the value to 6
and my problem was solved.
On Sun, Nov 25, 2018 at 11:01 PM
