On Sunday 13 February 2005 22:36, David Gilbert wrote: > Has anyone considered patching the vlan driver to support altq? I > gather that since tun works, so should vlan.
This should be a FAQ. Anyway, here is the story:
While you can do ALTQ queueing on vlan interfaces the usefulness of this is
very little. If the physical interface supports ALTQ it is *always* better
to do the queueing there. If the physical interface does not support ALTQ it
must be patched.
To configure queueing on physical interfaces you do the following:
Suppose we have the following VLAN:
vlan0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.10.1 netmask 0xffffff00
ether [---]
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vlan: 1 parent interface: xl0
pf.conf:
phy_if = xl0
vlan_if = vlan0
slow_peers = "{ 192.168.10.23, 192.168.10.42 }"
# QUEUE on physical interface:
altq on $phy_if cbq bandwidth 10Mb queue { default, limited }
queue default bandwidth 75% cbq(borrow default)
queue limited bandwidth 25% cbq
block all
# CLASSIFY on virtual interface:
pass on $vlan_if from $vlan_if:network to any keep state queue default
pass on $vlan_if from $slow_peers to any keep state queue limited
#EOF
If that does not help you, please try to explain what exactly you try to
achieve and why it is not possible with this method. Thanks.
--
/"\ Best regards, | [EMAIL PROTECTED]
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED]
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
pgpg2Q0T4Nf9v.pgp
Description: PGP signature
