From owner-freebsd-bugs@freebsd.org Thu Nov 7 17:40:51 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4CDF71BADAE for ; Thu, 7 Nov 2019 17:40:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4789fq1NyQz41Vj for ; Thu, 7 Nov 2019 17:40:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 2DD721BADAD; Thu, 7 Nov 2019 17:40:51 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2D8E41BADAC for ; Thu, 7 Nov 2019 17:40:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::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.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4789fq0VtGz41Vh for ; Thu, 7 Nov 2019 17:40:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E8EFE19503 for ; Thu, 7 Nov 2019 17:40:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xA7Heotv013213 for ; Thu, 7 Nov 2019 17:40:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xA7Heo2I013212 for bugs@FreeBSD.org; Thu, 7 Nov 2019 17:40:50 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 241785] [vlan][lagg] creating vlan over lagg causes flapping Date: Thu, 07 Nov 2019 17:40:50 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: konrad.kreciwilk@korbank.pl 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: Thu, 07 Nov 2019 17:40:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241785 Bug ID: 241785 Summary: [vlan][lagg] creating vlan over lagg causes flapping Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: konrad.kreciwilk@korbank.pl Hello, Starting of 12-STABLE (I do not know revision numer) up to 12.1-RELEASE I notice a problem with vlans over laggport. I have INTEL 82599 (ix0, ix1) and create a lagg(LACP): root@:~ # ifconfig lagg0 create root@:~ # ifconfig lagg0 laggproto lacp laggport ix0 laggport ix1 and vlans: root@:~ # ifconfig vlan3960 create root@:~ # ifconfig vlan3960 vlan 3960 vlandev lagg0 ifconfig output: ix0: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3De53fbb ether a0:36:9f:1d:db:4c media: Ethernet autoselect (10Gbase-Twinax ) status: active nd6 options=3D29 ix1: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3De53fbb ether a0:36:9f:1d:db:4c hwaddr a0:36:9f:1d:db:4e media: Ethernet autoselect (10Gbase-Twinax ) status: active nd6 options=3D29 lo0: flags=3D8049 metric 0 mtu 16384 options=3D680003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=3D21 lagg0: flags=3D8843 metric 0 mtu 15= 00 options=3De53fbb ether a0:36:9f:1d:db:4c laggproto lacp lagghash l2,l3,l4 laggport: ix0 flags=3D1c laggport: ix1 flags=3D1c groups: lagg media: Ethernet autoselect status: active nd6 options=3D29 vlan3960: flags=3D8843 metric 0 mtu= 1500 options=3D600703 ether a0:36:9f:1d:db:4c inet 212.127.xx.xx netmask 0xfffffffc broadcast 212.127.92.255 groups: vlan vlan: 3960 vlanpcp: 0 parent interface: lagg0 media: Ethernet autoselect status: active nd6 options=3D29 next, creating new vlan causes a port flapping (ix0,ix1 and whole lagg0): root@:~ # ifconfig vlan100 create root@:~ # ifconfig vlan100 vlan 100 vlandev lagg0 root@:~ # ifconfig vlan200 create root@:~ # ifconfig vlan200 vlan 200 vlandev lagg0 dmesg output: vlan3960: link state changed to UP ix0: link state changed to DOWN ix1: link state changed to DOWN lagg0: link state changed to DOWN vlan3960: link state changed to DOWN vlan100: link state changed to DOWN ix0: link state changed to UP ix1: link state changed to UP lagg0: link state changed to UP vlan3960: link state changed to UP vlan100: link state changed to UP ix0: link state changed to DOWN ix1: link state changed to DOWN lagg0: link state changed to DOWN vlan3960: link state changed to DOWN vlan100: link state changed to DOWN vlan200: link state changed to DOWN ix0: link state changed to UP ix1: link state changed to UP lagg0: link state changed to UP vlan3960: link state changed to UP vlan100: link state changed to UP vlan200: link state changed to UP Its happend for example on 12.0-STABLE #0 r344658M, 12.1-RELEASE. I use a diffrent hardware, only networkcard (based on INTEL 82599 chipset) is the s= ame. --=20 You are receiving this mail because: You are the assignee for the bug.=