From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 18:32:14 2004 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 5413F16A4CE for ; Mon, 20 Dec 2004 18:32:14 +0000 (GMT) Received: from mail.star-sw.com (mail.star-sw.com [217.195.82.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5382E43D31 for ; Mon, 20 Dec 2004 18:32:13 +0000 (GMT) (envelope-from nkritsky@star-sw.com) Received: from ARGON.star-sw.com (argon.star-sw.com [217.195.82.10]) by mail.star-sw.com (8.12.11/8.12.11) with ESMTP id iBKIW79T033695; Mon, 20 Dec 2004 21:32:07 +0300 (MSK) Received: from ibmka.stardevelopers4msi.com ([82.140.87.236]) by ARGON.star-sw.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 20 Dec 2004 21:32:07 +0300 Date: Mon, 20 Dec 2004 21:32:27 +0300 From: "Nickolay A. Kritsky" X-Mailer: The Bat! (v1.49) Personal X-Priority: 3 (Normal) Message-ID: <8510784015.20041220213227@star-sw.com> To: asegu@borgtech.ca In-reply-To: <3721.161.53.212.202.1103488437.squirrel@borg.darktech.org> References: <20041217094937.E4E6054C3@borgtech.ca> <721371959296.20041217154130@star-sw.com> <3721.161.53.212.202.1103488437.squirrel@borg.darktech.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Dec 2004 18:32:07.0801 (UTC) FILETIME=[360BE690:01C4E6C2] cc: freebsd-net@freebsd.org Subject: RE: FW: Curiosity in IPFW/Freebsd bridge. [more] 802.1q VLAN at fault? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Nickolay A. Kritsky" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 18:32:14 -0000 Hello asegu, This one should work OK. But do not forget to put parent interfaces in up and promisc mode in your rc.conf, otherwise you will not see any vlan-bridging. Sunday, December 19, 2004, 11:33:57 PM, asegu@borgtech.ca wrote: abc> Ok, the whole discussion to date led to how VLAN traffic wasn't being abc> registered by IPFW in my system. I think that it'll probably be too late abc> for a code change to fix my problem, so I'm going to go the route of abc> changing the network configuration. abc> I've rebuilt to 4.10 and.. And I had no luck there (IPFW _really_ doesn't abc> see the traffic now!). On the other hand, I've read about vlan pseudo-dev abc> and goten myself access to the switch's configuration. abc> So tomorrow evening I plan on changing the vlan id used to 3, and then in abc> freebsd, use the following configuration(and I post this to the list to abc> see if anybody knows that this is going to fail) fxp1 -->> router (uses ID 2) fxp0 -->> switch (uses ID 2, will switch to ID 3) abc> ifconfig vlan1 vlan 3 vlandev fxp0 abc> ifconfig vlan0 vlan 2 vlandev fxp1 abc> sysctl net.link.ether.bridge_cfg=vlan1,vlan0 abc> sysctl net.link.ether.bridge_ipfw=1 abc> Does anybody think this will allow IPFW to see the packets? or that this abc> will outright fail? abc> Thank you everybody, abc> Andrew -- Best regards, ; Nickolay A. Kritsky ; SysAdmin STAR Software LLC ; mailto:nkritsky@star-sw.com