From owner-freebsd-net@FreeBSD.ORG Thu Jul 31 12:33:45 2014 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 40FC0E67 for ; Thu, 31 Jul 2014 12:33:45 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id DCF2025F5 for ; Thu, 31 Jul 2014 12:33:44 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s6VCXHHv007608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Jul 2014 13:33:18 +0100 (BST) Date: Thu, 31 Jul 2014 13:33:18 +0100 From: Karl Pielorz To: Hrant Dadivanyan Subject: Re: FreeBSD 10.0-R connected to Cisco switch (in 'trunk' mode with native VLAN) - doesn't work? Message-ID: In-Reply-To: References: X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 12:33:45 -0000 --On 30 July 2014 13:26 +0400 Hrant Dadivanyan wrote: > Hi Karl, > > I'm not sure whether it's on by default, but many Cisco switches > (including all in 3750 family) can tag native vlan, so no a packet will > leave ports untagged. > no vlan dot1q tag native > in configuration mode will switch this off. Thanks to all that replied - the issue in the end was a switch config issue (as suspected - i.e. not an O/S issue). Something to do with QinQ being setup on it - and the switch then not de-tagging native trunk vlan's... I'm not setting up the switches - so I don't know for sure what config option was changed (i.e. the one above?), but it is resolved now. Thanks again, -Karl