problems with TCP send sizes greater than ETH_PKTSIZE (SAMA5D36)

Hi, I'm still having problems with TCP sending and receiving on the SAMA5D36. I switched from tcpblaster to tcpecho. That works as long as whatever send I do from the host linux computer is shorter than the MTU or ETH_PKTSIZE (right now, configured to be 1500 bytes). I'm using the SAMA5D36 GMAC (g

Re: problems with TCP send sizes greater than ETH_PKTSIZE (SAMA5D36)

I'm still having problems with TCP sending and receiving on the SAMA5D36. I switched from tcpblaster to tcpecho. That works as long as whatever send I do from the host linux computer is shorter than the MTU or ETH_PKTSIZE (right now, configured to be 1500 bytes). I'm using the SAMA5D36 GMAC (gi

Re: problems with TCP send sizes greater than ETH_PKTSIZE (SAMA5D36)

Hey Greg, Thanks for the help. Yeah I forgot the ethernet frame size. But– shouldn't I be able to send TCP data regardless of MSS? Why should the MSS matter at the TCP network layer? I was using the nuttx master branch from several weeks ago. Just updated to the latest master, and things are muc

Re: problems with TCP send sizes greater than ETH_PKTSIZE (SAMA5D36)

Greg, My question about MSS wasn't clear– what I mean is, to an application (like tcpecho or tcpblaster), the size of MSS shouldn't matter. Shouldn't the application be able to send as many bytes as it wants? The TCP stack divides the stream up into chunks (of MSS length) and transmits them... sen