[ moved to net@; current@ bcc'ed ]
Hi Craig,
I think I saw the same behaviour while developing a path-mtu discovery
tool. As I'm quite busy right now I didn't really dig into it, but I will
at some point.
I took the liberty to reply to freebsd-net@, because this is not only a
-CURRENT problem.
I was trying some network diagnostics yesterday and needed to generate a
continuous stream of small packets going across a few routers. So I
used ifconfig to set my MTU to some very low values (100, 300, 500, and
a few others). I know there's probably a better way to accomplish that,
but couldn't
