From owner-freebsd-net Mon Aug 7 9:44: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp.whitebarn.com (Spin.WhiteBarn.Com [216.0.13.113]) by hub.freebsd.org (Postfix) with ESMTP id 8B15437B50B for ; Mon, 7 Aug 2000 09:43:57 -0700 (PDT) (envelope-from Bob@WhiteBarn.Com) Received: from WhiteBarn.Com (BarnStorm.WhiteBarn.Com [216.0.13.81]) by smtp.whitebarn.com (8.9.3/8.9.3) with ESMTP id LAA28631; Mon, 7 Aug 2000 11:42:20 -0500 (CDT) (envelope-from Bob@WhiteBarn.Com) Message-ID: <398EE6EC.26646EE9@WhiteBarn.Com> Date: Mon, 07 Aug 2000 11:42:20 -0500 From: Bob Van Valzah Organization: WhiteBarn Web Works X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Pedro J. Lobo" Cc: freebsd-net@FreeBSD.ORG Subject: Re: VLAN Config Advice References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I found my problem in misconfiguration between my Cisco FreeBSD. Details below. "Pedro J. Lobo" wrote: > > If I do ifconfig fxp0 first and then ifconfig vlan0 on top of it, I get > > a booted system. However, arp issues lots of warning messages about > > packets arriving on fxp0 when they should be on vlan0 and I can't ping > > the box. > > Hmmm, I've been using simultaneously fxp0 (i.e., without tag) and vlan0 > (tagged, hooked on fxp0) without any problems. Are you sure you are > configuring fxp1 and vlan0 with addresses that are on different subnets? I've learned that 802.1q has this notion of a "native VLAN." On Ciscos (at least) that defaults to VLAN 1. My problem was that I had my FreeBSD vlan0 interface configured on an IP network that was on VLAN 1. My cisco wasn't tagging packets for VLAN 1 so they appeared to arp as if they were arriving on fxp0 (the physical interface) even though the arp request went out on vlan0. There are two simple fixes. 1) On the cisco side: "switchport trunk native vlan 999" or some other VLAN you're not using. This has the effect of forcing the Cisco to tag traffic for all VLANs in use. 2) Configure the physical interface for the IP network on VLAN 1. This is probably a little cleaner in that it doesn't depend on the VLAN code working at all to have at least one working IP address. Does anybody with experience on other switches know if VLAN 1 is always the default native VLAN? Either way, this quirk should be mentioned in the Handbook in the VLAN section (still to be written). Thanks, Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message