This sounds even more like a driver issue.
Am 1. August 2018 10:45:26 MESZ schrieb Mike Danby <[email protected]>: >When the test program is run for the first 3-5 seconds the each send >call will result is the string (approx. 15 bytes) being transmitted to >the client in separate frames. After that (even though the calls to >send continue at a rate of 1Hz) the strings start to get packaged up >into single frames. The number of strings in the packaged frames grows >on a few iterations to be around 20 -25 (frames around 300 bytes). > >I also see the server respond to ARP requests, however the frame is >1514 bytes. The data in the ARP request is correct but Wireshark notes >the "Ethernet Frame Check Sequence Incorrect", I assume (probably >incorrectly) because the frame size incorrect even though data is good. > >-----Original Message----- >From: lwip-users <[email protected]> >On Behalf Of Sergio R. Caprile >Sent: 31 July 2018 16:38 >To: [email protected] >Subject: Re: [lwip-users] Socket API send command packaging up data > >Completely missed the "20 second" part. >You don't remember wrong, and you know it ;^) > >_______________________________________________ >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
