From owner-freebsd-amd64@freebsd.org Fri Mar 4 13:04:00 2016 Return-Path: Delivered-To: freebsd-amd64@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 C1D549DB1A7 for ; Fri, 4 Mar 2016 13:04:00 +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 B1B837AE for ; Fri, 4 Mar 2016 13:04:00 +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 u24D40eb032210 for ; Fri, 4 Mar 2016 13:04:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 207701] vlan interface over failover lagg has empty/00:00:00:00:00:00 mac/ether address Date: Fri, 04 Mar 2016 13:04:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: freebsd-bugs@virtualtec.ch X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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 cc attachments.created 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-Mailman-Approved-At: Fri, 04 Mar 2016 13:08:23 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2016 13:04:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207701 Bug ID: 207701 Summary: vlan interface over failover lagg has empty/00:00:00:00:00:00 mac/ether address Product: Base System Version: 10.3-BETA2 Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: freebsd-bugs@virtualtec.ch CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 167713 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D167713&action= =3Dedit comparison between 10.2-release and 10.3-prerelease dmesg We configure some servers with two interfaces as follows: - failover lagg0 on em0 and em1 - several vlans on lagg0 after upgrading our systems due to the openssl bug, they came up without networking. The reason was the vlan interfaces on the lagg got configured with empty mac addresses: vlan10: flags=3D8843 metric 0 mtu 1= 496 ether 00:00:00:00:00:00 inet 10.0.1.11 netmask 0xffffff00 broadcast 10.0.1.255=20 nd6 options=3D29 media: Ethernet autoselect status: active vlan: 10 parent interface: lagg0 where as with RELEASE-10.2, this looked as follows: vlan10: flags=3D8843 metric 0 mtu 1= 496 ether 00:30:48:7f:29:74 inet 10.0.1.11 netmask 0xffffff00 broadcast 10.0.1.255=20 nd6 options=3D29 media: Ethernet autoselect status: active vlan: 10 parent interface: lagg0 The lagg0 looks the same in both releases: lagg0: flags=3D8843 metric 0 mtu 15= 00 =20=20=20=20=20=20=20 options=3D4219b ether 00:30:48:7f:29:74 nd6 options=3D29 media: Ethernet autoselect status: active laggproto failover lagghash l2,l3,l4 laggport: em0 flags=3D5 laggport: em1 flags=3D0<> We're normally using a stripped own kernel config, but for this purpose I deliberately booted with 10.2-RELEASE and created a 10.3-PRERELEASE@r2963= 82 GENERIC kernel to have a verifiable configuration. Our rc.conf snippet to configure the interfaces looks as follows (there are more vlans configured than this): cloned_interfaces=3D"vlan10 lagg0" ifconfig_em0=3D"vlanhwtag up" ifconfig_em1=3D"vlanhwtag up" ifconfig_lagg0=3D"laggproto failover laggport em0 laggport em1 up" ifconfig_vlan10=3D"inet 10.0.1.11/24 vlan 10 vlandev lagg0 up" --=20 You are receiving this mail because: You are on the CC list for the bug.=