Mon Oct 22, 2007 5:21 pm
Yep, what you need to do is think about where the traffic starts and stops. Thats first.
So lets use this:
192.168.0.0/24 is your clients
192.168.1./024 is your servers
then you have your internet connection, lets say, 1meg / 1meg is the connection rate
if you want your clients to get say, 3 meg to your servers, you have to define that, both directions.
so, if traffic comes from 192.168.1.x and is going to 192.168.0.x, then its internal
also, if you traffic comes from 192.168.0.x and is going to 192.168.1.x then it is also internal
Another rule to define your internet traffic would be
If traffic is coming from 192.168.1.x and is NOT going to 192.168.0.x, this is internet
if traffic is NOT coming from 192.168.0.x and is going to 192.168.1.x then it is internet
So now you have defined your network traffic. The two types, now create rules based on that. Mange your internal traffic first. If it does not match, then is passes on to the internet traffic rules (since you have only two, you can just say everything ELSE is internet traffic) something that is done quite often.
Something else you might wish to put in (cause if you are in a bridge this can happen), is to define client to client communications.. so, if traffic comes from 192.168.1.x and is going to a 192.168.1.x network, its internal, same difference the other way around.
Now, you have your mange rules, and you can mark your connections or packets however you wish.
Now, to track that, put it in a simple queue, set it to allow packets with the packet mark of internal ot 3meg both ways.
Then add another that say else and set it to 1meg.
Now you can't use PCQ if you want both rules, I don't like using PCQ even though I know quite a few people that do use them. Let us know of we can be more of a help!