From owner-freebsd-bugs@FreeBSD.ORG Tue Dec 15 17:50:03 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BA35106568D for ; Tue, 15 Dec 2009 17:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1E4558FC27 for ; Tue, 15 Dec 2009 17:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBFHo2wC097536 for ; Tue, 15 Dec 2009 17:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBFHo2tF097535; Tue, 15 Dec 2009 17:50:02 GMT (envelope-from gnats) Resent-Date: Tue, 15 Dec 2009 17:50:02 GMT Resent-Message-Id: <200912151750.nBFHo2tF097535@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Jeff Blank Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3CEA106568D for ; Tue, 15 Dec 2009 17:49:03 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 7897C8FC21 for ; Tue, 15 Dec 2009 17:49:03 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nBFHn3t1099195 for ; Tue, 15 Dec 2009 17:49:03 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id nBFHn36D099194; Tue, 15 Dec 2009 17:49:03 GMT (envelope-from nobody) Message-Id: <200912151749.nBFHn36D099194@www.freebsd.org> Date: Tue, 15 Dec 2009 17:49:03 GMT From: Jeff Blank To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/141646: em(4) + lagg(4) + vlan(4) generates ISL-tagged frames instead of 802.1q-tagged frames X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 17:50:03 -0000 >Number: 141646 >Category: kern >Synopsis: em(4) + lagg(4) + vlan(4) generates ISL-tagged frames instead of 802.1q-tagged frames >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 15 17:50:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Jeff Blank >Release: 8.0-RELEASE >Organization: >Environment: FreeBSD asterisk01.tc.mtu.edu 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Mon Dec 14 11:14:35 EST 2009 root@asterisk01.tc.mtu.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Using this em(4) chipset: em0@pci0:5:0:0: class=0x020000 card=0x135e8086 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'HP NC360T PCIe DP Gigabit Server Adapter (n1e5132)' class = network subclass = ethernet em1@pci0:5:0:1: class=0x020000 card=0x135e8086 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'HP NC360T PCIe DP Gigabit Server Adapter (n1e5132)' class = network subclass = ethernet I configured a lagg interface (lagg0) in failover mode between the two em interfaces and then created two vlan interfaces with "vlandev lagg0" (vlan20, vlan96). Under 7.1-RELEASE on this host, there were no issues. Upon upgrading to 8.0-RELEASE, the host became unable to communicate through either vlan interface. I inspected the traffic generated by the host, and the ethernet frames transmitted were decoded by wireshark as containing ISL tags (??) rather than 802.1q VLAN tags. The host is still able to receive and correctly process q-tagged frames; only outbound frames are problematic. This issue does not occur when the vlan interfaces' vlandevs are em0 or em1. If I assign an IP address to lagg0 when the switch port is expecting and transmitting untagged frames, there are likewise no issues. This issue does not occur with the same host's bce(4) interfaces (substitute bce0/1 for em0/1 in how-to-repeat). >How-To-Repeat: Boot a system containing two em(4) interfaces (may need to be the above chipset) with no network configuration in rc.conf and execute the following commands as root: # ifconfig em0 up # ifconfig em1 up # ifconfig lagg0 create laggproto failover laggport em0 laggport em1 up # ifconfig vlan20 create vlan 20 vlandev lagg0 # ifconfig vlan20 / up Generate traffic on the configured IP network (e. g., ping), examine the traffic transmitted, and verify that ISL tags instead of 802.1q VLAN tags are present on the frames. >Fix: >Release-Note: >Audit-Trail: >Unformatted: