From owner-freebsd-bugs@freebsd.org Mon Apr 29 20:38:22 2019 Return-Path: Delivered-To: freebsd-bugs@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 C54D6159D373 for ; Mon, 29 Apr 2019 20:38:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5AE3373536 for ; Mon, 29 Apr 2019 20:38:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1856E159D372; Mon, 29 Apr 2019 20:38:21 +0000 (UTC) Delivered-To: bugs@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 E88A2159D371 for ; Mon, 29 Apr 2019 20:38:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (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 "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62F9273533 for ; Mon, 29 Apr 2019 20:38:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7A66A1EC06 for ; Mon, 29 Apr 2019 20:38:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3TKcJFk014822 for ; Mon, 29 Apr 2019 20:38:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3TKcJXY014821 for bugs@FreeBSD.org; Mon, 29 Apr 2019 20:38:19 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 237660] Networking bridge config with vlan bug? Date: Mon, 29 Apr 2019 20:38:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: peo_s@incedo.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2019 20:38:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237660 Bug ID: 237660 Summary: Networking bridge config with vlan bug? Product: Base System Version: 12.0-RELEASE Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: peo_s@incedo.org Hi I have a firewall where I have named vlan interfaces and the IP:s directly = on the vlan interfaces. All good there... Now... To use bhyve with vlans in bridge setups I think I have found a bug (This is just a lab as I usually use SR-IOV...) Now I have struggled a bit, but now know what is wrong.... This is FreeBSD 12.0p3 relese #### This is my switch port.=20 interface 1/g8 description 'MISC TRUNK - LABORATION' switchport mode trunk switchport trunk native vlan 2008 switchport trunk allowed vlan 2-4,21,899,2008 vlan participation exclude 1,999 exit Setting an IP directly on the vlan interface and it works OK Setting an IP directly on a bridge not connected to a vlan and it works OK = (but of course the switch port must be reconfigured for that first to an access port) But... if I try to set the IP on the bridge that has a named vlan interface attached, it simply did not work to communicate. I have used this vlan config scheme below a-lot before, but not with bridge= s. It looks 100% ok with ifconfig. But it does not work. #### *NOT* WORKING #### ifconfig_re0=3D"up" cloned_interfaces=3D"bridge2 " vlans_re0=3D"vlan2" create_args_vlan2=3D"vlan 2" ifconfig_vlan2_descr=3D"Local LAN network interface (vlan 2)" ifconfig_bridge2_name=3D"LAN_BRIDGE" ifconfig_LAN_BRIDGE=3D"inet 192.168.0.35/24 addm vlan2 up" ifconfig_vlan2=3D"up" Now... I had to try something... :) so I rewrote the config in a different = way. This also looks ok with ifconfig. Bu THIS, THIS WORKS. #### WORKING #### ifconfig_re0=3D"up" cloned_interfaces=3D"bridge2" vlans_re0=3D"2" ifconfig_re0_2_descr=3D"Local LAN network interface (vlan 2)" ifconfig_bridge2=3D"inet 192.168.0.35/24 addm re0.2 up" ifconfig_re0_2=3D"up" I think there maybe is a bug. Otherwise, please enlighten me of my stupidit= y :) --=20 You are receiving this mail because: You are the assignee for the bug.=