From owner-freebsd-current@freebsd.org Sun Sep 6 15:05:50 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 37D409CBB11 for ; Sun, 6 Sep 2015 15:05:50 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.netplex.net", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E94FDDA1; Sun, 6 Sep 2015 15:05:49 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.15.1/8.15.1/NETPLEX) with ESMTP id t86F5f5M020436; Sun, 6 Sep 2015 11:05:41 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]); Sun, 06 Sep 2015 11:05:41 -0400 (EDT) Date: Sun, 6 Sep 2015 11:05:41 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net Reply-To: Daniel Eischen To: Gleb Smirnoff cc: Sergey Kandaurov , John Baldwin , FreeBSD Current , Adrian Chadd , "Ranjan1018 ." <214748mv@gmail.com> Subject: Re: Upgrading to r297291 LAGG(4) stops working. In-Reply-To: Message-ID: References: <4074787.MD5UFHZJLz@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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: Sun, 06 Sep 2015 15:05:50 -0000 Please add an entry to src/UPDATING to explain the change needed. Also, my question remains, if wlan now knows how to set the MAC address, do we still need to set the MAC address manually and can we go back to using lagg just like it was 2 non-wireless connections (in the case that the underlying wireless device _can_ change the MAC address). In the case that the underlying wireless device cannot change the MAC address, then the examples should change the MAC address of the wired device to match that of the wireless instead of the other way around (or recommend doing it this way all the time). On Fri, 4 Sep 2015, Daniel Eischen wrote: > On Fri, 4 Sep 2015, Sergey Kandaurov wrote: > >> On 1 September 2015 at 04:47, John Baldwin wrote: >>> On Monday, August 31, 2015 09:58:45 AM Adrian Chadd wrote: >>>> Hi, >>>> >>>> +glebius, as he recently messed around with the wifi stack and his >>>> changes may have broken how mac addresses are assigned to the >>>> hardware. >>> >>> Glebius did break this, though not because of what you say. It's broken >>> because the 'ifconfig_ath0' line that sets the mac address no longer >>> does anything because 'ath0' is no longer an interface (and so that >>> line is now ignored, plus it wouldn't work if it were passed to ifconfig >>> now anyway). >>> >>> At the very least the Handbook section on this needs to be updated to give >>> working instructions for both HEAD and stable branches. >> >> What about this change? > > [ ... ] > >> ifconfig_bge0="up" >> -ifconfig_iwn0="ether >> 00:21:70:da:ae:37" >> wlans_iwn0="wlan0" >> ifconfig_wlan0="WPA" >> +ifconfig_wlan0_alias0="ether 00:21:70:da:ae:3" >> cloned_interfaces="lagg0" >> ifconfig_lagg0="laggproto >> failover laggport bge0 laggport wlan0 DHCP" >> > > Is this in human readable form anywhere? Seems like it's missing > something (the ifconfig_iwn0="up"?). > > So to go from this: > > ifconfig_iwn0="ether 00:11:22:33:44:55" > wlans_iwn0=wlan0 > ifconfig_wlan0="ssid MYSSID WPA" > ifconfig_re0="up" > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0" > ifconfig_lagg0_alias0="inet 10.0.0.7 netmask 0xffffff00" > > It would now be: > > ifconfig_iwn0="up" > wlans_iwn0=wlan0 > ifconfig_wlan0="ssid MYSSID WPA" > ifconfig_wlan0_alias0="ether 00:11:22:33:44:55" > ifconfig_re0="up" > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0" > ifconfig_lagg0_alias0="inet 10.0.0.7 netmask 0xffffff00" > > Is that correct? > > Do we even need the ifconfig_wlan0_alias0 to set the MAC address? > If wlan0 (the cloned device under lagg0) knows how to set the MAC > address, then shouldn't lagg be able to tell wlan0 to set the MAC > address? The problem before was that wlan didn't know how to > set the MAC address, so it was ignored when lagg tried to set it. -- DE