ALTQ + vlan

[Radosław Kujawa <radoslaw.kujawa%altkom.pl@localhost>]

Hello list,
  I am trying to configure ALTQ on a server, where multipie vlan(4)'s are
used. However, it looks like ALTQ and vlan are incompatible.

  For example, let's assume that bge1 is the interface, where vlans are
configured:

# ifconfig bge1
bge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        enabled=0
        address: 00:11:85:c5:cb:41
        media: Ethernet autoselect (1000baseT full-duplex)
        status: active
# ifconfig vlan0
vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        enabled=0
        vlan: 1 parent: bge1
        address: 00:11:85:c5:cb:41
        inet 10.4.0.1 netmask 0xffffff00 broadcast 10.4.0.255
        inet alias 10.10.10.3 netmask 0xffffff00 broadcast 10.10.10.255

  Unfortunately, it does not matter what kind of ATLQ classes and filters
are set up, every packet will always go to the default class. I have
following rules for bge1:

interface bge1 bandwidth 100M cbq
class cbq bge1 root_class NULL priority 0 pbandwidth 100
class cbq bge1 net_class root_class exactbandwidth 756000
        filter bge1 net_class 0 0 0 0 0
class cbq bge1 lan_class root_class pbandwidth 95 default
        filter bge1 lan_class 10.4.0.0 netmask 16 0 192.168.0.0 netmask 16
0 0

  altqstat clearly shows that even packets for 192.168.0.0 network are
going into net_class.
  Of course, at first I tried using vlan0 instead of bge1 - it does not
make any difference.

  I did some experiments - after disabling vlans everything worked as
expected. I suspect that ATLQ'ing traffic takes place before
deencapsulation of 802.1q... Is this a known problem? Should I gather
more data and fill PR?

Greetings
Radoslaw Kujawa