From owner-freebsd-net@FreeBSD.ORG Wed Jan 19 21:02:06 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 CA65C16A4CE for ; Wed, 19 Jan 2005 21:02:06 +0000 (GMT) Received: from mailhost.schluting.com (schluting.com [131.252.214.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2D3843D2F for ; Wed, 19 Jan 2005 21:02:06 +0000 (GMT) (envelope-from charlie@schluting.com) Received: from localhost (localhost [127.0.0.1]) by mailhost.schluting.com (Postfix) with ESMTP id 46BA62581 for ; Wed, 19 Jan 2005 13:02:06 -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 94221-03 for ; Wed, 19 Jan 2005 13:01:53 -0800 (PST) Received: from [131.252.209.122] (smelly.cat.pdx.edu [131.252.209.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhost.schluting.com (Postfix) with ESMTP id E7B8B22AC for ; Wed, 19 Jan 2005 13:01:52 -0800 (PST) Message-ID: <41EECAC0.3000801@schluting.com> Date: Wed, 19 Jan 2005 13:01:52 -0800 From: Charlie Schluting User-Agent: Mozilla Thunderbird 1.0 (X11/20041215) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by your mom at schluting.com Subject: 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, 19 Jan 2005 21:02:06 -0000 Did something change from 5.2.1 to 5.3? In 5.2.1 I used to have a config where the parent device, em(4), didn't have an IP, and the vlan dev had the IP address. (yes, the parent device was "UP") I then configured the trunk (on the switch) to have a native vlan of something other than the vlan interface's vlan. This worked. 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? Thanks :) -Charlie