Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network?

[Itzik Levi]

Hi Noam,

Thanks for the prompt response!

The actual link isn't serial. its a non-reliable rfcomm link, which is a stream based protocol.

Regarding ram available ram - up to 50MB I would say.

I'm attaching my entire lwipopts.h here.

https://pastebin.com/24AR5sYB

Regarding the socket API - I did not actually put lots of thought to it, it was trivial to implement and that's that. do you have a reason to believe the root cause is there? Although the only change between the 2 tests I ran was randomly dropping data in the physical layer output?

If you think that might be it, I can rewrite the socket layer and attempt to test again.

And regarding misusing the stack - I totally agree, I probably did misused it somehow, I'm new to lwip and that's why I'm here.

Question is, what did I do wrong, and how to pinpoint the problem.

Thanks,

Itzik.

On Mon, Nov 6, 2017 at 11:19 PM, Noam Weissman <address@hidden> wrote:

Hi Itzik,

I see that you have defined:

TCP_WND=(100 * TCP_MSS)

TCP_SND_BUF=TCP_WND

MEMP_NUM_TCP_SEG=TCP_SND_QUEUELEN

If TCP_MSS is defined 536 (default) that means that your TCP_WND is 53,600 bytes ?

and that is over a serial line ?

How much RAM do you have?, How much RAM is defined for TCP memory?

I never worked with PPP so I am a bit on the dark here.

From my experience with LwIP (over 6 years) Almost always it was misusing the stack or

doing something wrong.

You have written that you are using the Socket API. Normally Socket API is used with different

threads/task. If you do not use an OS why not use the RAW API ?

BR,

Noam. 

---

From: lwip-users <lwip-users-bounces+noam=silrdaddress@hidden> on behalf of Itzik Levi <address@hidden>
Sent: Monday, November 6, 2017 7:07 PM
To: address@hidden
Subject: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network?

 

Hi All, 

Firstly, a bit of background:

I'm currently evaluating lwip stack in order to determine whether it can fit my needs.

The end-goal, is integrating Socket API --> TCP/IP --> PPPoS stack on both sides over a serial-like-interface(stream-based)  which isn't reliable.

I decided to unittest it before actually integrating the stack.

Setup:

(This is done symmetrically on both "client" and "server")

1. Network Interface:
   1. The "physical layer" is currently a localhost connected tcp socket.
   2. Using pppapi in order to create the network interface.
   3. Its "output_cb" is the tcp connect socket(as mentioned before).
   4. Using "pppos_input_tcpip" which is fed by the same tcp socket.
2. Forming a TCP connection over the interface:
   1. Using lwip's bsd-like socket api.
   2. Single socket connection.
   3. Disabling Nagle.
   4. Working with a non-blocking sockets.
   5. Not writing and reading at the same time(mutex protected), but using lwip_poll in parallel to both.
3. Data validation:
   1. Transferring the same generated data client-->server and server-->client and validating at the same time.

Results:

• When not introducing losses to the physical layer, the data is passed and validated successfully without any issues.
• When starting to randomly introduce losses to the physical layer(basically drop some data when output_cb is being called), it seems to go well for minutes, but eventually it appears that I'm loosing data when sending.

I'm sure I'm doing something wrong here, can you please help me figure this thing out?

Pointers to debug such a case is also welcome!

I'm attaching lwip's debug logs from both client and server, when losses are introduced to both physical layer ends.

 

In this specific case some data that was sent from the client --> server, and the server failed to validate the data.

 

The last received valid stream offset is 19008, the next 400 bytes were incorrect(future data), basically I got some skipped data.

lwip configuration:

SYS_LIGHTWEIGHT_PROT=1

NO_SYS =0

LWIP_TCPIP_CORE_LOCKING=1

LWIP_TCPIP_CORE_LOCKING_INPUT=1

TCP_WND=(100 * TCP_MSS)

TCP_SND_BUF=TCP_WND

MEMP_NUM_TCP_SEG=TCP_SND_QUEUELEN

I used lwip's repo commit: 5d8d21fcae63c36005baf1b15e91268836dec679.

(which is lwip 2.0.3 plus some..)

Please tell me if any more info is required.

Thanks,

Itzik

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users