How are you?

After a long time spent in this issue with debugging in my network drive
(socket raw), lwip configuration tuning (lwipopts.h), my client code, etc,
etc; I noted (using simhost -d) that large packets  caused check-sum error
in the lwip received side. So by searching in the internet, I found links
relating to "offload segmentation".
Resuming,  when I disable the "gro" (generic-receive-offload) of the NIC
that treats the lwip packets the problem disappears.
Command (for eth0):   > sudo ethtool -K eth0 gro off
Verification:                > ethtool -k eth0 | grep
generic-receive-offload

Please, does this make sense?
Thanks.


Em sex, 21 de dez de 2018 às 15:20, Norberto R. de Goes Jr. <
[email protected]> escreveu:

> Hi all, how are you doing?
>
> I updated the lwip and lwip-contrib codes:
>     - lwip:   159e31b (HEAD, tag: STABLE-2_1_2_RELEASE) Prepare 2.1.2
> release
>     - lwip-contrib:  35b011d (HEAD, tag: STABLE-2_1_0_RELEASE,
> origin/master, origin/HEAD, master) Fix compiling lwiperf_example.c with
> TCP disabled
>
> The altered files are attached:
>     - .../lwip-contrib/apps/tcpecho/tcpecho.c
>     - .../lwip-contrib/examples/example_app/lwipopts.h
>     - .../lwip-contrib/ports/unix/example_app/default_netif.c
>     - .../lwip-contrib/examples/example_app/lwipcfg.h
>
> The same sequence/setup reported in my first email of this current
> thread.  Just the "simhost" executable was replaced by the "example_app"
> (lwip-contrib contet was altered).
>
> But the behavior is the same, there is a blocking when large packets (+/-
> 1100 bytes) are sent by the client.
> I attached too a wireshark trace where we can see tcp-dup_ack and
> tcp-retransmission packets.
>
> Please, any suggestion?
> Thanks you very much.
>
>
> Em ter, 18 de dez de 2018 às 18:01, [email protected] <[email protected]>
> escreveu:
>
>> Am 18.12.2018 um 11:15 schrieb Norberto R. de Goes Jr.:
>> > Hi all. Thanks David Gauchard!
>> >
>> > Unfortunately I have been used an old LWIP version in my project, that
>> > is in production. I will have problems to update that.
>> > Please, then does the older versions have this kind of bug I reported?
>>
>> None that I directly know of, but this kind of behaviour can be the
>> result of many bugs or misconfigurations. So while I think it's not a
>> bug in lwIP itself (this would have popped up before), I tend to think
>> it's not just gone by upgrading lwIP. I guess it's something in your
>> port or application (usage of lwIP) that triggers this.
>>
>> > Or the configuration (lwipopts.h and/or opt.h) can solve that behavior?
>>
>> Sorry, digging into your config is not a thing I can do right now.
>> Debugging such an issue takes more time.
>>
>> Regards,
>> Simon
>>
>> >
>> > Regards.
>> >
>> >
>> >
>> >
>> >
>> > Em seg, 17 de dez de 2018 às 10:35, David Gauchard <[email protected]
>> > <mailto:[email protected]>> escreveu:
>> >
>> >
>> >     Have you tried with LWIP_TCP_SACK_OUT option enabled ?
>> >     This option alone solves quite a number of issues on some low-mem
>> >     devices.
>> >
>> >     To use it you would need to upgrade to lwIP-2.1.2.
>> >
>> >     I must take this opportunity to thank all lwIP devs for their work,
>> >     this is much appreciated (I'm speaking from esp8266/arduino
>> community).
>> >
>> >     david
>> >
>> >     On Mon, Dec 17, 2018 at 09:26:55AM -0200, Norberto R. de Goes Jr.
>> wrote:
>> >      > Please, anybody could help me in this my issue?
>> >      > Thanks!
>> >      > Norberto Goes
>> >      >
>> >      >
>> >      >
>> >      > Em dom, 9 de dez de 2018 às 19:18, Norberto R. de Goes Jr. <
>> >      > [email protected] <mailto:[email protected]>> escreveu:
>> >      >
>> >      > > Hi, how are you?
>> >      > >
>> >      > > I have been used the LWIP library for several years already.
>> >      > > Now I developed a new application that exchange larger packets,
>> >     like 2K
>> >      > > bytes.
>> >      > >
>> >      > > Commits in use (SHA-1) :
>> >      > >  - lwip :           d70d9bf8660827e2919d5fc9c9469532196225e1
>> >      > > - lwip-contrib:   4e553f7b3d3af4ac1f3f6c70f38371e4395fdccd
>> >      > >
>> >      > > To simulate my real scenario and you can try  to reproduce the
>> >     problem I
>> >      > > am facing,  I have made alterations in the "simhost.c",
>> >     "lwipopts.h"  and
>> >      > > "tcpecho.c" from lwip-contrib. The ethernet data for teh netif
>> >     is  provided
>> >      > > by a socket-raw driver (Linux). The tcpecho just consume the
>> >     data,  no
>> >      > > reply (no echo). The "simhost" (server) is generated with the
>> >     own Makefile
>> >      > > associated avaliable in the "lwip-contrib" git.
>> >      > >
>> >      > > In addition, I wrote a small "client" (use the TCP-IP/Linux
>> stack).
>> >      > > When the "client" sends small packets, all works fine. But when
>> >     it sends
>> >      > > larger packets (for instance, 2048 bytes), just the first are
>> >     sent fast
>> >      > > (normal) but just after the locking occurs.
>> >      > >
>> >      > > Summary:
>> >      > > a) 02 Oracle VMBox (VM#1 and #2) - Linux host
>> >      > >
>> >      > > b)  Sequence to run:
>> >      > >    - VM#1 (server):
>> >      > >      >  sudo  your_path1/simhost
>> >      > >    - VM#2 (client):
>> >      > >      >  your_path2/client ip_netif  port  size_data
>> >      > >        - example:    >  ./client 10.0.2.121  5124   2065  /*
>> >     block */
>> >      > >        - example:    >  ./client 10.0.2.121  5124   1000  /* no
>> >     block  */
>> >      > >
>> >      > >  c) Altered files (from lwip-contrib), attacheds:
>> >      > >         - .../apps/tcpecho/tcpecho.c
>> >      > >         - .../ports/unix/proj/unixsim/lwipopts.h
>> >      > >         - .../ ports/unix/proj/unixsim/simhost.c
>> >      > >
>> >      > >  d) Client app (attacheds files)
>> >      > >
>> >      > > Just to compare, when I use another server with TCP-IP/Linux,
>> >     not LWIP
>> >      > > stack, but the same attached client,  no problem found,
>> >     including larger
>> >      > > packets.
>> >      > >
>> >      > > Please, what I am doing or configuring wrong ?
>> >      > > Thank you very much.
>> >
>> >     _______________________________________________
>> >     lwip-users mailing list
>> >     [email protected] <mailto:[email protected]>
>> >     https://lists.nongnu.org/mailman/listinfo/lwip-users
>> >
>> >
>> >
>> > --
>> > Norberto R. de Goes Jr.
>> > CPqD - DRC
>> > Tel.: +55 19 3705-4241 / Fax: +55 19 3705-6125
>> > [email protected] <mailto:[email protected]>
>> > www.cpqd.com.br <http://www.cpqd.com.br/>
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>
>
>
> --
> Norberto R. de Goes Jr.
> CPqD - DRC
> Tel.: +55 19 3705-4241 / Fax: +55 19 3705-6125
> [email protected] <[email protected]>
> www.cpqd.com.br
>
>
>

-- 
Norberto R. de Goes Jr.
CPqD - DRC
Tel.: +55 19 3705-4241 / Fax: +55 19 3705-6125
[email protected] <[email protected]>
www.cpqd.com.br
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to