Date: Mon, 28 May 2012 17:14:22 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Eygene Ryabinkin <rea@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r236178 - in head: sbin/ifconfig sys/net Message-ID: <20120528131422.GH92865@FreeBSD.org> In-Reply-To: <201205281213.q4SCD5PO010671@svn.freebsd.org> References: <201205281213.q4SCD5PO010671@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 28, 2012 at 12:13:05PM +0000, Eygene Ryabinkin wrote: E> The real-world case is when I am bundling together my Ethernet and E> WiFi interfaces and using multiple profiles for accessing network in E> different places: system being booted up with one profile, but later E> this profile being exchanged to another one, followed by 'service E> netif restart' will not add WiFi interface back to the lagg: the E> "stop" action from 'service netif restart' will shut down my main WiFi E> interface, so wlan0 that exists in the lagg0 will be destroyed and E> purged from lagg0; the "start" action will try to re-add both E> interfaces, but since Ethernet one is already in lagg0, ifconfig will E> refuse to add the wlan0 from WiFi interface. Although the lagg(4) change is definetely a needed fix, the way of network roaming via stacking WiFi and Ethernet into lagg(4) always looked like a huge crutch to me. Isn't the problem solvable via a some kind of smarter dhclient? How other UNIX-like OS-es solve this? -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120528131422.GH92865>