Require example to limit all ips on a specified port ie:1214

[paulmacp]

I am BW limiting customers on all ports at 1.5m down & 640kb up. I would like to add to that a global setting to limit the upload speeds for all customers on port 1214 to only 56k up. If someone could provide a example that would be greatly appreciated.

Thanks..

[tony]

For shaping an IP or subnet, use the syntax below:

cust1=101
pipe $cust1 bw 56K
shape tcp to pipe $cust1 from <customer_or_net> 1214 to any out via $net

Thanks!

[paulmacp]

Thanks Tony..

[paulmacp]

Hi

I must be missing something... call me slow or whatever..

This is what I have in my config and it does not seem to work
** I have it setup just as a BW server only with just nic's

input1 = ether1 ** Incoming dsl1
sector1 = ether2 ** Customers

kazaa=101
pipe $kazaa bw 0k
shape tcp to pipe $kazaa from 10.10.11.0/25 1214 to any out via $input1

I have also tried to change the out via $sector1 as well and it still lets traffic on port 1214 out. It does read 0 bytes in the traffic report.

What am I missing... Thanks

[lonnie]

The bandwidth manager does not control down to 0K. the lowest is about 5K. I guess we should document that. Very sorry.

The block you are trying to do is more appropriate for a firewall rule. You use a firewall to block and the CBQ to limit.

[paulmacp]

Hi

My intention is to limit it to 10 - 15 k anyway... I just wanted to test it and confirm it was correct. Im having a hard time getting my head around the "out via $net".
If $net1 is the main feed and $net2 the customer is on. To me from the customer side they are both out.. ?

The other question is in the system example for shape there is [sport] & [dport]... What does this reference to.. ?

The reason for that question is it may be required to BW a range of ports and would be nice to include that range in one statement if possible... Thank You

[pnutz]

I would like to do something like this but it does not seem to work

all of the client a controled by ip but i would like to also slow down other ports as well can this be done?

(example)

cust1=101
pipe $cust1 bw 56K
shape tcp to pipe $cust1 from ip 119 to any out via $net
cust1=101
pipe $cust1 bw 10K
shape tcp to pipe $cust1 from ip 119 to any out via $net


qshape 70 bw fb 600K 160K ip on $client
qshape 71 bw fb 600K 160K ip on $client
qshape 74 bw fb 600K 160K ip on $client
qshape 75 bw fb 600K 160K ip on $client
qshape 76 bw fb 600K 160K ip on $client

I am looking to slow down news servers and all of the users ip's are public

[lonnie]

# news users
news = 5
pipe $news bw 56K
typical = "bw fb 600K 160K share 119 pipe $news"

qshape 70 $typical ip on $client
qshape 71 $typical ip on $client
qshape 74 $typical ip on $client
qshape 75 $typical ip on $client
qshape 76 $typical ip on $client

All news will share the 56K pipe and all other traffic will get their own private 600K download with fallback and 160K upload.

[paulmacp]

Hi Maybe this got missed so I'll repost

The other question is in the system example for shape there is [sport] & [dport]... What does this reference to.. ?

The reason for that question is it may be required to BW a range of ports and would be nice to include that range in one statement if possible... Thank You

[tony]

Hi Maybe this got missed so I'll repost

The other question is in the system example for shape there is [sport] & [dport]... What does this reference to.. ?

The reason for that question is it may be required to BW a range of ports and would be nice to include that range in one statement if possible... Thank You

The sport and dport represent the tcp/udp source and destination port numbers. (ie, if you wish to shape on a per-port basis). Port ranges in the CBQ script are not supported.

Thanks

[paulmacp]

Thanks Tony..

[pnutz]

:(

[pnutz]

:?:

[paulmacp]

Hello

I assume that the last 2 posts are a sign of dissapiontment... while it would be nice to have a range option on restricting the speed of certian ports. The product as it is... I must say I am very pleased with its performance and having being a user/abuser of it for the past 10 months can say support has been excellent... :) Keep it up..

[pnutz]

yes the disapointment would be that port limiting does not seem to work and the lack of any response!


I can limit the ip or end user just fine but to limit a port to use only the bandwidth i set does not work.

[tony]

yes the disapointment would be that port limiting does not seem to work and the lack of any response!


I can limit the ip or end user just fine but to limit a port to use only the bandwidth i set does not work.

I believe we have replied to all your questions, but apologies if we have missed any.

With port ranges aside, what problems are you encountering with the 'shape' command, and it's ability to shape based on ports? If you wish, please email be directly as I would like to lend some assistance.

The reply to your message from Lonnie on 29 Nov 2002 08:14 am shows an accurate method for doing what you wish.

If you wish to control the upload to port 119 (news), then you can add one more line per rule as follows.

This method will share pipe 5 with anybody using news. You can easilly modify to use a different pipe for each user if you do not wish them to share a common one.

news = 5
pipe $news bw 56K
typical = "bw fb 600K 160K share 119 pipe $news"

shape tcp to pipe $news from ip to any 119 in via $client
qshape 70 $typical ip on $client

shape tcp to pipe $news from ip to any 119 in via $client
qshape 71 $typical ip on $client

shape tcp to pipe $news from ip to any 119 in via $client
qshape 74 $typical ip on $client

shape tcp to pipe $news from ip to any 119 in via $client
qshape 75 $typical ip on $client

shape tcp to pipe $news from ip to any 119 in via $client
qshape 76 $typical ip on $client

Thanks!

[tony]

As an update. There will be including CBQ port ranges in the next release, as well as the ability to shape the 'icmp' protocol by itself. (it's normally only shapeable if specified with the 'all' protocol flag on the shape command which is not desirable)

We are hoping to include more options as time goes on.

[tony]

The sport and dport represent the tcp/udp source and destination port numbers. (ie, if you wish to shape on a per-port basis). Port ranges in the CBQ script are not supported.

Thanks

Latest release has support for ICMP-only shaping, as well as port ranges.

Thanks!

[paulmacp]

Thanks... the ranges will simplify the process of filtering greatly..
:D

[tony]

It should be very handy to many people. More features are in the works, but this is a good start.

Thanks!