I don't use sockets, but I suspect that increasing MEMP_NUM_UD_PCB isn't needed in which case you'll save some memory. Feel free to yell at me if I'm wrong. J
Bill From: [email protected] [mailto:[email protected]] On Behalf Of Enrique Wellborn Sent: Wednesday, October 30, 2013 12:34 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] maximum lwip sockets limitation OK, changing this macro alone didn't do it, but changing the MEMP_NUM_TCP_PCB and MEMP_NUM_UDP_PCB macros along solved it. Is there any other macro that needs to be changed along with the above for lwip to function properly and stably? Thank you very much! On Wed, Oct 30, 2013 at 5:25 PM, Yafei Yan <[email protected]> wrote: You can modify the marco as follow: /* MEMP_NUM_NETCONN: the number of struct netconns. */ #define MEMP_NUM_NETCONN 8 It indicates that the number of sockets. 2013/10/30 Enrique Wellborn <[email protected]> Hi, I'm using the lwip_socket() api to create lwip sockets on linux and it works well, but only for 4 sockets. When I try to create a fifth socket, the functions fails (returns -1). When I call lwip_close() on one of the 4 existing sockets, it works, and then i can recreate the same socket (I get the same socket id) using lwip_socket(). Is there a way to remove this limitation? Thank you very much! _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
