Sylvain Rochet wrote:
> PPPoE use PBUF_LINK, PPPoL2TP use PBUF_TRANSPORT, PPPoS use PBUF_RAW, it
> all makes sense at first sight and IP forwarding should work for PPPoE
> and PPPoL2TP. Maybe we should allocate a PBUF_LINK for PPPoS as well.
That would be a good idea for the forwarding case, I
sammy77 wrote:
> Thank you for your answer. I will try to clean up my includes.
>
> Is there an example project for lwip 1.4.1 and win32? The one from the
> contrib package I didn't get running.
Exactly the one. What's the problem getting it to run?
Simon
___
My guess would be that you have manual listen backlog enabled but don't tell
the stack to decrement the listen backlog after accepting a connection...
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip
Having read that, I'm not sure lwip is the right stack to do that. Its simply
not meant for such a setup. And like Z wrote, even if you get it running,
there's no guarantee future changes to lwip will leave your setup intact.
I'd suggest to either get an OS with support for separated processes o
Sergio R. Caprile wrote:
> Anyway, glad you managed to solve your issue Michael, next user with an
> STM bug will be charged ;^) I wonder if the SICS can take donations...
I would take donations as well :-) I'm not getting paid for this, and my slooow
2007er MacBook is one of the reasons I disl
Joel Cunningham wrote:
> 1) Should SYS_ARCH_PROTECT() do more than just disable interrupts? Something
> that would act as a critical section in the case where a context switch
> happens?
Up to now, it should block task switching too, I guess. Although this is not
cleanly documented, it's just
