From owner-freebsd-current@freebsd.org Thu May 30 20:25:29 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 4EDE315A9CB5 for ; Thu, 30 May 2019 20:25:29 +0000 (UTC) (envelope-from SRS0=kAX8=T6=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3D506C4E6 for ; Thu, 30 May 2019 20:25:28 +0000 (UTC) (envelope-from SRS0=kAX8=T6=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8B58D28411; Thu, 30 May 2019 22:25:25 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 3B09A28422; Thu, 30 May 2019 22:25:23 +0200 (CEST) Subject: Re: Inconsistent behavior with wpa / devd / network interfaces To: Greg Rivers , freebsd-current@freebsd.org References: <2836877.0P3pStmDMi@no.place.like.home> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Thu, 30 May 2019 22:25:22 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <2836877.0P3pStmDMi@no.place.like.home> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: C3D506C4E6 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd-current]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.991,0] 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 20:25:29 -0000 Greg Rivers wrote on 2019/05/30 18:37: [...] >> 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. lagg and bridge can work together. I am running machine with FreeBSD 11.2 with 2 Intel NICs: em0 and em1 combined in to lagg0 lagg0 has 4 static IP addresses There is also bhyve VM on tap20, this VM has another 2 static IP addresses tap20 and lagg0 are members of the bridge. This bridge is renamed to "vm-public" vm-public: flags=8843 metric 0 mtu 1500 ether da:ae:ba:75:53:ce nd6 options=1 groups: bridge vm-switch viid-4c918@ id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap20 flags=143 ifmaxaddr 0 port 5 priority 128 path cost 2000000 member: lagg0 flags=143 ifmaxaddr 0 port 4 priority 128 path cost 2000000 Everything works without any problem. The only problem in the beginning was PF rules. I added rule to allow traffic to the VM IP addresses. Miroslav Lachman