On Sat, March 1, 2014 19:56, Chris Buechler wrote: > On Wed, Feb 26, 2014 at 8:48 AM, Nenhum_de_Nos <[email protected]> > wrote: >> >> On Wed, February 26, 2014 11:18, Nenhum_de_Nos wrote: >>> >>> hail, >>> >>> sometime agora I talked here about an adapter that was supported by FreeBSD >>> for altq, but >>> pfsense >>> was not listing it as one altq-able nic. I got another (ue, axe based), and >>> just WAN (em based) >>> shows in the "By Interface" page. >>> >>> I tried to find the mail and could not find the mail. Witch file I can >>> include ue as altq >>> enabled >>> nic ? >>> >>> thanks, >>> >>> matheus >> >> hail, >> >> found it. >> >> /etc/inc/interfaces.inc >> >> neither ue or axe is there. axe is gone, and I think all usb nic are now >> shown as ue. >> > > Those drivers don't have ALTQ support, which is why.
Chris, they do. That's what the pfsense team said back then, but I posted saying otherwise. See http://www.freebsd.org/cgi/man.cgi?query=altq&apropos=0&sektion=4&manpath=FreeBSD+8.3-RELEASE&arch=default&format=html, the altq man page includes axe as supported. And, although ue is not listed, it works fine. I edited that file on pfsense and the bridge is working like a charm, altq included. I used it on some versions of FreeBSD past HPS USB code, and some drivers that before wouldn't count on altq now is ok. I bought those axe adapter just for that :) if pftop -v queue shows the queues, the traffic shaping works, it is ok to say it i supported ? axe driver has altq references, ue doesn't. 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 _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
