From owner-freebsd-net Fri Apr 19 13: 3:11 2002 Delivered-To: freebsd-net@freebsd.org Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by hub.freebsd.org (Postfix) with ESMTP id C5F4337B416; Fri, 19 Apr 2002 13:02:41 -0700 (PDT) Received: (from ambrisko@localhost) by ambrisko.com (8.11.6/8.11.6) id g3JK1q748470; Fri, 19 Apr 2002 13:01:52 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200204192001.g3JK1q748470@ambrisko.com> Subject: Re: vlan traffic over ipsec tunnel In-Reply-To: <200204191713.g3JHDVg41265@arch20m.dellroad.org> To: Archie Cobbs Date: Fri, 19 Apr 2002 13:01:52 -0700 (PDT) Cc: Terry Lambert , "Peter J. Blok" , freebsd-hackers@FreeBSD.org, freebsd-net@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Archie Cobbs writes: | Terry Lambert writes: | > Bridging doesn't work with the vlanX interface currently in FreeBSD. | | Why not? | | I believe you, I've just never used vlans and always assumed | that they acted like normal Ethernet interfaces. Same here: a21p# ngctl list There are 5 total nodes: Name: ngctl53375 Type: socket ID: 00000006 Num hooks: 0 Name: an0 Type: ether ID: 00000005 Num hooks: 0 Name: vmnet1 Type: ether ID: 00000004 Num hooks: 0 Name: vlan0 Type: ether ID: 00000003 Num hooks: 0 Name: fxp0 Type: ether ID: 00000002 Num hooks: 0 a21p# ifconfig vlan0 vlan0: flags=8843 mtu 1500 inet 192.168.33.1 netmask 0xffffff00 broadcast 192.168.33.255 ether 00:10:a4:91:2e:ce vlan: 34 parent interface: fxp0 a21p# Would imply it should just work to bridge vlan's via netgraph bridging. As Archie said I have not tested this to prove how it does or does not work since I haven't had a need to try it. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message