Re: vlan(4) broken.

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Hello,
:
:Thank you for your help. I have successfully tested your patch with 
:several NICs vr(4), fxp(4), xl(4) and re(4). I've added support for 
:honoring the VLAN_MTU and VLAN_HWTAGGING parent interface flags. I was 
:able to test VLAN_MTU and VLAN_HWTAGGING handling with re(4). This means 
:we no longer have to manually set LINK0 on the vlan interface to enable 
:hardware support. I have also updated the man page.

    All committed, thank you!

:The only issue I can find is that tcpdump(1) listening on the parent 
:interface does not display the fact that the packets are encapsulated.
:
:   ifconfig vlan10 create vlan 10 vlandev vr0
:   ifconfig vlan10 inet 192.168.10.10 netmask 255.255.255.0
:   ping 192.168.10.20&
:
:   tcpdump -n -i vr0 icmp
:...
:I don't know if this is a bug or is just due to DragonFly using a newer 
:version of tcpdump. It had me thinking bpf handling wasn't working for a 
:while.
:
:Regards
:
:Gary

    I'm not going to worry about this for the release.  I suspect
    that the BPF tap is either in the wrong place or is not constructing
    the pseudo-header properly.

 						-Matt