From owner-freebsd-current@FreeBSD.ORG  Tue Jul 25 06:07:10 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2FAF616A4DE
	for <current@freebsd.org>; Tue, 25 Jul 2006 06:07:10 +0000 (UTC)
	(envelope-from ianf@hetzner.co.za)
Received: from hetzner.co.za (office.dc2.cpt.your-server.co.za [196.7.147.230])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B43EB43D46
	for <current@freebsd.org>; Tue, 25 Jul 2006 06:07:07 +0000 (GMT)
	(envelope-from ianf@hetzner.co.za)
Received: from localhost ([127.0.0.1] helo=ian.hetzner.africa)
	by hetzner.co.za with esmtp (Exim 4.62 (FreeBSD))
	(envelope-from <ianf@hetzner.co.za>) id 1G5G4O-000FRX-6O
	for current@freebsd.org; Tue, 25 Jul 2006 08:07:04 +0200
To: current@freebsd.org
From: Ian FREISLICH <if@hetzner.co.za>
X-Attribution: BOFH
Date: Tue, 25 Jul 2006 08:07:04 +0200
Sender: ianf@hetzner.co.za
Message-Id: <E1G5G4O-000FRX-6O@hetzner.co.za>
Cc: 
Subject: em promiscuous mode bug?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2006 06:07:10 -0000

Hi

It seems that placing an em(4) interface into promiscuous mode the
card stops doing hardware offload of 802.1Q tagging, in fact, it
stops tagging entirely if vlanhwtag is enabled on the card.

With vlanhwtag:
15:40:48.050645 00:00:5e:00:01:02 > 01:00:5e:00:00:12, ethertype IPv4 (0x0800), length 70: (tos 0x10, ttl 255, id 44821, offset 0, flags [DF], proto: VRRP (112), length: 56) 196.30.82.61 > 224.0.0.18: VRRPv2, Advertisement, vrid 2, prio 10, authtype none, intvl 1s, length 36, addrs(7): 157.248.206.115,76.246.42.167,148.235.231.80,70.180.123.113,201.169.28.232,19.31.18.203,59.148.50.175

Without vlanhwtag:
15:40:57.419522 00:00:5e:00:01:02 > 01:00:5e:00:00:12, ethertype 802.1Q (0x8100), length 74: vlan 1001, p 0, ethertype IPv4, (tos 0x10, ttl 255, id 44867, offset 0, flags [DF], proto: VRRP (112), length: 56) 196.30.82.61 > 224.0.0.18: VRRPv2, Advertisement, vrid 2, prio 10, authtype none, intvl 1s, length 36, addrs(7): 157.248.206.115,76.246.42.176,8.148.142.115,171.178.137.11,211.216.40.239,67.124.122.122,253.155.32.152

The interface is placed in promiscuous mode by the carp driver.

em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        options=cb<RXCSUM,TXCSUM,VLAN_MTU,POLLING,VLAN_HWCSUM>
        ether 00:04:23:cf:50:00
        media: Ethernet autoselect (1000baseTX <full-duplex>)
        status: active

vlan1001: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        inet 196.30.82.62 netmask 0xfffffff0 broadcast 196.30.82.63
        ether 00:04:23:cf:50:00
        media: Ethernet autoselect (1000baseTX <full-duplex>)
        status: active
        vlan: 1001 parent interface: em0

carp1001: flags=49<UP,LOOPBACK,RUNNING> mtu 1500
        inet 196.30.82.60 netmask 0xfffffff0 
        carp: BACKUP vhid 2 advbase 1 advskew 0

I've also noticed that the re(4) driver on the 8169 chip miss-tags
frames when vlanhwtag is enabled.

Ian

--
Ian Freislich