From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Frischknecht peter@empoweringsolutions.com Date: Mon, 23 Oct 2000 22:31:30 +0000 Subject: [LARTC] I can control traffic based on IP ADDRESS but not on PROTOCOL Message-Id: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 
I have spent a tremendous amount of time on this one, and I can reproduce
it.

I set up all of my classes and queues.
Now is time for the filters.

Let's say that I have a flowid 1:100 which is the handle of a queue with a
very small bounded isolated bandwidth allocation of 25Kbit.

If I use the following filter:

tc filter add dev eth1 parent 1:0 protocol ip prio 25 u32 match ip src
216.79.164.46 flowid 1:100

I get the correct throughtput of 25Kbit.

However, if I attempt to filter by protocol instead, it does not work.
I will disregard the fact that this filter will manipulate both TCP and UDP
sessions destined to the specific port.
I am attaching to a server on port 8080 (0x1f90).

tc filter add dev eth1 parent 1:0 protocol ip prio 25 u32 match tcp src
0x1f90 0xffff flowid 1:100

A connection to the above port will yield the default bandwidth of 10Mbit.
Not the desired effect.

I have used many examples copied strainght out of the sources, in all of
them, the IP address matching works, but the TCP matching never does.

Any help is greatly appreciated.

Peter Frischknecht
Empowering Solutions, Inc.
http://www.empoweringsolutions.com
(864)654.6544 x103 Phone
(864)654.0022      Fax