From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] CBQ and load balancing
Date: Tue, 10 Oct 2000 13:53:53 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216767@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216760@msgid-missing>
<PRE>On Tue, Oct 10, 2000 at 12:36:36PM +0200, joern maier wrote:
><i> bert hubert wrote:
</I>><i> >
</I>><i> > On Mon, Oct 09, 2000 at 04:32:58PM +0200, joern maier wrote:
</I>><i> > > o.k. here some more details I haven´t mentioned yet
</I>><i> >
</I>><i> > Please keep it on the list, I don't like to give private advice, I want
</I>><i> > everyone to benefit.
</I>><i>
</I>><i> sorry -> I just pushed the reply button not thinking that it won´t get
</I>><i> back
</I>><i> to the list but to your private e-mail account
</I>
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 see
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
--
PowerDNS Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
prev parent reply other threads:[~2000-10-10 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-09 12:46 [LARTC] CBQ and load balancing joern
2000-10-09 14:08 ` bert
2000-10-10 10:36 ` joern
2000-10-10 13:42 ` joern
2000-10-10 13:53 ` bert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-98373938216767@msgid-missing \
--to=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.