Re: [v4tov6transition] Ways to break IPv6

Joel Jaeggli <> Wed, 13 October 2010 06:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5FD0F3A68E4 for <>; Tue, 12 Oct 2010 23:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.342
X-Spam-Status: No, score=-102.342 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 28wadCa424sJ for <>; Tue, 12 Oct 2010 23:48:28 -0700 (PDT)
Received: from ( [IPv6:2001:418:1::81]) by (Postfix) with ESMTP id AC5E93A68C7 for <>; Tue, 12 Oct 2010 23:48:27 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id o9D6ncM0019475 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 13 Oct 2010 06:49:42 GMT (envelope-from
References: <>
Message-Id: <>
From: Joel Jaeggli <>
To: Ed Jankiewicz <>
In-Reply-To: <>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (7B405)
Mime-Version: 1.0 (iPad Mail 7B405)
Date: Tue, 12 Oct 2010 23:49:46 -0700
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 ( []); Wed, 13 Oct 2010 06:49:43 +0000 (UTC)
Cc: "" <>
Subject: Re: [v4tov6transition] Ways to break IPv6
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Oct 2010 06:48:30 -0000

I love how we talk about what they will do in the future tense. They do this today. my corporate laptops have had v6 broken in various sundry ways by bad policy and retarded security products across three employers since 2007. As long as v6 has been enabled in systems  people have been disabling it deliberately, or worse, breaking it in ways that make you wonder how these companies keep v4 working, in point of fact sometimes they don't. 

Joel's widget number 2

On Oct 12, 2010, at 19:40, Ed Jankiewicz <> wrote:

> this is not a surprise, it is something that has been predicted by many as one of the "growing pains" of IPv6 transition.  Firewalls and other security software will "support" IPv6 initially by just blocking it - too much work (and too little demand) for a real implementation.
> Just loaded an updated version of the commercial anti-virus package that I've been using, let it remain nameless, it is certainly not the only offender in this area.  Unlike the previous version this includes an enhancement - it blocks all IPv6 and IPv6 over IPv4 traffic by default.  The firewall rule can be disabled.
> If you are a network operator, there is a lot of mischief that can be done by software that the end-user downloads onto their machines that can make IPv6 appear broken.  This is another area that should get some attention - how will customer service and help desk people be trained to deal with "connectivity" problems the user can cause themselves?
> It took me a while to figure this out, and I'm one of the people who frequently predicted this would happen.  Imagine your average end-user who knows nothing about IPv6 and expects that "it just works".  Also, many books, websites and other security advice says "when in doubt, turn off IPv6".  At least in the foreseeable future, this will continue to be impedance against the uptake of IPv6.
> -- 
> Ed Jankiewicz - SRI International
> Fort Monmouth Branch Office - IPv6 Research
> Supporting DISA Standards Engineering Branch
> 732-389-1003 or
> _______________________________________________
> v4tov6transition mailing list