On Fri, Oct 07, 2005 at 04:56:32PM +0200, Oliver Fromme wrote:
> [broken quoting fixed]
>
> Donatas <[EMAIL PROTECTED]> wrote:
> > Oliver Fromme wrote:
> > > Donatas <[EMAIL PROTECTED]> wrote:
> > > > Just wonder - what is the major reason double vlan support
> > > > (also known as q-in-q or n
[broken quoting fixed]
Donatas <[EMAIL PROTECTED]> wrote:
> Oliver Fromme wrote:
> > Donatas <[EMAIL PROTECTED]> wrote:
> > > Just wonder - what is the major reason double vlan support
> > > (also known as q-in-q or nested vlan) is still not included
> > > in freebsd.
> >
> > It is suppor
netgraph sweet netgraph...
think you understand on my mind was a liitle bit different solution of the
problem :]
ifconfig vlan 10 create && ifconfig vlan10 vlan 10 vlandev fxp0
ifconfig vlan 111 create && ifconfig vlan111 vlan 111vlandev vlan10
> Donatas <[EMAIL PROTECTED]> wrote:
> > Just wo
Donatas <[EMAIL PROTECTED]> wrote:
> Just wonder - what is the major reason double vlan support (also known as
> q-in-q
> or nested vlan) is still not included in freebsd.
It is supported, for years already (even in FreeBSD 4.x).
See ng_vlan(4). You can even do q-in-q-in-q if you want
(do C
Just wonder - what is the major reason double vlan support (also known as
q-in-q or nested vlan) is still not included in freebsd. The need for this
feature is growing parallely with new L3 switches being available (cisco,
allied telesyn, foundry networks etc...). Enabling this in some cases co
