I have set it up like so..

bandwidth_hogger="192.168.1.20"

# Queueing: rule-based bandwidth control.
altq on rl1 bandwidth 10Mb cbq queue {dflt, limited_pipe}
queue dflt bandwidth 9Mb cbq(default)
queue limited_pipe bandwidth 56Kb

and the rule I have set for this machine is:

pass from $bandwidth_hogger to any keep state queue limited_pipe

bandwidth hogger is still happily getting download speeds of 700k a second
:/

What have I missed?


"Peter N. M. Hansteen" <peter@bgnett.no> wrote in message
news:86d5ur9vu1.fsf@amidala.datadok.no...
> "Paul" <paul@rtfm.org> writes:
>
>> Ok.. I have an issue, the traffic I am wanting to limit is NAT'd
>> traffic.
>> Is this still possible to do?
>
> Whether you NAT or not should not affect your queueing. Your pass rule
> will
> be something like
>
> pass from $bandwidth_hogger to any port $allowed_ports \
> keep state queue thin_pipe
> pass from $rest_of_lan to any port $allowed_ports \
> keep state queue big_pipe
>
> - assuming of course you have defined bandwidth_hogger, allowed_ports,
> rest_of_lan and the queues thin_pipe, big_pipe already.
>
> My PF tutorial (http://www.bgnett.no/~peter/pf/en/) contains a few
> reasonably clear examples lifted from real world use which are slightly
> less complex than the ones in the excellent PF user guide.
> --
> Peter N. M. Hansteen, member of the first RFC 1149 implementation team
> http://www.blug.linux.no/rfc1149/ http://www.datadok.no/
> http://www.nuug.no/
> "First, we kill all the spammers" The Usenet Bard, "Twice-forwarded tales"