I had a look at this a while ago (and a quick check again seems to bring up
the same results).

The FreeBSD 6.2 branch does not support VLAN tagging in the vr driver.
Release 7 will, but that will be of very little help to you at the moment.




On 21/11/07 13:45, "Bill Arlofski" <waa dash m0n0wall at revpol dot com> wrote:

> 
> OK, I needed another firewall and decided that since WRAPS are EOL and
> no longer available through my normal vendors that I would sell off my
> WRAP and test/use the new ALIX 3port board in my office.
> 
> The install went fine, the new ALIX 3port boards are the same size/shape
> as the old WRAP 3port boards and fit perfectly in the old wrap aluminum
> cases. I was sure they wouldn't based on some initial information on the
> ALIX boards.
> 
> Any way, just as Manuel mentioned in an Aug 2007 post, I needed to
> change the "sis" ethernet interfaces in the config.xml to "vr" and
> upload to the new ALIX board.  This also went well.
> 
> My small office network is slightly more complex than most others and
> probably more complex than it needs to be but I _require_ VLAN support
> in my m0n0wall box because of this. I have several VLANS trunked to my
> m0n0wall's LAN interface where m0n0wall filters and forwards traffic as
> necessary.
> 
> It seems that the VR network interfaces do NOT support VLANS under
> FreeBSD, and hence m0n0wall can not support them.
> 
> What are my options?
> 
> Where is the breakdown? I mean, is it simply that VLAN support on vr
> devices are not supported upstream by the FreeBSD core team? Is it that
> vr devices simply can not properly support VLANS at a hardware level?
> 
> P.S. Anyone want to trade a BRAND NEW ALIX 3port for a recent WRAP
> 3port?   :)
> 
> 
> sigh..
> 
> --
> Bill Arlofski
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>