Re: Yes, I know this is the wrong mailing list
Thomas Dineen <tdineen@ix.netcom.com> Wed, 11 July 2012 16:22 UTC
Return-Path: <tdineen@ix.netcom.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 21DFD21F8665 for <ipv6@ietfa.amsl.com>; Wed, 11 Jul 2012 09:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 6QvutcdxT1va for <ipv6@ietfa.amsl.com>; Wed, 11 Jul 2012 09:22:16 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id DF93321F85F0 for <ipv6@ietf.org>; Wed, 11 Jul 2012 09:22:15 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=ZrB81J+LLb393dATQfxzFFQK8jgdtKOhPqDWwGkkPnaqr4PCw9OX1SCNbkluhvRe; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [71.94.23.76] (helo=[192.168.0.2]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tdineen@ix.netcom.com>) id 1SozgG-0006wR-O6; Wed, 11 Jul 2012 12:22:24 -0400
Message-ID: <4FFDA840.6080609@ix.netcom.com>
Date: Wed, 11 Jul 2012 09:22:24 -0700
From: Thomas Dineen <tdineen@ix.netcom.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: George Mitchell <george@m5p.com>
Subject: Re: Yes, I know this is the wrong mailing list
References: <4FFCCD9A.10605@m5p.com> <20120711013529.9966D2250F19@drugs.dv.isc.org> <4FFCDB23.9000109@m5p.com>
In-Reply-To: <4FFCDB23.9000109@m5p.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 8fd196f32229d336776432462e451d7bb721073b08cf141fe1e7b2145cf0c0c86ec8acde450591e7350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.94.23.76
Cc: ipv6@ietf.org, Mark Andrews <marka@isc.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 16:22:17 -0000
Why don't you just use IPv4 and stop bothering us???????? We are busy to busy with the next boondoogle to worry about IPv6 Bugs!!!!!! Thomas Dineen On 7/10/2012 6:47 PM, George Mitchell wrote: > 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. >> > > Thanks very much -- your diagnosis is correct! Using > "route change -inet6 :: -mtu 1280" fixed the problem for www.ietf.org > and all the other sites I've been having problems with, too. > > We now return you to your normal working group traffic. -- George > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > >
- Yes, I know this is the wrong mailing list George Mitchell
- Re: Yes, I know this is the wrong mailing list Mark Andrews
- Re: Yes, I know this is the wrong mailing list George Mitchell
- Re: Yes, I know this is the wrong mailing list Mark Andrews
- Re: Yes, I know this is the wrong mailing list George Michaelson
- Re: Yes, I know this is the wrong mailing list Glen
- Re: Yes, I know this is the wrong mailing list Jeroen Massar
- Re: Yes, I know this is the wrong mailing list George Mitchell
- Re: Yes, I know this is the wrong mailing list Simon Perreault
- Re: Yes, I know this is the wrong mailing list Thomas Dineen