> Note that only the pf.conf directives that apply directly to the above policy > are present; nat, rdr, options, etc., are not shown.
Yeah, I noticed that too =) But I don't know if that setup would work without NAT enabled. But then, I'm no network expert... > Bear in mind that while a queue is applied to the egress interface, > the classification of that traffic may take place on another > interface. So you could do something more like this: > > pass from 192.168.0.5 to ! <mynet> keep state queue traffic1_ext I considered trying that, but I think that queueing only the egress interface wouldn't solve my problem. Since my link to the internet is an ADSL line, 1Mb downstream and 512Kb upstream, I think that the only sane way to queue both up and down bandwidth would be to set up altq on the egress interface (for queueing uploads) and another altq on the internal interface (for queueing downloads). The big problem here is that I have _three_ internal interfaces that must share the internet link. I considered setting a hard limit on each internal interface (33% each), but that can't be, since I need them to borrow available bandwidth and have different priorities on downloading via the external interface. Does anyone has any ideas on how to accomplish such a setup? Leonardo Rodrigues
