From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: More ethernet port same ip address
Date: Sun, 20 Jul 2008 18:41:41 -0500 [thread overview]
Message-ID: <4883CD35.3060704@riverviewtech.net> (raw)
In-Reply-To: <48819901.6030604@unipex.it>
On 7/19/2008 2:34 AM, Michele Petrazzo - Unipex srl wrote:
> I need to setup a linux box with more than one ethernet ports and
> every one must have the same ip address. I, of course :), already
> tried to do it with a lot of solutions that linux offer
> (iptables+mark+ip route, bonding, a vlan every port), but with the
> same result... Packet come into the right port but go out through the
> "last" that I have set, so it will never arrive.
>
> Here the server have the two ports with 172.16.0.1 and two clients,
> connected into the two others has 172.16.0.3 and 172.16.0.10
>
> It's there a solution for achieve this?
Like others have said, I think (based on what little you have said) that
bridging is an appropriate option. I say "think" because I don't know
if you are trying to filter what passes between the two sides of the server.
Could you do what you are wanting to do by moving the two ethernet
cables that connect to the server over to a switch and then run one
cable from the switch to the server? If this will work, bridging will
do exactly the same thing in software.
I'd suggest that your bridge the two interfaces (with out any IPs) and
bind the 172.16.0.1 IP address to the bridge interface its self.
With regards to the question about choosing which interface the traffic
will go out, (with out forcing its hand) bridging does the exact same
thing as a switch would. When you send a packet to a given destination
the bridge will send the ethernet frame containing the packet out the
port that is destination MAC is connected to. If the port the
destination MAC is connected to is not known bridging will send the
frame out all ports until it does know what port it is connected to
(i.e. the bridge receives a reply thus learning the port).
I say "with out forcing its hand" because there are a lot of things that
you can do with EBTables and / or IPTables to encourage bridging to do
what you want if it is not the norm.
Grant. . . .
next prev parent reply other threads:[~2008-07-20 23:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 7:34 More ethernet port same ip address Michele Petrazzo - Unipex srl
2008-07-19 8:18 ` Bernhard Bock
2008-07-19 13:46 ` Michele Petrazzo - Unipex srl
2008-07-19 14:01 ` Leonardo Rodrigues Magalhães
2008-07-19 14:13 ` Jan Engelhardt
2008-07-19 15:14 ` Michele Petrazzo - Unipex srl
2008-07-19 15:42 ` Jan Engelhardt
2008-07-19 16:05 ` Michele Petrazzo - Unipex srl
2008-07-19 16:13 ` Jan Engelhardt
2008-07-19 16:17 ` Leonardo Rodrigues Magalhães
2008-07-19 16:34 ` Jan Engelhardt
2008-07-19 16:45 ` Leonardo Rodrigues Magalhães
2008-07-19 15:11 ` Michele Petrazzo - Unipex srl
2008-07-20 23:41 ` Grant Taylor [this message]
2008-07-21 7:00 ` Anatoly Muliarski
2008-07-21 14:08 ` Grant Taylor
2008-07-21 18:11 ` Michele Petrazzo - Unipex srl
2008-07-21 19:46 ` Grant Taylor
2008-07-22 13:03 ` Anatoly Muliarski
2008-07-22 15:06 ` Grant Taylor
2008-07-22 15:20 ` Jan Engelhardt
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=4883CD35.3060704@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox