rohc team mailing list archive

[Didier Barvaux <didier@xxxxxxxxxxx>]

Hello,

>    I have some more information about the issues I have with our
> kernel implementation:
> 
> I have several network namespaces set up in a chain, so packets from
> one end will be transmitted to the receiver on the other end. I have
> 2 simple tcp_server and tcp_client applications - the server listens
> on port 5000 and the client sends packets as fast as possible to the
> server.   The transmission is 1-directional, from client to server.
> The only packets coming back from the server are ACK's, specifically,
> SACK packets.   I have modified the code to compress only packets
> from the client and leave the ACK's from the server in the clear.
> There are no issues with the compressed packets traversing over 5
> namespace nodes in a chain.  Then I disable the compression on the
> sending client, and enable the compression on the ACK's.  Then I see
> all the problems with the inconsistent option lists and packet
> lengths, as I explained to you before.
> 
> Hope this additional information is helpful.

Yes, it is. Your setup looks fine, the ROHC protocol and library should
be able to handle this situation just fine (except the library bugs of
course).

Regards,
Didier