From owner-freebsd-wireless@FreeBSD.ORG  Mon Jul 29 13:34:09 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 94F6EC19;
 Mon, 29 Jul 2013 13:34:09 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com
 [IPv6:2a00:1450:400c:c03::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 038122670;
 Mon, 29 Jul 2013 13:34:08 +0000 (UTC)
Received: by mail-we0-f177.google.com with SMTP id m46so3933191wev.22
 for <multiple recipients>; Mon, 29 Jul 2013 06:34:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type
 :content-transfer-encoding;
 bh=mmE+VAjDh074+YgxCoSONDwyZOBeaNogLZ/zrCE6I2A=;
 b=qEEzHTLNt0cF2twqsz2pqlsY4potBmPtKnhAX3TlbemSsv1211ZKkcry5DeVJFOm8h
 cFQX4hmoO+DVvN1otnAiv23+ZtX9odMWiNBmqX+8Vo56JtrOzqUraRlgccktQsLTH1ki
 P3O1pD329Yta0xysPPs336oQCEFqmyYiQsoErsIffhBEVMvEfo3UABxTJlmeLmUBkNXh
 YgSbVxIz4wHd2N6bzTRo7/nkYb9MDZb+p9EqmsMH7PTgITzs6TU/1vkqShlIbV1P0+FJ
 j7VLrHaKzQRp6vMNX3tkrz6ODNYgZEwiP8aNnKuzuqqMYgTwU4JET9oH4WX2X/tIwHeN
 5EmQ==
MIME-Version: 1.0
X-Received: by 10.180.14.105 with SMTP id o9mr7266052wic.30.1375104847255;
 Mon, 29 Jul 2013 06:34:07 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.217.94.132 with HTTP; Mon, 29 Jul 2013 06:34:07 -0700 (PDT)
In-Reply-To: <20130729095946.GK59101@e-new.0x20.net>
References: <51F26CEB.9010200@dumbbell.fr>
 <20130729095946.GK59101@e-new.0x20.net>
Date: Mon, 29 Jul 2013 06:34:07 -0700
X-Google-Sender-Auth: S1Rb5zAvRjZesYjXG48REUDuOl0
Message-ID: <CAJ-Vmo=yw-jL+T2QUfiOfx8oGZweNt+gWFBaVriVPtWsrVCEiA@mail.gmail.com>
Subject: Re: 802.1X: dhclient started before the auth. process ends
From: Adrian Chadd <adrian@freebsd.org>
To: Lars Engels <lars.engels@0x20.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: =?ISO-8859-1?Q?Jean=2DS=E9bastien_P=E9dron?=
 <jean-sebastien.pedron@dumbbell.fr>, freebsd-current@freebsd.org,
 wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2013 13:34:09 -0000

I think you were lucky.

dhclient shouldn't start running until wpa_supplicant has completed
authentication.


-adrian

On 29 July 2013 02:59, Lars Engels <lars.engels@0x20.net> wrote:
> On Fri, Jul 26, 2013 at 02:34:51PM +0200, Jean-S=E9bastien P=E9dron wrote=
:
>> Hi!
>>
>> At $WORK, we use 802.1X to authenticate computers on the network.
>> Authenticated computers receive a lease in the 192.168.X.X/24 network.
>> Unauthenticated ones receive a lease in the 172.16.X.X/24 network.
>>
>> Today, I upgraded one computer running 10-CURRENT to latest HEAD and it
>> seems that the interface is brought up to early now: dhclient is started
>> before wpa_supplicant finishes. This was working perfectly before the
>> upgrade.
>>
>> I don't have logs of the working case, but here are the logs of the
>> non-working one:
>> http://pastebin.com/ZHcbHLQZ
>>
>> Was I lucky with wpa_supplicant/dhclient timing? Or is there a real
>> issue here?
>>
>
> CC'ed wireless@, that's probably the proper list for the issue.