From owner-freebsd-net@freebsd.org Fri Aug 4 10:45:48 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60080DD28ED for ; Fri, 4 Aug 2017 10:45:48 +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 mx1.freebsd.org (Postfix) with ESMTPS id 445003D45 for ; Fri, 4 Aug 2017 10:45:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v74AjmxO097958 for ; Fri, 4 Aug 2017 10:45:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221146] [LAGG] Problem with second laggport Date: Fri, 04 Aug 2017 10:45:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: konrad.kreciwilk@korbank.pl X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Aug 2017 10:45:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 --- Comment #9 from Konrad --- I set LAGG on igb0 and igb1 and seems to be ok: lagg0: flags=3D8843 metric 0 mtu 15= 00 =20=20=20=20=20=20=20 options=3D6403bb ether 00:1e:67:27:1d:5e inet 192.168.202.254 netmask 0xffffff00 broadcast 192.168.202.255=20 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg=20 laggproto lacp lagghash l2,l3,l4 laggport: igb0 flags=3D1c laggport: igb1 flags=3D1c lagg1: flags=3D8843 metric 0 mtu 15= 00 =20=20=20=20=20=20=20 options=3De400bb ether 0c:c4:7a:bd:65:58 inet 192.168.202.254 netmask 0xffffff00 broadcast 192.168.202.255=20 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg=20 laggproto lacp lagghash l2,l3,l4 laggport: ix0 flags=3D1c laggport: ix1 flags=3D1c but when ix's ports are configured as lagg1, all laggports work properly. W= hen I switch ix's ports as lagg0 and first in cloned_interfaces the problem appears: lagg0: flags=3D8843 metric 0 mtu 15= 00 =20=20=20=20=20=20=20 options=3De400bb ether 0c:c4:7a:bd:65:58 inet 192.168.202.254 netmask 0xffffff00 broadcast 192.168.202.255=20 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg=20 laggproto lacp lagghash l2,l3,l4 laggport: ix0 flags=3D1c laggport: ix1 flags=3D0<> lagg1: flags=3D8843 metric 0 mtu 15= 00 =20=20=20=20=20=20=20 options=3D6403bb ether 00:1e:67:27:1d:5e inet 192.168.202.254 netmask 0xffffff00 broadcast 192.168.202.255=20 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg=20 laggproto lacp lagghash l2,l3,l4 laggport: igb0 flags=3D1c laggport: igb1 flags=3D1c --=20 You are receiving this mail because: You are the assignee for the bug.=