From owner-freebsd-current@freebsd.org Thu May 30 16:37:53 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DF8E15C6E33 for ; Thu, 30 May 2019 16:37:53 +0000 (UTC) (envelope-from gcr+freebsd-current@tharned.org) Received: from roadkill.tharned.org (tunnel294749-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:107f::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "tharned.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A9AE93531; Thu, 30 May 2019 16:37:52 +0000 (UTC) (envelope-from gcr+freebsd-current@tharned.org) Received: from flake.tharned.org ([IPv6:2001:470:1f11:107f:fc23:b4f4:b79d:a329]) (authenticated bits=0) by roadkill.tharned.org (8.15.2/8.15.2) with ESMTPSA id x4UGboMl091297 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 30 May 2019 11:37:51 -0500 (CDT) (envelope-from gcr+freebsd-current@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tharned.org; s=2017; t=1559234271; bh=e6XlN0raQes/7Z3tKXtfESz1zw3jSyh7fDp1scOTzvs=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=HDX6DHP5Bjli551uB+H3Kb6KJth2RT5OReNXfQg2x/cTpaN4h3Jz7oj0JOF51rW6w rwd4ry7ecZ4tj486NwnWr+SZafIYxIfKqUE8/qYeAwPcjhC7XHIJOsM87qLK7tVmbp Kig2lF6rFH1q8tD87tpnwE62TVbpu+8dC71j/rnHjrfXqk7Qar8N1WmFY0n6RviidT rFAQ73K6cxRPKX6YRu6tEzTCMxcpVdpJyT4qxX4fYa4hJXhwRJl7owBF6yEpFGyodP qJlYkqSQOkSRYAmPrpZ2VOhqxDxuVuJSP8kO+Xc1ssMbdos05Sk4jX5dlqureN0CBq VrHZC5i6ZW6Pw== X-Authentication-Warning: roadkill.tharned.org: Host [IPv6:2001:470:1f11:107f:fc23:b4f4:b79d:a329] claimed to be flake.tharned.org From: Greg Rivers To: freebsd-current@freebsd.org Cc: Johannes Lundberg Subject: Re: Inconsistent behavior with wpa / devd / network interfaces Date: Thu, 30 May 2019 11:37:50 -0500 Message-ID: <2836877.0P3pStmDMi@no.place.like.home> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (roadkill.tharned.org [IPv6:2001:470:1f10:107f:0:0:0:2]); Thu, 30 May 2019 11:37:51 -0500 (CDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 16:37:53 -0000 On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: > Hi > > I have a bridge and an ethernet/wifi lagg failover like this: > > # First define all cloned interfaces > cloned_interfaces="bridge0 lagg0" > > # bhyve bridge > ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" > > # Ethernet/WiFi failvoer > ifconfig_em0="up" > wlans_iwm0="wlan0" > ifconfig_wlan0="WPA up" > create_args_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" > ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP up" > > When I move between home and work networks and plug in the network cable > it sometimes reconfigure and sometimes (mostly) not. Looking at devd > output from a failed occasion and I can see that it calls dhclient on > em0 and not lagg0. But it since it works sometimes I don't know if this > is correct or not (I would expect lagg0 and not em0 but manually running > this command with either em0 or lagg0 doesn't do anything)... > > devd log: Executing 'service dhclient quietstart $'em0'' > > In addition to this, I often have to run ifconfig wlan0 scan (or service > netif restart) or to have the it reconnect to a different wifi. It > doesn't seem to be doing any periodical scanning and reconnecting at all > (but maybe that's a different issue). > > For sometime now I usually have to run service netif restart to get > network working after switching location, followed by adding all my VM > tap interfaces to the bridge manually, and restarting bhyve guests > because they lose connectivity.. It's getting a bit tiring and I would > like to find a solution. > > Do I have something weird in my setup causing this? I don't recall ever > having this issue when not using failover lagg. Running recent 13-CURRENT. > I think there's a (unknown?) problem that makes lagg(4) incompatible with bridge(4). I've never been unable to make a lagg interface work as a member of a bridge. Lacking the time to pursue it, I've resorted to NATing instead. Also, wlan interfaces tend to break if you change their MAC address. So in a lagg consisting of a wlan interface and a ethernet interface (without a bridge), I always set the MAC of the ethernet to match the native MAC of the wlan, and not vice versa. -- Greg