That could be, I wasn't aware of how that works. But now that you mention
that, I believe it will use the oldest inactive one if none are available?
--- On Wed, 3/17/10, Kieran Mansley wrote:
From: Kieran Mansley
Subject: Re: [lwip-users] listening connection issue
To: "Mailing list for lwIP
Switching to lwip 1.3.2 solved the issue running the same code.
Il 04/03/2010 16.13, goldsi...@gmx.de ha scritto:
It seems you are violating threading requirements: calling the netif_*
and dhcp_* functions from any other thread than the tcpip_thread is not
allowed! And if the code below *would*
Andrea Visinoni wrote:
Switching to lwip 1.3.2 solved the issue running the same code.
You're still violating threading requirements then, and can be lucky it
works. You might run into problems with that later because two threads
are active in the lwIP code at the same time, which is not su
On 17 Mar 2010, at 10:53, JM wrote:
> That could be, I wasn't aware of how that works. But now that you mention
> that, I believe it will use the oldest inactive one if none are available?
Yes, it should.
Kieran
___
lwip-users mailing list
lwip-use
Hi,
Looking through threads
(http://lists.gnu.org/archive/html/lwip-users/2009-12/msg00073.html),
the implication was that a version of PPP with no OS was almost ready to
be released (for 1.3.2).
Wondering how it is progressing? I would prefer not to 'customise' the
LwIP code.
Regards,
Mykola
Mykola Kyrylenko wrote:
Looking through threads
(http://lists.gnu.org/archive/html/lwip-users/2009-12/msg00073.html),
the implication was that a version of PPP with no OS was almost ready to
be released (for 1.3.2).
Wondering how it is progressing? I would prefer not to 'customise' the
LwIP cod
