On 2012-07-11 04:54, Mark Andrews wrote: [..] >> And so I don't have to do it repeatedly, I can change /etc/rc.conf from: >> ipv6_defaultrouter="2001:418:3fd::fd" >> to: >> ipv6_defaultrouter="2001:418:3fd::fd -mtu 1280" >> >> I appreciate all the help! -- George > > You really should talk to your tunnel provider and get this fixed as > this only helps TCP connections. It does not help UDP based > protocols. Once your tunnel provider has fixed the tunnel ingress > to correctly sent PTB's you will then be in a position to report > broken web sites.
I am fairly sure that NTT does generate and pass through PTBs, if the user filters them incoming is a different question though. The problem in this case seems to be the forgetting to configure an MTU on an tunnel. A better thing is to ask/check what the real MTU of the tunnel is. Likely it is even up to 1480 depending on the underlying path. Of course even better is to get rid of the tunnel and go native ;) On 2012-07-11 03:38, George Michaelson wrote: > IETF should be running on a clamped MSS. The only benefits of > floating MTU upwards is an efficiency gain which is almost irrelevant > for a text-mainly website of this nature. > > It would be lovely if they could rely on the other end, but a > governance body should be reachable all the time. No, the connectivity on the side of the user should be configured properly. Adding hacks is not the way to go and does not solve the general problem of misconfiguration that one can't hack around. Greets, Jeroen -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
