All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Stolle" <alexlists@web.de>
To: bridge@lists.osdl.org
Subject: [Bridge] Problem with bond interface in bridge
Date: Mon, 18 Jul 2005 21:40:32 +0200	[thread overview]
Message-ID: <E1DubTc-0003tw-00@smtp08.web.de> (raw)
In-Reply-To: <200507111901.j6BJ09jC011023@smtp.osdl.org>

Hi @all,

I have a strange problem. Here is the setup: I have a bridging linux box
with 3 NICs (Intel e1000). 1 NIC (eth0) connected to the internet interface
and the other both (eth1 and eth2) are each connected to a different switch
in the bridged network.

I setup bonding (bond0) with active failover for eth1 and eth2. Then I added
eth0 and bond0 to br0 and brought it up with an ip. I am able to ping into
the internet and I can also ping servers in the bridged network from my
bridging linux box.

internet---bridging box---bridged network
		   br0
		eth0  bond0

But if I try to ping from the internet via the bridging box to the bridged
network, I get a "host not reachable". Looks like the bridge does not
forward anything. Has anybody ever had an equal problem or are there other
possible solutions for my setup? I have tried to add the 3 interfaces to the
br0, but this did not work either (amnd as far as I kniow there is no auto
failover for bridge ports).

Could someone please advise me or give me some tips, so that I can track
down the problem?
Thanks in advance :)

Best, Alex

Versions:
Dist debian sarge
Bonding Driver, v2.6.0
Kernel 2.4.31
bridge-utils, 1.0.4


       reply	other threads:[~2005-07-18 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200507111901.j6BJ09jC011023@smtp.osdl.org>
2005-07-18 19:40 ` Alexander Stolle [this message]
2005-07-19  5:23   ` [Bridge] Problem with bond interface in bridge Garik E

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=E1DubTc-0003tw-00@smtp08.web.de \
    --to=alexlists@web.de \
    --cc=bridge@lists.osdl.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.