From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 19:55:49 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF7031065676 for ; Wed, 12 Mar 2008 19:55:49 +0000 (UTC) (envelope-from sean@chittenden.org) Received: from davie.textdrive.com (davie.textdrive.com [207.7.108.101]) by mx1.freebsd.org (Postfix) with ESMTP id A32858FC1F for ; Wed, 12 Mar 2008 19:55:49 +0000 (UTC) (envelope-from sean@chittenden.org) Received: from [192.168.255.187] (60.ten-net.org [71.6.14.60]) by davie.textdrive.com (Postfix) with ESMTP id 6D57ACA2D8; Wed, 12 Mar 2008 19:38:13 +0000 (GMT) Message-Id: From: Sean Chittenden To: Giulio Ferro In-Reply-To: <47D7C34E.8060805@zirakzigil.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 12 Mar 2008 12:38:06 -0700 References: <47D7C34E.8060805@zirakzigil.org> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Mar 2008 19:55:49 -0000 > interface ethernet 1/g1 > switchport mode trunk > switchport trunk allowed vlan add 10 > exit I think this is an issue with default VLAN membership. I have this config running on *hundreds* of servers without issue. Since Dell should be a cisco rip-off, on your switchport config, throw in (haven't tested this, on dell's CLI): switchport trunk encapsulation dot1q then change your ifconfig foo to: cloned_interfaces="vlan10 vlan11" ifconfig_re0="media 100baseTX mediaopt full-duplex" ifconfig_vlan10="vlan 10 vlandev re0" ifconfig_vlan10_alias0="inet 192.168.60.1 netmask 255.255.255.0" ifconfig_vlan11="vlan 11 valndev re0" ifconfig_vlan11_alias0="inet 192.168.100.1 netmask 255.255.255.0" FWIW, I think you'll find fewer gray hairs if you stick to the convention of using a vlan device that has the same VLAN tag. You may be able to have a default VLAN, but I consider it poor practice to rely on default VLAN membership. There are good reasons to have a default VLAN configured, but this doesn't sound like one of those cases. Stick with explicit VLAN tagging on your servers and you can't go wrong. -sc -- Sean Chittenden sean@chittenden.org http://sean.chittenden.org/