From owner-freebsd-net  Fri Apr 19 13:20:49 2002
Delivered-To: freebsd-net@freebsd.org
Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38])
	by hub.freebsd.org (Postfix) with ESMTP
	id DAEE437B425; Fri, 19 Apr 2002 13:20:19 -0700 (PDT)
Received: from InterJet.elischer.org ([12.232.206.8])
          by rwcrmhc51.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020419202019.KWBZ1143.rwcrmhc51.attbi.com@InterJet.elischer.org>;
          Fri, 19 Apr 2002 20:20:19 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA08503;
	Fri, 19 Apr 2002 13:18:17 -0700 (PDT)
Date: Fri, 19 Apr 2002 13:18:16 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Doug Ambrisko <ambrisko@ambrisko.com>
Cc: Archie Cobbs <archie@dellroad.org>,
	Terry Lambert <tlambert2@mindspring.com>,
	"Peter J. Blok" <Peter.Blok@inter.NL.net>,
	freebsd-hackers@FreeBSD.org, freebsd-net@FreeBSD.org
Subject: Re: vlan traffic over ipsec tunnel
In-Reply-To: <200204192001.g3JK1q748470@ambrisko.com>
Message-ID: <Pine.BSF.4.21.0204191316370.8266-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org

failing that, I have just had "contributed"
some code that produces an actual "vlan" netgraph node.
You attach it to the ethernet node.. I'm still
reading it to work out what it does..


On Fri, 19 Apr 2002, Doug Ambrisko wrote:

> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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-hackers" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message