From owner-freebsd-current@freebsd.org Tue Sep 1 08:44:45 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3146A9C699D for ; Tue, 1 Sep 2015 08:44:45 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AB2D615D5 for ; Tue, 1 Sep 2015 08:44:43 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.15.2/8.15.2) with ESMTPS id t818ie51087122 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 1 Sep 2015 11:44:40 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.15.2/8.15.2/Submit) id t818ieb1087121; Tue, 1 Sep 2015 11:44:40 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 1 Sep 2015 11:44:40 +0300 From: Gleb Smirnoff To: Adrian Chadd Cc: "Ranjan1018 ." <214748mv@gmail.com>, FreeBSD CURRENT Subject: Re: Upgrading to r297291 LAGG(4) stops working. Message-ID: <20150901084440.GJ56997@glebius.int.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 08:44:45 -0000 On Mon, Aug 31, 2015 at 09:58:45AM -0700, Adrian Chadd wrote: A> Hi, A> A> +glebius, as he recently messed around with the wifi stack and his A> changes may have broken how mac addresses are assigned to the A> hardware. I've tested that with new code setting MAC address on wlan0 passed it down to device driver (iwn in my case). As Adrian already noted to Ranjan, his setup worked only by accident :) If it were not ath(4), but some more dumb WiFi device, the setup wouldn't work. -- Totus tuus, Glebius.