From mboxrd@z Thu Jan 1 00:00:00 1970 From: bert hubert ahu@ds9a.nl Date: Tue, 10 Oct 2000 13:53:53 +0000 Subject: [LARTC] CBQ and load balancing Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org 
On Tue, Oct 10, 2000 at 12:36:36PM +0200, joern maier wrote:
> bert hubert wrote:
> >=20
> > On Mon, Oct 09, 2000 at 04:32:58PM +0200, joern maier wrot=
e:
> > > o.k. here some more details I haven=B4t mentioned yet
> >=20
> > Please keep it on the list, I don't like to give private a=
dvice, I want
> > everyone to benefit.
>=20
> sorry -> I just pushed the reply button not thinking that it=
 won=B4t get
> back
> to the list but to your private e-mail account

What we need to do is setup a class for packets going out on eth0 with a dst
address of the backend, and then limit that. CBQ doesn't know what an
eth0:110 is, it only knows that you have eth0, and that addresses have been
assigned to it. Try running "ip addr show dev eth0", and you'll s=
ee
192.168.10.17 with eth0, and not with eth0:110.

You can either mark packets leaving your host with the destination of your
magic ip addresses, and you'll limit them all together to 200kbit, or you
can try to make more classes, one for each backend server, and select on the
basis of the real mac address.

Regards,

bert hubert

--=20
PowerDNS                     Versatile DNS Services =20
Trilab                       The Technology People  =20
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet