Re: [v6ops] When IPv6 breaks IPv4

João Butzke <lista-gter@tbonet.net.br> Wed, 25 April 2018 18:03 UTC

Return-Path: <lista-gter@tbonet.net.br>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 538C5129C56 for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 11:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IM_rrivuG5Fh for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 11:03:39 -0700 (PDT)
Received: from smtp-sp201-44.kinghost.net (smtp-sp201-44.kinghost.net [177.185.201.44]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1930912895E for <v6ops@ietf.org>; Wed, 25 Apr 2018 11:03:38 -0700 (PDT)
Received: from [10.10.10.59] (unknown [168.227.132.42]) (Authenticated sender: lista-gter@tbonet.net.br) by smtp-sp201-44.kinghost.net (Postfix) with ESMTPA id 700FA200F7A7 for <v6ops@ietf.org>; Wed, 25 Apr 2018 15:03:33 -0300 (-03)
To: v6ops@ietf.org
References: <5e02c3d9-5382-205e-f552-496da5c529bc@gmail.com>
From: João Butzke <lista-gter@tbonet.net.br>
Message-ID: <a9f102f7-419c-b32c-ab8e-769a245fcb5c@tbonet.net.br>
Date: Wed, 25 Apr 2018 15:03:31 -0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5e02c3d9-5382-205e-f552-496da5c529bc@gmail.com>
Content-Type: multipart/alternative; boundary="------------FC95893EAC7AB1313D43C39F"
Content-Language: pt-BR
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LK9-IU_vKz-SyHHEh2XQIXLr2DY>
Subject: Re: [v6ops] When IPv6 breaks IPv4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2018 18:03:42 -0000

Thats a sad story, RIP TABLET.

Today we are having some issues with MikroTik, i updated the routers for 
the new version because of a winbox vulnerability and now ipv6 on my 
network is DEAD.

Some brands do not give the proper attention to IPv6 and things like 
that happen, very sadly.

Trying to solve wtf is happening.

Best Regards,
João Butzke.

Em 25/04/2018 13:26, Alexandre Petrescu escreveu:
> There was a presentation at an IETF meeting in v6ops, about when 
> people recommend to rather turn off IPv6 on some consumer electronics 
> (Netgear was that?).  The GUI was telling in red characters to rather 
> turn off IPv6, instead of risking IPv4 not working either.
>
> Today I had a similar experience.
>
> The hardened Android tablet Aaeon by ASUS (described in 
> AAEON_RTC-700B.PDF) has an Ethernet port which is great.  The Android 
> GUI allows to set an IPv6 address in a field.  I put there "1::1" 
> because it is very fast to type on a virtual keyboard.  After that, 
> the Ethernet stopped working in IPv4 altogether.  Long press reboot 
> button does not solve it. There is no means to revert back, not 
> possible to remove that IPv6 address.
>
> Now I can throw out a window this tablet, for two reasons: neither 
> IPv6 is working, nor IPv4 is working.  There is no reset button, no 
> documentation about 'cold reset' and there are are two batteries: one 
> main and one backup.  The backup can be removed but the main is 
> hardened.  I suspect that even if the main battery dies out the GUI 
> config file containing that "1::1" will still be there for many years 
> a writeable RAM lasts.
>
> Worse, I did this in front of partner, in my good intentions to 
> illustrate proof how IPv6 is so present everywhere already.
>
> Next time I will be more moderate about my trust in IPv6 availability.
>
> Alex
>
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops