From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: More ethernet port same ip address
Date: Mon, 21 Jul 2008 14:46:42 -0500 [thread overview]
Message-ID: <4884E7A2.5070403@riverviewtech.net> (raw)
In-Reply-To: <4884D160.7060701@unipex.it>
On 07/21/08 13:11, Michele Petrazzo - Unipex srl wrote:
> made some tries and I see that it works well with the "bridge" mode.
> The only thing that I do was to to create a new bridge, remove the ip
> address from the interfaces, add them to the bridge and set an ip
> address for the bridge. Nothing other. With arp_proxy 1 or 0 it works
> in the same manner.
*nod*
> The strange it's that I already tried this solution in test room, but
> I remember that it didn't work. One think that forgot to say it's
> that when I tried, I was using a different switch configuration (that
> now I cannot reproduce): there was two different switch (with stp
> enabled and configured), each one with 3 different vlan and each of
> the three vlans end into one server ethernet port.
VLANs and especially STP make things more interesting.
> Here, for make the communication working, I have to setup the three
> vlan(s) on the server port's, but they must have the same address.
> And, with the "bridge" solution I think that I cannot.
With traditional bridging, you would bridge the three (virtual)
interfaces together and then bind your server's IP(s) to the bridge
interface. I've got a system in service that has an excess of 24
different VLAN interfaces bridged together, and it's working great.
> Thanks to all,
*nod*
Grant. . . .
next prev parent reply other threads:[~2008-07-21 19:46 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
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 [this message]
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=4884E7A2.5070403@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 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.