From: "Tomasz Chilinski" <chilek@chilan.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] is round-robin on interface aliases possible?
Date: Sat, 16 Oct 2004 09:51:53 +0000 [thread overview]
Message-ID: <20041016094802.M54664@chilan.com> (raw)
In-Reply-To: <417056ED.3060505@sysd.org>
On Fri, 15 Oct 2004 20:02:05 -0300, Stanislaw Pusep wrote
> Hello, I'm new to the list and iproute2 itself. I was searching for
> a way to simultaneously use several IPs on the *same network
> interface* for outbound traffic. Let me explain: I have eth0
> interface to which I set 2 IP addresses; 192.168.0.1 and
> 192.168.0.2. Then I want to connect to Internet through
> 192.168.0.254 gateway using round-robin between those 2 addresses.
> The iproute2 usage that best fits my needs is following:
> http://lartc.org/howto/lartc.rpdb.multiple-links.html But I was
> unable to get it working, as it supposes I have 2 *interfaces*
> while I have only 1 interface with aliases. I'm simply unable to set
> the same gateway on both IPs as it seems to be per-device setting. I
> am aware that iptables is able to do it with: iptables -t nat -A
> POSTROUTING -o eth0 -j SNAT -to-source 192.168.0.1-192.168.0.2 This
> actually doesn't fits my needs as it only applies to masquerade
> networks. Any suggestions? Thanks for attention!
You can use nth and connmark extensions (patch-o-matic from
http://netfilter.org) with two route tables. This way you can get load
balancing for ip dialogues.
--
Kind regards,
Tomasz Chilinski
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-10-16 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 23:02 [LARTC] is round-robin on interface aliases possible? Stanislaw Pusep
2004-10-16 9:51 ` Tomasz Chilinski [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=20041016094802.M54664@chilan.com \
--to=chilek@chilan.com \
--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 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.