From owner-freebsd-net@FreeBSD.ORG Wed Jan 26 17:37:52 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AA1916A4CE for ; Wed, 26 Jan 2005 17:37:52 +0000 (GMT) Received: from mailhost.schluting.com (schluting.com [131.252.214.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 053B643D4C for ; Wed, 26 Jan 2005 17:37:52 +0000 (GMT) (envelope-from charlie@schluting.com) Received: from localhost (localhost [127.0.0.1]) by mailhost.schluting.com (Postfix) with ESMTP id AE1252281 for ; Wed, 26 Jan 2005 09:37:51 -0800 (PST) Received: from mailhost.schluting.com ([127.0.0.1]) by localhost (schluting.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74959-06 for ; Wed, 26 Jan 2005 09:37:46 -0800 (PST) Received: from [131.252.213.83] (schrodinger.cat.pdx.edu [131.252.213.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhost.schluting.com (Postfix) with ESMTP id 5605E20F9 for ; Wed, 26 Jan 2005 09:37:46 -0800 (PST) Message-ID: <41F7D566.1030601@schluting.com> Date: Wed, 26 Jan 2005 09:37:42 -0800 From: Charlie Schluting User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-net@freebsd.org" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by your mom at schluting.com Subject: Re: vlans changed? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 17:37:52 -0000 On 1/20/2005 2:33 AM, Robert Watson wrote: > On Wed, 19 Jan 2005, Charlie Schluting wrote: >>Now, in 5.3, the only thing I can get working is to configure the em0 >>int with the IP, and set the trunk to have the native vlan corresponding >>to that IP. Weird. >> >>Also, is there a way to stop em(4) from stripping dot1q tags in >>hardware? I'd like to see them with tcpdump. What kind of a performance >>hit does this involve? > > > Try "ifconfig em0 -vlanhwtag" and see if that helps. If not, take a look > in if_em.c:em_setup_interface(), and you'll see two lines like this: Ok, I seem to have forgotten the nature of this bug, even though I had previously run into it. Heh. This is a different computer, and em0 (aside from vlans not working properly) "turns off" every once in a while too. It happened with the fxp driver on my other box. What a coincidence that I asked about disabling hw tagging :) So, I've disabled vlanhwtag with ifconfig. If it worked, the interface will stay up all day today. It normally doesn't last more than 4 hours on this box. By "up" I mean it will continue to work.. it doesn't really go down. I'll let you know. If this doesn't help, I'll try commenting out the stuff you mentioned in em_setup_interface(). -Charlie