All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Glanzmann <thomas@glanzmann.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: gernoth@cs.fau.de, bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Packet reflection breaks Linux bridge
Date: Thu, 5 Dec 2013 18:27:51 +0100	[thread overview]
Message-ID: <20131205172751.GA9778@glanzmann.de> (raw)
In-Reply-To: <20131205090947.364e30d7@nehalam.linuxnetplumber.net>

Hello Stephan,

> Bridging doesn't like loops, and you have created a loop.

I agree. It was actually a Microsoft Load Balancing cluster that created
the loop. Michael told me that the physical switch works because it:

        a) broadcasts
        b) sends it to both ports.

> If you are goin to mess around using ebtables, just write another rule
> to drop the reflections.

Michael said that ebtables only after the bridge has seen the packets
and so is not applicable. Is that true? So should I use arptables. I
tried to block the looped packages by:

        - iptables
        - arptables
        - eptables

But somehow I never made it. Do you have an example for me or can tell
me which of the 3 tools should work, so that I can try again. The NATing
fought the symptoms of my problem.

Cheers,
        Thomas

  reply	other threads:[~2013-12-05 17:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30  8:54 [Bridge] Packet reflection breaks Linux bridge Thomas Glanzmann
2013-12-05 17:09 ` Stephen Hemminger
2013-12-05 17:27   ` Thomas Glanzmann [this message]
2013-12-05 17:31     ` Stephen Hemminger
2013-12-05 21:11 ` Bart De Schuymer
2013-12-06  4:33   ` Thomas Glanzmann

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=20131205172751.GA9778@glanzmann.de \
    --to=thomas@glanzmann.de \
    --cc=bridge@lists.linux-foundation.org \
    --cc=gernoth@cs.fau.de \
    --cc=stephen@networkplumber.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.