On 6to4 gateway and recommended MTU setting
phrickman at upcbroadband.com
Thu Mar 11 13:40:45 CET 2010
you need to consider the latency on pMTU in general with long paths as the negotiation needs to be distributed along each link - each negotiating locally and globally.
Statics cannot be configured only at 1280 as anything higher on your network would cause drops from an originating MTU along the path higher than 1280.
DD - +31 207 789 969
Mob: +31 610847604
From: ipv6-ops-bounces+ipv6=aorta.net at lists.cluenet.de [ipv6-ops-bounces+ipv6=aorta.net at lists.cluenet.de] On Behalf Of Martin List-Petersen [martin at airwire.ie]
Sent: 11 March 2010 13:39
To: Martin Millnert
Cc: ipv6-ops at lists.cluenet.de
Subject: Re: On 6to4 gateway and recommended MTU setting
Martin Millnert wrote:
> On Thu, 2010-03-11 at 12:05 +0000, Martin List-Petersen wrote:
>> Your underlying network is the factor, that limits you and that's the
>> IPv4 network. Remember, 6to4 is tunneling, just like 6in4.
>> So your MTU has to be smaller than 1500. EVERYONE is running 1280, why
>> do you want to run something else and break things even further.
> I've missed the memo saying that I should change it, if I run the
> gateway in Linux. :) I mean, that's why I'm asking. I'm missing a
> relevant section in a RFC stating that a global relay should be
> configured according to XYZ, due to ABC. Even after reading tens of RFCs
> multiple times, it can be hard to distill that XYZ.
I guess there has been no MTU specified in any RFC, because pMTU
discovery should be taking care of it. My point really is, that you
can't go beyond 1480 because you are tunneling over an unknown network,
where you have to assume that a lot of it is no higher than 1500, if not
less. The vast majority of end-users will be sitting behind a PPPoE or
PPPoA tunnel, so they have less than 1500.
1280 has sort of been adapted for 6in4 tunneling and thus most 6to4
implementations follow that same setup.
More information about the ipv6-ops