IETF Logo Mail Archive

Re: [100attendees] further on nat64 - other SSID problems (not v4/v6)

Alexandre PETRESCU <alexandre.petrescu@cea.fr> Mon, 20 November 2017 18:45 UTC

Return-Path: <alexandre.petrescu@cea.fr>
X-Original-To: 100attendees@ietfa.amsl.com
Delivered-To: 100attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E1CD12704B for <100attendees@ietfa.amsl.com>; Mon, 20 Nov 2017 10:45:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 hi4MPn7657Rb for <100attendees@ietfa.amsl.com>; Mon, 20 Nov 2017 10:45:37 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D7B312E05C for <100attendees@ietf.org>; Mon, 20 Nov 2017 10:45:37 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAKIjY9a009377; Mon, 20 Nov 2017 19:45:34 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D6044208A31; Mon, 20 Nov 2017 19:45:34 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C5B90208993; Mon, 20 Nov 2017 19:45:34 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAKIjYVv006907; Mon, 20 Nov 2017 19:45:34 +0100
To: joel jaeggli <joelja@gmail.com>, 100attendees@ietf.org
References: <074664C2-8231-4DFD-83B3-3AEA4E96AD38@daedelus.com> <m27euxreju.wl-randy@psg.com> <D6347C83.8C332%lee@asgard.org> <2D09D61DDFA73D4C884805CC7865E6114DCB8917@GAALPA1MSGUSRBF.ITServices.sbc.com> <CAFU7BAT8-k7grwZ+YwUCwiOuUQbyQbYhfvUVC45G=c6G8dTe6A@mail.gmail.com> <2D09D61DDFA73D4C884805CC7865E6114DCBB7CC@GAALPA1MSGUSRBF.ITServices.sbc.com> <559FB87E-FB9D-4F25-8D21-E318BFD27E59@gmail.com> <284f573b-8073-1f50-849c-8d1438d8ec21@cea.fr> <1ac20414-95b5-376b-b5ee-e45fdad06959@gmail.com>
From: Alexandre PETRESCU <alexandre.petrescu@cea.fr>
Organization: CEA
Message-ID: <8ccc733e-7686-6cd4-9706-deff66f2727e@cea.fr>
Date: Mon, 20 Nov 2017 19:45:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <1ac20414-95b5-376b-b5ee-e45fdad06959@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms000509000504000202080100"
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/30tvJbzvPXw37gkuUUkya0mtsl8>
Subject: Re: [100attendees] further on nat64 - other SSID problems (not v4/v6)
X-BeenThere: 100attendees@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Mailing list of IETF 100 attendees that have opted in on this list." <100attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/100attendees>, <mailto:100attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/100attendees/>
List-Post: <mailto:100attendees@ietf.org>
List-Help: <mailto:100attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/100attendees>, <mailto:100attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 18:45:40 -0000

Le 20/11/2017 à 19:07, joel jaeggli a écrit :
> On 11/20/17 08:48, Alexandre PETRESCU wrote:
>> For example, the "ietf-legacy" SSID has been very unstable in large
>> meeting rooms (e.g. v6ops, plenary) vs small meeting rooms.  And that
>> was so since it was invented a few IETFs back.  On "ietf-legacy" my VPN
>> was up alive for no more than 5 minutes or so in large meeting rooms,
>> but it was up alive during the entire meeting if the meeting room was small.
>>
>> That 'legacy' word has nothing to do with IPv4 or IPv6, but it is about
>> the authentication scheme and the frequency band.
> The legacy ssid is delivered on the same radios and frequency bands as
> the other mixed 2.4 and 5ghz ssids. legacy is not encrypted so it's not
> clear what you mean by authentication scheme.

That's what I meant - no encryption.

>   legacy is intended to have
> largely identical behavior to ietf prior to that having wpa2 enterprise
> enabled.

YEs.

As we discussed separately, that wpa2 enterprise constituted a big 
problem for my laptop.

Alex

>
> ietf ietf-v6ONLY ietf-nat64 were 5ghz only.
>
>
>> There were other problems as well.
>>
>> Alex
>>
>>>>> What OS/Jabber client were you using?
>>>> Psi
>>> Same here and I had no problems on the ietf network.
>>>
>>> Yoav
>>>
>>>
>>> _______________________________________________
>>> 100attendees mailing list
>>> 100attendees@ietf.org
>>> https://www.ietf.org/mailman/listinfo/100attendees
>>
>>
>> _______________________________________________
>> 100attendees mailing list
>> 100attendees@ietf.org
>> https://www.ietf.org/mailman/listinfo/100attendees
>>
>

v2.23.0 | Report a Bug | By Email