From owner-freebsd-bugs@FreeBSD.ORG Wed Mar 2 02:04:44 2011 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C915106566B for ; Wed, 2 Mar 2011 02:04:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id B51908FC13 for ; Wed, 2 Mar 2011 02:04:43 +0000 (UTC) Received: by gyh4 with SMTP id 4so2533539gyh.13 for ; Tue, 01 Mar 2011 18:04:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=8ISYXv+nsFc4q4zw22UnYmpy2JActwmeAkFon0to9Nk=; b=bLA2Z4yQrtuoBJEXvycM/bxAlUENX9XuP34OaZ5OegXpugiXnTIr15IEoz2PtLfEoH 25WWk+LD0Egqlza3ie/zZpxz44R1XAjEn38gbMqbBuhJMLoGKI0+aRmtVB2gCu3fjMRX VrBD6Swt3+ThfUv5IvYBOCs6n2HDViT5cbrLE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=LTexya9VYHMMgxYchdC3bzzT7dAFGtRGU1QnYp9yCNEfnmXqJhOjOTXN5YaX+2AYe/ ilxmdiK8YlGrVgs6BGyG58pSv+vTRbYTd8iV0UfdAaT8mCte3IgnTvHcROUP3FWmipkO 1dIHzDz3fwGm6UYVpioP91+qLlV16D0rbGJZM= Received: by 10.90.7.9 with SMTP id 9mr10242325agg.109.1299029827666; Tue, 01 Mar 2011 17:37:07 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id c7sm2577438ana.17.2011.03.01.17.37.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 17:37:06 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 01 Mar 2011 17:37:07 -0800 From: YongHyeon PYUN Date: Tue, 1 Mar 2011 17:37:07 -0800 To: Andrei Manescu - Ivorde Message-ID: <20110302013707.GC7076@michelle.cdnetworks.com> References: <201103011819.p21IJ5Bu039230@freefall.freebsd.org> <4D6D7317.7070300@ivorde.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D6D7317.7070300@ivorde.ro> User-Agent: Mutt/1.4.2.3i Cc: freebsd-bugs@freebsd.org, andrei@ivorde.ro, yongari@freebsd.org Subject: Re: misc/155134: Vlan hwtagging on fxp under 7.4-PRERELEASE doesn't work X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 02:04:44 -0000 On Tue, Mar 01, 2011 at 11:28:39PM +0100, Andrei Manescu - Ivorde wrote: > Hi, > > Thanks for replying. > > When vlanhwtag is enabled on the fxp physical interface, the packets are > not vlan tagged and, sometimes, not replied: > > [root@thor ~]# ifconfig fe-0/0 > fe-0/0: flags=8843 metric 0 mtu 1500 > options=211b > > [root@thor ~]# ifconfig vlan10 > vlan10: flags=8843 metric 0 mtu 1500 > ether 00:02:b3:9f:ef:86 > inet 192.168.3.2 netmask 0xffffff00 broadcast 192.168.3.255 > media: Ethernet autoselect (100baseTX ) > status: active > vlan: 10 parent interface: fe-0/0 > > Consecutive commands: > [root@thor ~]# ping -c 1 192.168.3.1 --> NO REPLY > PING 192.168.3.1 (192.168.3.1): 56 data bytes > > --- 192.168.3.1 ping statistics --- > 1 packets transmitted, 0 packets received, 100.0% packet loss > [root@thor ~]# ping -c 1 192.168.3.1 --> REPLY > PING 192.168.3.1 (192.168.3.1): 56 data bytes > 64 bytes from 192.168.3.1: icmp_seq=0 ttl=64 time=0.398 ms > > --- 192.168.3.1 ping statistics --- > 1 packets transmitted, 1 packets received, 0.0% packet loss > round-trip min/avg/max/stddev = 0.398/0.398/0.398/0.000 ms > > tcpdump of the above echo requests. Only the reply is tagged: > [root@thor ~]# tcpdump -nni fe-0/0 -e > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on fe-0/0, link-type EN10MB (Ethernet), capture size 96 bytes > 23:10:28.667909 00:02:b3:9f:ef:86 > 00:02:a5:8f:56:69, ethertype IPv4 > (0x0800), length 98: 192.168.3.2 > 192.168.3.1: ICMP echo request, id > 17620, seq 0, length 64 > 23:10:44.196339 00:02:b3:9f:ef:86 > 00:02:a5:8f:56:69, ethertype IPv4 > (0x0800), length 98: 192.168.3.2 > 192.168.3.1: ICMP echo request, id > 24788, seq 0, length 64 > 23:10:44.196616 00:02:a5:8f:56:69 > 00:02:b3:9f:ef:86, ethertype 802.1Q > (0x8100), length 102: vlan 10, p 0, ethertype IPv4, 192.168.3.1 > > 192.168.3.2: ICMP echo reply, id 24788, seq 0, length 64 > > The tcpdump clearly shows that for the first two packets (echo > requests), the ethertype is 0x0800 and it doesn't contain the vlan tag. > > Now, if I disable the vlanhwtag on the physical interface, all gets back > to normal. > > The physical interface is a supported 82550 chip. > > [root@thor ~]# grep fe-0/0 /etc/rc.conf > ifconfig_fxp0_name="fe-0/0" > [root@thor ~]# pciconf -lv > fxp0@pci0:1:1:0: class=0x020000 card=0x10408086 chip=0x12298086 > rev=0x0c hdr=0x00 > vendor = 'Intel Corporation' > device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' > class = network > subclass = ethernet > Your controller is i82550 Pro/100 Ethernet and it is known to support TSO/VLAN hardware tagging as well as IPSec acceleration. > Am I really off topic ? > No, but looks strange to me. Could you capture both boxes(one for sender(fxp0) and receiver to see whether the packets really have no VLAN header.)? > P.S.: I also attached a capture with one echo request and an echo reply. > The req leaving the FreeBSD box in question is not encapsulated, but the > reply is coming in (with the vlan tag). I think the capture is incomplete since it only has sender side. I need capture both sender and receiver. > P.S.S.: At the other end, there is a pFsense 2.0-RC1 (FreeBSD 8.1) > firewall with vlans configured on an fxp0 interface also. > Don't know about pfSense but you can disable VLAN hardware tagging on pfSense side to rule out possible VLAN hardware related issues before capturing VLAN traffic. Make sure to capture parent interface traffic instead of vlan interface. > > Thanks, > Andrei. >