From: joern maier joern.maier@informatik.uni-ulm.de
To: lartc@vger.kernel.org
Subject: [LARTC] CBQ and load balancing
Date: Tue, 10 Oct 2000 13:42:05 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216770@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216760@msgid-missing>
<PRE>bert hubert wrote:
><i> </I>
><i> On Tue, Oct 10, 2000 at 12:36:36PM +0200, joern maier wrote:
</I>><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 </I>want
><i> > > everyone to benefit.
</I>><i> >
</I>><i> > sorry -> I just pushed the reply button not thinking that it won´t </I>get
><i> > back
</I>><i> > to the list but to your private e-mail account
</I>><i> </I>
><i> What we need to do is setup a class for packets going out on eth0 with </I>a dst
><i> address of the backend, and then limit that. CBQ doesn't know what an
</I>><i> eth0:110 is, it only knows that you have eth0, and that addresses have </I>been
><i> assigned to it. Try running "ip addr show dev eth0", and you'll see
</I>><i> 192.168.10.17 with eth0, and not with eth0:110.
</I>><i> </I>
I did run "ip addr show dev eth0" the result was this:
2: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc cbq qlen 100
link/ether 00:01:02:07:5f:cf brd ff:ff:ff:ff:ff:ff
inet 192.168.10.6/24 brd 192.168.255.255 scope global eth0
inet 192.168.10.17/32 brd 192.168.255.255 scope global eth0:110
so to me it looks like ..10.17 works with eth0:110
><i> You can either mark packets leaving your host with the destination of y</I>our
><i> magic ip addresses, and you'll limit them all together to 200kbit, or y</I>ou
><i> can try to make more classes, one for each backend server, and select o</I>n the
><i> basis of the real mac address.
</I>><i> </I>
><i> Regards,
</I>><i> </I>
><i> bert hubert
</I>><i> </I>
><i> --
</I>><i> PowerDNS Versatile DNS Services
</I>><i> Trilab The Technology People
</I>><i> 'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</I>><i> </I>
><i> _______________________________________________
</I>><i> LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO: <A HREF="http://ds9a.nl/2.4=">http://ds9a.nl/2.4=</A>
</I>Routing/
</PRE>
next prev parent reply other threads:[~2000-10-10 13:42 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 [this message]
2000-10-10 13:53 ` bert
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-98373938216770@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.