lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-devel] Issue related to Tcp Server max connections


From: Ishmeet
Subject: Re: [lwip-devel] Issue related to Tcp Server max connections
Date: Sun, 30 Jun 2013 22:32:47 -0700 (PDT)

Hello guys,

sorry for the delay,

Thanks Simon for the reply, I was using tcp_listen at first which is basically a #define to tcp_listen with backlog with backlog set to 255, now I am using tcp_listen_backlog with backlog set to 4, NOTE: my no. of pcb connections are also 4, and priority is set to HIGH, so after 4 successful connection, 5th connection gives TCP SYN packet but does not receive any replies, thus gets time out after specified no. of timeouts. This scenario is working for me weather its right or not, that I am not sure of, I still have much to learn. I was thinking the fifth connection could receive a FIN or RST rather than getting timeouts, anyways, maybe there's a way of doing this from the application, that I would see later.

Hello Zach smith,
I am using a NoOS on STM32L151 board running under the wireless driver. I have used listen backlog to 4. 
I checked that the first 4 sockets were getting successful 3 way handshake, but the 5th one was getting time out (the scenario I have explained above).
For the remote ping issue, I was not pinging domain name like www.google.com, I was to ping its IP address like 74.125.235.16, well yes now remote ping is working, the problem was  I misconfigured the dhcp server, as my module is the dhcp client.

thanks for the reply's, 
Can you also give some fix about tcp poll mechanism fast, as my http page loads very slow. I am thinking of increasing the tcp window size, but I am almost out of RAM. The mem.o and memp.o are using 2K, 2K each respectively. I am almost left with tiny 400 to 500 Bytes on the whole. would increasing the TCP MSS or TCP window size would help in getting fast tcp poll and subsequently fast http server page loads, or there is any other way?

Thanks,
Ishmeet



On Sat, Jun 29, 2013 at 12:41 AM, Simon Goldschmidt [via lwIP] <[hidden email]> wrote:
Zach Smith wrote:
> As for your question #1:
>
> It is by design that any new connection of same or greater priority than an already existing connection replaces the older connection.

If you want to limit the connections to a single port, use listening
backlog instead of reducing the number of available PCBs.

Simon

_______________________________________________
lwip-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-devel



If you reply to this email, your message will be added to the discussion below:
http://lwip.100.n7.nabble.com/Issue-related-to-Tcp-Server-max-connections-tp21615p21629.html
To unsubscribe from Issue related to Tcp Server max connections, click here.
NAML



View this message in context: Re: Issue related to Tcp Server max connections
Sent from the lwip-devel mailing list archive at Nabble.com.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]