MTU Blackhole problem?
cswiger at mac.com
Tue Sep 7 10:13:43 PDT 2004
On Sep 7, 2004, at 7:46 AM, R. W. wrote:
> I'm guessing that this is a path MTU discovery blackhole, since if I
> sysctl net.inet.tcp.sendspace=400 the problem goes away. (I presume
> that net.inet.tcp.path_mtu_discovery: 1 means that path MTU discovery
> is already turned-on by default.)
> What the correct way to deal with this? Should I just play around with
Try "ifconfig en0 mtu 512"; replace en0 with the name of your NIC.
[ Try different MTUs, too. ]
More information about the freebsd-questions