From: Javier Miguel Rodriguez <javier@talika.fie.us.es>
To: lartc@vger.kernel.org
Subject: [LARTC] High Availability and QoS (problem with IP aliasing)
Date: Fri, 08 Jun 2001 05:43:34 +0000 [thread overview]
Message-ID: <marc-lartc-99198254914862@msgid-missing> (raw)
Hello
I am using Ultramonkey to create a highly available firewall linux
cluster. Everything works okay with ipchains or iptables...
The problem is with QoS... Ultramonkey creates a "cluster virtual" IP
address called eth0:0. I am using cbq script to control the bandwith, but it
does NOT work with ip-aliasing
Does anybody how to do QoS with an ip-aliased interface?
Thank you in advance
Greetings from Spain!
--
Javier Miguel Rodríguez. (GUFO)
Miembro del grupo Linux de la Facultad de Informática de Sevilla -o)
http://talika.fie.us.es/linux /\\
Linux Registered User #145051. _\_V
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-06-08 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 5:43 Javier Miguel Rodriguez [this message]
2001-06-08 7:47 ` [LARTC] High Availability and QoS (problem with IP aliasing) Juri Haberland
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-99198254914862@msgid-missing \
--to=javier@talika.fie.us.es \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox