From owner-freebsd-net@FreeBSD.ORG Tue Jul 29 16:36:55 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 2DA1FADE for ; Tue, 29 Jul 2014 16:36:55 +0000 (UTC) Received: from relay1-bcrtfl2.verio.net (relay1-bcrtfl2.verio.net [131.103.218.142]) by mx1.freebsd.org (Postfix) with ESMTP id D935C2612 for ; Tue, 29 Jul 2014 16:36:54 +0000 (UTC) Received: from iad-wprd-xchw02.corp.verio.net (iad-wprd-xchw02.corp.verio.net [198.87.7.165]) by relay1-bcrtfl2.verio.net (Postfix) with ESMTP id 6E09EB038040; Tue, 29 Jul 2014 12:09:42 -0400 (EDT) Received: from IAD-WPRD-XCHB01.corp.verio.net ([198.87.7.137]) by iad-wprd-xchw02.corp.verio.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 29 Jul 2014 12:09:41 -0400 Content-Class: urn:content-classes:message Subject: RE: FreeBSD 10.0-R connected to Cisco switch (in 'trunk' mode with native VLAN) - doesn't work? Importance: normal Priority: normal MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 29 Jul 2014 12:09:40 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4913 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD 10.0-R connected to Cisco switch (in 'trunk' mode with native VLAN) - doesn't work? thread-index: Ac+rLf4J9m9qfwnmQN2W0zA7o17t8gAGMvrw References: From: "David DeSimone" To: "Karl Pielorz" X-OriginalArrivalTime: 29 Jul 2014 16:09:41.0751 (UTC) FILETIME=[814F2870:01CFAB47] 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: Tue, 29 Jul 2014 16:36:55 -0000 We use exactly the sort of configuration you showed, and it works = perfectly with our FreeBSD systems. It is possible you are running afoul of spanning-tree behavior on the = port. Access ports are treated as "edge" ports and can activate right = away, while trunk ports must go through the full listen/learn/forward = cycle before they will start forwarding traffic, making the port appear = dead during its first 30-40 seconds. Consider adding to the 3750 configuration: interface GigabitEthernet_/0/__ spanning-tree portfast trunk The switch will give you a big warning about why this is a terrible = idea, but it is in fact a very good idea, since your server (hopefully) = isn't doing any bridging of traffic. If you do have any bridging code enabled, however, then this is actually = a terrible suggestion. :) -----Original Message----- From: owner-freebsd-net@freebsd.org = [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Karl Pielorz Sent: Tuesday, July 29, 2014 8:02 AM To: freebsd-net@FreeBSD.org Subject: FreeBSD 10.0-R connected to Cisco switch (in 'trunk' mode with = native VLAN) - doesn't work? Hi, I've got a Cisco 3750X switch a colleague is setting up. We've got this=20 configured - but it doesn't seem to talk nicely to our FBSD 10.0-R box,=20 looks like some kind of VLAN issue (but shouldn't be). Switch side - the port is configured with: switchport trunk encapsulation dot1q switchport trunk native vlan 2000 switchport trunk allowed vlan 2000,2200-2300 switchport mode trunk >From what I understand this tells the Cisco to present all the = 'allowed'=20 VLAN's to the port, and that untagged traffic traversing the port should = be=20 sent/received as VLAN 2000? So, we connect our BSD box and do: ifconfig bge0 inet 192.168.100.10 netmask 255.255.255.0 But we can't ping another host connected on the network, on = '192.168.100.1'. The above ifconfig uses no VLAN spec, but that should be covered by the=20 'trunk native vlan'? The only way we can fix this - is to take the system 'as-is' and change = the=20 Cisco port to: switchport mode access switchport access vlan 2000 This sets the port to be 1 VLAN only, and sets that VLAN to VLAN 2000 - = so=20 traffic traversing the port will be untagged, but carried as part of = VLAN=20 2000. I've been told in theory the bottom config should be the 'same' as the=20 previous one (i.e. untagged traffic is treated as VLAN 2000). But with the top config - the BSD box can't connect anywhere, with the=20 bottom config (with the BSD box setup the same) - it can. Presuming someone here has used Cisco kit with FreeBSD - can anyone see = why=20 the top config doesn't work? - The guy setting up the switches says he=20 always uses the top config - and hasn't had an issue with it, but this=20 obviously doesn't work with our FreeBSD boxes. I would say we'd try it with a different O/S but at the moment, all the = kit=20 on 'our' side is FreeBSD based... Cheers, -Karl _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" This email message is intended for the use of the person to whom it has = been sent, and may contain information that is confidential or legally = protected. If you are not the intended recipient or have received this = message in error, you are not authorized to copy, distribute, or = otherwise use this message or its attachments. Please notify the sender = immediately by return e-mail and permanently delete this message and any = attachments. Verio Inc. makes no warranty that this email is error or = virus free. Thank you.