Frédéric Grandjean wrote:
> Do I have to restart my TCP and UDP servers when the address gets changed by
> DHCP ?
That depends upon the specific daemon. Off the top of my head I am
aware of these cases. There are probably more.
1. The daemon listens on the wildcard address. In this case no
RAW API functions must be called in the same thread as the lwIP core
functions. In fact, afaik, except for netconn and socket API, all lwIP
functions must be called from the same thread.
You can run RAW API apps on the lwIP thread, and netconn/socket API apps
on other threads.
There is a runnin
Thank you Sergio,
But unfortunately that doesn't answer my real question:
Do I have to restart my TCP and UDP servers when the address gets changed by
DHCP ?
Best regards
Frédéric Grandjean
-Original Message-
From: lwip-users
[mailto:lwip-users-bounces+frederic.grandjean=telealarm..
Hello Sergio,
sorry for that confusion, I will try to answer your remaining questions.
We're using FreeRTOS 8.2.3, regular lwIP 1.4.1, netconn API and the fsdata.c
file system from raw API on our XMC4500.
Did you check that with a known-good application ? No, we can't, we have no
'known-good appl
Márk,
your post has a lot of info and I get confused following it. Can you
please post a Wireshark capture file ?
Are running an RTOS ? NO_SYS = ?
All calls to lwIP functions on the same context ? I mean, you are not
calling lwIP from rx interrupt and main loop/thread, are you ?
Last one, some
Under those conditions, I did exactly the same for some products and
they've been working fine (although they weren't using lwIP ;^)).
Yes, you do need a discovery protocol if the device is for consumer end
users with no IT capabilities.
___
lwip-us
On śro, 2016-04-13 at 10:52 +0200, Freddie Chopin wrote:
> On śro, 2016-04-13 at 10:23 +0200, Francisco Expósito wrote:
> >
> > Hi Freddie,
> >
> > Thank you very much for your quick answer.
> >
> > It seems that ST hasn’t corrected yet its EMAC driver in version
> > 1.4.4 (22-January-2016).
>
