Hi everybody,
I'm not sure whether this Issue comes from LwIP or not, but maybe someone has
experienced something similar already.
The project is based on a Atmel SAM4E Xplained Pro evaluation board with the
ASF lwIP raw example (originally used 1.4.1 but updated to 2.0.3). On top of
that we'
We had to make the subnet smaller... 1024 is about as big as we go...
255.255.255.252 IOW. What is your mask set to?
__
Steve Cowell
.
On 10/22/2018 5:23 AM, Markus Pischinger wrote:
Hi everybody,
I'm not sure whether this Issue comes from LwIP or not, but maybe
someone has experienced somet
One of the networks where we experienced this was set to 255.255.255.0 in the
192.168.0.1 range, so it shouldn't be too big i guess.
Am 22. Oktober 2018 um 16:45 schrieb Stephen Cowell :
We had to make the subnet smaller... 1024 is about as big as we go...
255.255.255.252 IOW. What is your ma
Bump :) Anyone? :)
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
On 18.10.2018 22:27, Terence Darwen wrote:
I'm using LWIP for TCP/IP communication on a TI Tiva microcontroller
(a TM4C1294NCPDT). TI includes LWIP 1.4.1 in its TivaWare package.
I've read that LWIP is not threadsafe, however, I'm not sure exactly
what that means in my context where I'm using
On 19.10.2018 12:07, Sylvain Rochet wrote:
[..]
If I remember correctly, Sylvain started to make things work that he needed
when porting the updated PPP sources. It doesn't necessarily mean there was
an issue, but I guess he didn't want to implement proxy ARP support in the
lwIP ARP layer unless
On 22.10.2018 16:44, Stephen Cowell wrote:
We had to make the subnet smaller... 1024 is about as big as we go...
255.255.255.252 IOW. What is your mask set to?
What does the subnet mask have to do with this?
And why do you top-post?
Simon
___
lwi
