Re: Yes, I know this is the wrong mailing list

George Mitchell <george+ipng@m5p.com> Wed, 11 July 2012 02:04 UTC

Return-Path: <george+ipng@m5p.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754D411E80E4 for <ipv6@ietfa.amsl.com>; Tue, 10 Jul 2012 19:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.671
X-Spam-Level:
X-Spam-Status: No, score=-1.671 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jO0EEkEIp+bO for <ipv6@ietfa.amsl.com>; Tue, 10 Jul 2012 19:04:55 -0700 (PDT)
Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by ietfa.amsl.com (Postfix) with ESMTP id ADD0311E8072 for <ipv6@ietf.org>; Tue, 10 Jul 2012 19:04:53 -0700 (PDT)
Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.4/8.14.4) with ESMTP id q6B25Gwv066348; Tue, 10 Jul 2012 22:05:21 -0400 (EDT) (envelope-from george+ipng@m5p.com)
Message-ID: <4FFCDF5C.80809@m5p.com>
Date: Tue, 10 Jul 2012 22:05:16 -0400
From: George Mitchell <george+ipng@m5p.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120623 Thunderbird/13.0.1
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Yes, I know this is the wrong mailing list
References: <4FFCCD9A.10605@m5p.com> <20120711013529.9966D2250F19@drugs.dv.isc.org>
In-Reply-To: <20120711013529.9966D2250F19@drugs.dv.isc.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Tue, 10 Jul 2012 22:05:22 -0400 (EDT)
X-Scanned-By: MIMEDefang 2.72 on 10.100.0.3
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 02:04:56 -0000

On 07/10/12 21:35, Mark Andrews wrote:
> In message <4FFCCD9A.10605@m5p.com>, George Mitchell writes:
>> So I was trying to browse the list of IETF mailing lists at www.ietf.org
>> to see who might be interested in my failures to browse sites like
>> yahoo.com and netflix.com following the onset of World IPv6 Day.
>>
>> Except that I can't browse www.ietf.org either.
>>
>> It did work previously.  I have a packet capture of the failing "telnet
>> www.ietf.org 80" session, if anyone is interested.  It looks fine and
>> proper, all the expected SYNs and ACKs as I sent my HTTP request,
>> except for the failure to return any HTTP response.  I'm running
>> FreeBSD 9.0-STABLE.  8.2-STABLE also fails the same way.  No doubt you
>> can reach www.m5p.com over IPv6; it's been working for years.
>>
>> Would one of you be able to tell me which mailing should I be using?
>> My apologies for the inappropriate message.         -- George Mitchell
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
> This sort of failure is usually a PMTUD failure.  If you are using
> a tunnel you need to ensure that your tunnel provider sends back
> PTB's.  The IETF servers do see the PTB's.  www.ietf.org does work
> over tunnels.
>
> You can test this theory by lowering the local mtu using "route
> change -inet6 :: -mtu 1280" (from memory).  This will change the
> advertised mss from 1440. "route -n get -inet6 ::" will show you
> the current values.
>

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