Sending data packets will cause network blocking between TX2 and the Terminal Equipment

Hello there

Use a network cable to directly connect the TX2 development board (without passing the switch) to an embedded device terminal, and ping the data packet to the TX2 at the embedded device terminal. When the data size exceeds about 15000 (ping -s 15000 10.168.3.1), the network will be Blocking, the embedded device prompts “no buffer space available”. And also pings the packet to the embedded device terminal on the TX2 side,if the packet size exceeds 15000, the network will be blocked. When both TX2 and embedded device terminals are connected through the switch, the network is normal when the data packets are pinged between each other. This problem occurs only when TX2 and the embedded device terminal are directly connected through the network cable.

At the same time, the TX2 and x86 computers were directly connected with the network cable, the embedded device terminal and the x86 computer network cable were directly connected, and the TX2 ping x86 computer was tested, the embedded device terminal ping x86 computer was tested, both the network was working normally without network congestion.

The operating system version of TX2 is ubuntu16.04 LTS. The operating system version of the embedded device terminal is ARM Linux 5.4.

What is the reason that may be caused?

Hi zhouxs,

We don’t have experience on this use case, hope someone could share their result if they ever done something similar.

I’m just speculating, but it makes me wonder if this is what is going on:
https://en.wikipedia.org/wiki/Ping_of_death

Part of the reason for speculation is if the MTU is 1500, then probably the MRU was also 1500, and larger sizes would result in fragmentation. Once fragmentation occurs, then the description from the above URL would be possible.

Is this just an academic question, or do you have some reason to need this to work?