From owner-freebsd-stable@freebsd.org  Sun Apr 10 17:54:35 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 A13D3B0BE02
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun, 10 Apr 2016 17:54:35 +0000 (UTC)
 (envelope-from cmt@burggraben.net)
Received: from smtp.burggraben.net (smtp.burggraben.net
 [IPv6:2a01:4f8:140:50a2::3:1])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "ns.exwg.net", Issuer "Christoph Moench-Tegeder" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 68DBB1063
 for <freebsd-stable@freebsd.org>; Sun, 10 Apr 2016 17:54:35 +0000 (UTC)
 (envelope-from cmt@burggraben.net)
Received: from localhost (localhost [127.0.0.1])
 by smtp.burggraben.net (Postfix) with ESMTP id DE8B06002EE
 for <freebsd-stable@freebsd.org>; Sun, 10 Apr 2016 19:54:33 +0200 (CEST)
X-Spam-Scanned: by amavisd-new at exwg.net
Received: from smtp.burggraben.net ([127.0.0.1])
 by localhost (ns.burggraben.net [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id npJu95Tq6QNt for <freebsd-stable@freebsd.org>;
 Sun, 10 Apr 2016 19:54:33 +0200 (CEST)
Received: from elch.exwg.net
 (dslb-088-066-015-071.088.066.pools.vodafone-ip.de [88.66.15.71])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "elch.exwg.net", Issuer "Christoph Moench-Tegeder" (verified OK))
 by smtp.burggraben.net (Postfix) with ESMTPS
 for <freebsd-stable@freebsd.org>; Sun, 10 Apr 2016 19:54:33 +0200 (CEST)
Received: by elch.exwg.net (Postfix, from userid 1000)
 id 4CF0D301F2; Sun, 10 Apr 2016 19:54:33 +0200 (CEST)
Date: Sun, 10 Apr 2016 19:54:33 +0200
From: Christoph Moench-Tegeder <cmt@burggraben.net>
To: freebsd-stable@freebsd.org
Subject: Re: VLAN problem on some em(4) cards
Message-ID: <20160410175432.GB1746@elch.exwg.net>
Mail-Followup-To: freebsd-stable@freebsd.org
References: <20160410174415.GA1746@elch.exwg.net>
 <CAFMmRNzyTw_cX3rp4kaOMGcGaPpAXZPYuJ_=19TcCUb3oSHEfQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAFMmRNzyTw_cX3rp4kaOMGcGaPpAXZPYuJ_=19TcCUb3oSHEfQ@mail.gmail.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Apr 2016 17:54:35 -0000

## Ryan Stone (rysto32@gmail.com):

> tcpdump on em0 will show the vlan-tagged packets if everything is working
> correctly.  The fact that they are not showing up is a sign that something
> is not working correctly (or that your tcpdump filter isn't account for the
> vlan tag)

They do on the 82579LM (working) interface, but not on the 82574L
(non-working) interface. As I was working in a test setup, I
just tcpdumped "everything" (tcpdump -nevi em0).

Regards,
Christoph

-- 
Spare Space