From owner-freebsd-stable@freebsd.org Sun Apr 10 17:50:24 2016 Return-Path: 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 5C511B0BBFA for ; Sun, 10 Apr 2016 17:50:24 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 286E21CD2 for ; Sun, 10 Apr 2016 17:50:24 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id 2so183951384ioy.1 for ; Sun, 10 Apr 2016 10:50:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=1eqNwaNO9F5Z35uruXs4R4RJSMzOlvDH6KY3Sj/LiI8=; b=gszZncpN/afPAkpTDhGKg3v4cDYRVBQ+EHebmYqyvbyp0lJWLWKWWycuP02pxQI/G+ Bb+uVhXiQ0ZOJ599IhmJSNtpqa23rXxyW5O812tYR8Ne8IcCldm1PgQhCPtwZPm03wUB RUinBS4NqE38iJFoqJP2WsvMjBF5heL1+BgSQMfRnq3wMBQ4ZnB3EWTImqcPj49xm+Nl CckhWC0EsREUQbkQmOXaIUT3UMmYImOo1K57TlQNaBtZCCrmK+alNKFIxV6ySHtNX1Gr 0o4IulZEFTxN7zb8UB7iBl8T5GaZJgyiz3hIOoHMD7i/SjZCoWkmBZkj4CpS6bq8DKAG VEsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=1eqNwaNO9F5Z35uruXs4R4RJSMzOlvDH6KY3Sj/LiI8=; b=EkGffMOg7kVxpLp2iM0tdrrWGmrzZ170dfm2J5lK/ju+OMh9WOKLr1cFHJw1DVqznF 8bSTku8WykmMphcV7IcbNOx5e98ZRIFhChBgHWbu/SWn2kxqy0RQhoMwdoSrG1DeqR+r AyAk+2YoiMNrYDN/rMsy+a6tVY6OkoTcJ9fBAKjxEVc8R1AihY490LnoahMPJWTaV+HE mr16VHuu0pIvNksfCnhzBT5gdf2ekXpWiBmEhGnr4pQSDmsV+O8x6d3UiXa/oX10us3Y T1+iSoOeP7OXe/K63c/7tw0CZiKEclz7G93eSXbsb/lOjrdEf5NRdgKZ/A1ZMa01txKA DsYg== X-Gm-Message-State: AD7BkJL2szy64GZ0+aDkYMjdU9ZYNH/8N9JU3httjAsuW91hKnoL1j2AxjOiw1V7+MLsO8o8PMiR9yngJKI3Ew== MIME-Version: 1.0 X-Received: by 10.107.150.2 with SMTP id y2mr19981228iod.113.1460310623399; Sun, 10 Apr 2016 10:50:23 -0700 (PDT) Received: by 10.107.133.162 with HTTP; Sun, 10 Apr 2016 10:50:23 -0700 (PDT) In-Reply-To: <20160410174415.GA1746@elch.exwg.net> References: <20160410174415.GA1746@elch.exwg.net> Date: Sun, 10 Apr 2016 13:50:23 -0400 Message-ID: Subject: Re: VLAN problem on some em(4) cards From: Ryan Stone To: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2016 17:50:24 -0000 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) On Sun, Apr 10, 2016 at 1:44 PM, Christoph Moench-Tegeder < cmt@burggraben.net> wrote: > Hi, > while replacing a switch I ran into a problem with using 802.1q VLANs > (vlan(4)) on a em(4) card - that is, I could not get the card to work > with VLANs. > Details: > Software is FreeBSD 10.3-RELEASE i386 with a custom kernel (but has > em(4) and vlan(4) compiled in (not as a module)). > Hardware is a Soekris net6501-70, the interface in question is (pciconf) > em2@pci0:10:0:0: class=0x020000 card=0x00008086 chip=0x10d38086 > rev=0x00 > vendor = 'Intel Corporation' > device = '82574L Gigabit Network Connection' > class = network > subclass = ethernet > > The setup I wanted to create was a "router on a stick", that is having > 3 (for starters) tagged VLANs on that one link between router and > switch. I was not able to get any packet through to the switch, > while tcpdump shows the packets on the vlan interface (but not on > the underlying em interface - I understand that this could be the > result of hardware vlan processing). I could not ping any host beyond > the switch nor the switch's management interface itself, I did not > even receive ARP replies. > I tried both manual creation of the vlan devices and the rc.conf/ > netif mechanism - with the very same results ("doesn't work"). > Experimenting with the vlanhw* flags on the em interface did not > result in any change. > > To make sure it's not the switch (or my own mistake), I took another > host with an em interface - this time, it was a > em0@pci0:0:25:0: class=0x020000 card=0x21ce17aa chip=0x15028086 > rev=0x04 > vendor = 'Intel Corporation' > device = '82579LM Gigabit Network Connection' > class = network > subclass = ethernet > > (again 10.3-RELEASE, but amd64). > With this interface (connected to the very same switch port) I > had instantaneous success, so I guess the switch is ok and I'm > not totally mistaken in my doings. > > Could anybody give a hint on how to further debug this or a pointer > to further reading? > > Regards, > Christoph > > -- > Spare Space > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >