On Mon, Oct 09, 2000 at 02:46:17PM +0200, joern maier wrote: > Hi there, > > I got a question about CBQ, hope anybody can help me (did not found > anything > in the archives). This is the first post ever on the LARTC list, so this does not amaze me :-) > My setup is like this: > all hosts are Athlon 800MHZ, 256 MByte RAM and 3com9x Netcards (100MBit) > Distribution SuSE 7.0 -> Kernel 2.2.16 > > Host Setup: > > ---www_server_1 > / > --------------|-------------www_server_2 > load balancer \ > (with CBQ) ---www_server_3 > 192.168.10.17 > > > all I want to do is shaping the INCOMING traffic this means > that if I define a special IP only 200Kbit of HTTP request > traffic (as an example) is forwarded to the webservers from > that IP. Well, you can't shape incoming traffic directly. You can shape traffic going out to www_server_[123]. > The load balancer (Linux Virtual Server) works on IP basis and > is integrated as a patch into the system-kernel. It distributes > the packets via "direct routing" this means load balancer and > www_server_X have all the same IP. If a package is received by > the LB it changes the MAC Address of the package and forward it > to the right www_server_X. Perhaps this interferes with Linux traffic shaping, not sure. Does your loadbalancer have multiple ethernet cards? If so, you could shape the 'backend card' to limit itself to 200kbit. > The following attempts did not work: > > using the fw filter: > implementing one of the following rules via ipchains did not work: > (ip 192.168.10.15 is the client I want to restrict bandwidth) > > ipchains -A forward -p ip -d 192.168.10.17 m 1 -j ACCEPT > or > ipchains -A output -p ip -d 192.168.10.17 m 1 -j ACCEPT > or > ipchains -A forward -p ip -s 192.168.10.15 m 1 -j ACCEPT > or > ipchains -A output -p ip -s 192.168.10.15 m 1 -j ACCEPT > > the filter was set up with the following rule > > tc filter add dev eth0 protocol ip parent 100:0 prio 100 handle 1 fw > classid 100:100 Did you enable 'shaping based on fwmark' when compiling the kernel? > should be reduced to to let´s say 200Kbit, with the last two rules > traffic > from source IP 192.168.10.15 sould be reduced to 200Kbit. Non did work. > > using the u32 filter: > > tc filter add dev eth0 parent 100:0 protocol ip prio 100 u32 match ip > src 192.168.10.15 flowid 100:100 Here you match outgoing traffic on eth0 with a source of your webbrowser client. > the whole outgoing traffic was reduced to 200Kbit. > So if anybody has an idea what I did wrong in first place I would be > very > happy if you could tell me. Or is it impossible to shape incomming > traffic > like this. If you need any further information please ask me. Please give some details on your network cards, and include where 192.168.10.15 is in this picture, and which card it is connected to, and which card the webservers are connected to. Regards, bert hubert -- PowerDNS Versatile DNS Services Trilab The Technology People 'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
