Chris Zakelj wrote:
>>
> 
> Welcome to the crew.  Sounds like you're doing pretty much the exact
> same thing I was doing last year on an ADSL line shared between myself
> and two roomies.  If you haven't gotten all the way through it yet, read
> the PF user's guide at http://www.openbsd.org/faq/pf/index.html, and pay
> special attention to the examples in the "Packet Queueing and
> Prioritization" section.  While leaving the particular rules up to you,
> I'll make the following suggestions:
> 
> 1: Set your upload bandwidth to about 125% of your advertised rate
> 2: Unless it was just dumb luck, there's nothing wrong with using the
> full bandwidth of your internal interface.
> 3: I've had better results using CBQ on internal interfaces, and PRIQ on
> the external.  In my 3-person condo last year, using your 300k
> downstream, I'd set 100k (borrow) to each person internally, so that if
> someone's not using their straw, the others could borrow from it. 
> Likewise, my outbound priority was something along the lines of ACK,
> DNS, SSH, HTTP, SMTP/POP, bulk (one was an anime freak, and forcing his
> habit into the 'bulk' queue allowed the rest of us to surf in peace).
> 
> Obviously, what worked best for me may not be best for you.
> 
> 
Thanks for the prompt reply. I had some luck yesterday with altq. I've
put 300kb as bandwidht limit in my internal iface and 150Kb in my
external iface. And assigned traffic to the download queue (300Kb) and
it worked. The only problem is that i'm using keep state in all of my
rules, and i'll have to change this behavior to filter the incoming and
the outcoming packets. I only run into one problem, the connections to
the firewall itself (ssh, for example) ended being queued to. And 300Kb
is a very little bandwidth if you have 2 simultaneous downloads. But i
believe that no using keep state for some of my rules will do the trick.

My regards,

-- 
Giancarlo Razzolini
Linux User 172199
Moleque Sem Conteudo Numero #002
Slackware Current
Snike Tecnologia em Informatica
4386 2A6F FFD4 4D5F 5842  6EA0 7ABE BBAB 9C0E 6B85

Reply via email to