I frequently use mtr to check that Jumbo Frames work on my packet path.
Up until 0.95 mtr allowed me to set --psize whatever, but 0.96 clamps
packet size to 28-4470, which is smaller than typical Jumbo Frame
networks in the 2020s.

My needs would be fulfilled by 9000, but most Intel 10G cards support
much bigger packet sizes like 16384, so having an upper limit does not
really make sense. Let the socket API decide if the packet size is OK or
not.

I do understand the minimum packet size limitation tho.

Best Regards,

Hi again,

Workaround in file ui/mtr.h: set MAXPACKET to something bigger

Someone also created an issue at upstream:

https://github.com/traviscross/mtr/issues/553

BR,