PF + ALTQ... help please!!

[Marcelo Celleri]

Sorry, but it was a mistake when I wrote the mail...

The configuration looks like this:

queue marcelo bandwidth 128Kb cbq { gold, silver, default }
queue gold bandwidth 70% priority 3 cbq(borrow red)
queue silver bandwidth 20% priority 2 cbq(borrow red)
queue default bandwidth 10% cbq(borrow)

 

pass in on $int_if from any to xxx.xxx.xxx.xxx keep state queue default
pass in on $int_if proto tcp from any port { 25,110 } to 200.49.242.42 \
keep state queue silver
pass in on $int_if proto tcp from any port { 22,80,443 } to 200.49.242.42 \
keep state queue gold
pass in on $int_if proto { udp,tcp } from any port 53 to 200.49.242.42 \
keep state queue gold

But it doesn't work like I want...

-----Mensaje original-----
De: jsimola at gmail.com [mailto:jsimola at gmail.com] En nombre de Jon Simola
Enviado el: Miércoles, 30 de Noviembre de 2005 18:08
Para: Marcelo Celleri
CC: freebsd-pf at freebsd.org
Asunto: Re: PF + ALTQ... help please!!

On 11/30/05, Marcelo Celleri <marceloc at espoltel.net> wrote:
> $int_if="em1"
> queue marcelo bandwidth 128Kb cbq { gold, silver, default }
>         queue marcelo1 bandwidth 70% priority 3 cbq(borrow red)
>         queue marcelo2 bandwidth 20% priority 2 cbq(borrow red)
>         queue marcelodf bandwidth 10% cbq(borrow)

You've omitted a lot of the pf.conf file. The only thing I can suggest
is that you name the sub-queues (marcelo1/2/df) the same as what the
queue expects them to be named (gold/silver/default).

Like this:
altq on em0 cbq bandwidth 100Mb queue { default_ext, throttle_ext }
queue default_ext bandwidth 40Mb qlimit 1000 priority 5 cbq(default red ecn)
queue throttle_ext bandwidth 64Kb priority 1 cbq(red ecn)

> pass in on $int_if proto { udp,tcp } from any port 53 to 200.49.242.42
keep
> state queue gold

Not actually having defined a gold queue, that does nothing.

--
Jon Simola
Systems Administrator
ABC Communications

-- 
Este mensaje ha sido analizado por el antivirus de ESPOLTEL S.A.
en busca de virus y otros contenidos peligrosos,
y se considera que está limpio.


-- 
Este mensaje ha sido analizado por el antivirus de ESPOLTEL S.A.
en busca de virus y otros contenidos peligrosos,
y se considera que está limpio.