From: "Gáspár Lajos" <swifty@freemail.hu>
To: "Javier Gálvez Guerrero" <javier.galvez.guerrero@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Mapping multiple interfaces to a single IP address
Date: Thu, 01 Oct 2009 18:06:08 +0200 [thread overview]
Message-ID: <4AC4D370.6090503@freemail.hu> (raw)
In-Reply-To: <145d4e1a0910010330r216e68cch763b6c7a4b954992@mail.gmail.com>
Hi,
Javier Gálvez Guerrero írta:
> Hi there,
>
> I would like to know if it is possible to map multiple network
> interfaces into a single IP address in order to perform load balancing
> and network channels virtualization/abstraction tasks. If so, could
> you please point me to the proper iptables modules that are needed in
> client and routing elements?
>
You may have the same ip address on multiple interfaces.
I have a following setup:
br1 Link encap:Ethernet
inet addr:172.16.1.254 Bcast:172.16.1.255 Mask:255.255.254.0
...
lan1 Link encap:Ethernet
inet addr:172.16.1.254 Bcast:172.16.1.255 Mask:255.255.254.0
...
vpn-bia Link encap:UNSPEC
inet addr:172.16.1.254 P-t-P:192.168.10.254 Mask:255.255.255.255
...
In this scenario I have three physical NICs: lan1, wan1, mfl1.
I have also some vlans.
lan1 connected to the local subnet.
br1 consist of vlan100 and vpn1. These are virtual interfaces.
The endpoint of vpn1 is on wan1. vlan100 is on lan1.
vpn-bia is a tunnel over the mfl1 connection.
So it is all working. But you have to have some routing rules.
These are mine:
next prev parent reply other threads:[~2009-10-01 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 10:30 Mapping multiple interfaces to a single IP address Javier Gálvez Guerrero
2009-10-01 16:06 ` Gáspár Lajos [this message]
2009-10-01 16:11 ` Mapping multiple interfaces to a single IP address (cont.) Gáspár Lajos
2009-10-01 16:17 ` Gáspár Lajos
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=4AC4D370.6090503@freemail.hu \
--to=swifty@freemail.hu \
--cc=javier.galvez.guerrero@gmail.com \
--cc=netfilter@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.