Unable to ping device with MTU 9000 (jumbo frame), but default ping error message shows up

I need to set a local connection with Jumbo Frames enabled.

I set up my network adapter to have a MTU of 9000.

~$ ifconfigeth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9000        inet 10.0.0.3  netmask 255.255.255.0  broadcast 10.0.0.255        inet6 fe80::215:5dff:fe8a:1792  prefixlen 64  scopeid 0x20<link>        ether 00:15:5d:8a:17:92  txqueuelen 1000  (Ethernet)        RX packets 0  bytes 0 (0.0 B)        RX errors 0  dropped 0  overruns 0  frame 0        TX packets 5  bytes 398 (398.0 B)        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I checked my network adapter settings, everything is okay. I am using WSL2 and the MTU size is 9000 in Ubuntu and on my network adapter settings (using netsh and Get-NetAdapterAdvancedProperty from Powershell).

However, when I ping my reomte device (IP 10.0.0.10) by specifying the packet size, I get a fail. The strange thing is that it is not the "large packet" error message that displays, but simply the "ping failed". To compare, let me show you the result of a normal ping (#1), a ping with a packet too large (#2), and a ping with a packet that should be handled by the jumbo frame (#3).

# 1.~$ ping 10.0.0.10PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data.64 bytes from 10.0.0.10: icmp_seq=2 ttl=64 time=1.49 ms# 2.~$ ping 10.0.0.10 -c 10 -M do -s 10000PING 10.0.0.10 (10.0.0.10) 10000(10028) bytes of data.ping: local error: message too long, mtu=9000# 3. ~$ ping 10.0.0.10 -c 10 -M do -s 8900PING 10.0.0.10 (10.0.0.10) 8900(8928) bytes of data.--- 10.0.0.10 ping statistics ---10 packets transmitted, 0 received, 100% packet loss, time 9368ms

As you see, behavior #1 and #2 are normal, but not #3. The packet size is not too big to be handled by MTU (or else, I would have had the same error as #2).

I looked this problem up online and the answer I found was: my PC is configured correctly, but the receiving device does NOT have a MTU big enough. However, this device is specifically made to handle these large packets, I contacted the device's maker and they told me that it natively handles jumbo frames.

The problem seems to be on my connection, but I can't find anything.