On Sun, June 6, 2010 01:07, Chris Buechler wrote:
> On Sat, Jun 5, 2010 at 10:04 PM, Nenhum_de_Nos <[email protected]>
> wrote:
>> hail,
>>
>> I tried to enable the traffic shaper on this release, but it said at
>> least
>> one of the nic's is not supported for altq.
>>
>> I have an axe based Linksys USB200M, and onboard via rhine pci card. vr
>> is
>> said to support, but axe is not.
>>
>> but I then installed a vanilla FreeBSD 7.2R and loaded a simple ruleset
>> just to see if altq would complaint, and it did not.
>>
>> this 1.2.3R was upgraded from RC1, and had some other usb nics that were
>> not altq compatible. this would have anything to do with it ? I thought
>> about installing a vanilla 1.2.3R to test, but had no time to yet.
>>
>> is this the expected behavior ?
>>
>
> Yes, axe in 7.2 doesn't support altq.
>
> http://www.freebsd.org/cgi/man.cgi?query=altq&apropos=0&sektion=0&manpath=FreeBSD+7.2-RELEASE&format=html

thanks chris, I saw that. but i think the man page is not accurate:

pfTop: Up Queue 1-2/2, View: queue, Cache: 10000                       
13:27:19

QUEUE               BW SCH  PR  PKTS BYTES DROP_P DROP_B QLEN BORR SUSP
P/S  B/S
root_axe0        1000K hfsc  0     0     0      0      0    0            
0    0
 out_bolo         200K hfsc     1215 1378K      7  10598    0          
0.2   25

phoenix# pfctl -sq
queue root_axe0 on axe0 bandwidth 1Mb priority 0 {out_bolo}
queue  out_bolo on axe0 bandwidth 200Kb hfsc( default )

phoenix# uname -a
FreeBSD phoenix.apartnet 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Mon Jun  7
03:52:15 BRT 2010     [email protected]:/usr/obj/usr/src/sys/ALTQ 
i386

phoenix# ifconfig axe0
axe0: flags=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NEEDSGIANT>
metric 0 mtu 1500
        ether 00:xx:xx:xx:xx:xx
        inet 192.168.11.10 netmask 0xffffff00 broadcast 192.168.11.255
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

phoenix# usbdevs -dv
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
VIA(0x0000), rev 1.00
  uhub0
 port 1 powered
 port 2 powered
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
VIA(0x0000), rev 1.00
  uhub1
 port 1 powered
 port 2 powered
Controller /dev/usb2:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
VIA(0x0000), rev 1.00
  uhub2
 port 1 powered
 port 2 powered
 port 3 powered
 port 4 addr 2: high speed, power 250 mA, config 1, product
0x0018(0x0018), vendor 0x13b1(0x13b1), rev 0.01
   axe0

the kernel is GENERIC with ALTQ added.

so, if 7.2R is altq capable, 1.2.3R (7.2-p5) should as well, right ?

thanks,

matheus
-- 
We will call you cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Commercial support available - https://portal.pfsense.org

Reply via email to