Re: [lwip-users] how to handle multiple TCP socket simultaneously

Thanks Simon, I mean rest of the processes are working but only ethernet related functions stops working. It's my first project with LwIP so dont know from where to start debug. Now as you suggested I'll try to get data from lwip_stats first. Thanks again. On Tue, Aug 8, 2017 at 10:02 AM, Simon

Re: [lwip-users] Advice on wifi module

Hi, On 4.8.2017 19:30, u123 wrote: Hello all, we are in the same situation and we have the same question but 4 years later... Are there new ideas and/or solutions? I have been using MXCHIP EMW3165 modules with LwIP. Those modules have Cypress Semiconductor CYW43362 (previously broadcom

Re: [lwip-users] how to handle multiple TCP socket simultaneously

Mohsin Madki wrote: > can anybody reply to this email.  That's hard. First, I don't know what "stops working" means. Then: no way to tell from here. Get a debugger and start searching what's wrong. "lwip_stats" might help you. Simon ___ lwip-users

Re: [lwip-users] Advice on wifi module

Hi All, You can try out Artik053 IoT module which uses LWIP on Wifi. For more information checkout: https://www.artik.io/modules/artik-053/ ARTIK 053 - ARTIK IoT Platform www.artik.io The Samsung ARTIK 053 IoT module brings Wi-Fi to "things" that need

Re: [lwip-users] how to handle multiple TCP socket simultaneously

can anybody reply to this email. On Fri, Aug 4, 2017 at 10:10 AM, Mohsin Madki wrote: > Hi, > > I am using STM32F107 with FreeRTOS+LWIP with Netconn APIs. > > I have created 4 tcp ports (server in listening mode) and trasfers data > received to UARTS and viseversa. i.e.

Re: [lwip-users] Advice on wifi module

I've been searching for something like that for some time. Most wifi modules have their own TCP/IP stack because they already have horsepower and intelligence to support WPA. We embedded developers would want to have our applications written once for lwIP and peruse them either on Ethernet or

Re: [lwip-users] TCP 2.0.2 pcb->snd_nxt is not updated somewhere?

> > On Aug 7, 2017, at 4:43 AM, Simonas Kazlauskas > wrote: > > So it seems like for some reason the pcb->snd_nxt is one-off. This seems really strange. For an active open, sending of the SYN packet advances pcb->snd_nxt by 1. See the following code in

[lwip-users] TCP 2.0.2 pcb->snd_nxt is not updated somewhere?

Hi all, I've been using lwIP 2.0.2 branch as a base my networking stack. I implemented a device driver and am using a tcpip thread, these are my options: #define LWIP_SKIP_CONST_CHECK 1 #define LWIP_PROVIDE_ERRNO 1 #define LWIP_TCPIP_CORE_LOCKING 1 #define

Re: [lwip-users] Randomized initial local port in tcp_connect()

Hi Gus! You also need to define LWIP_RAND to a rand()-like function which will be called to get the next random number. This number is used to initial the local port. Only if both (LWIP_RAND and LWIP_RANDOMIZE_INITIAL_LOCAL_PORTS) are defined, UDP (udp.c line 98) and TCP (tcp.c line 144)