All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Petri Gynther <petri.gynther@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: How to hairpin two Ethernet interfaces together (L2 hub/repeater mode)?
Date: Mon, 25 Feb 2013 14:16:53 -0500	[thread overview]
Message-ID: <512BB8A5.60103@mojatatu.com> (raw)
In-Reply-To: <CAKuTDr_eC4Wrv=uGthGJk3Zps=fnyAxpqqmsSDau7ZLs4PGyZw@mail.gmail.com>


Look at tc action redirect. Add it to ingress of eth0 to match 
everything and send out on eth1.

cheers,
jamal


On 13-02-22 07:10 PM, Petri Gynther wrote:
> Hi netdev:
>
> I'd like to hairpin two Ethernet interfaces together (e.g. eth0 and
> eth1) so that any frame received on eth0 is forwarded as-is to eth1
> and vice versa.
>
> Does Linux networking code support this? I've looked at the bridging
> code, but it doesn't seem to do this (at least trivially).
> Specifically, when eth0 and eth1 are added to bridge, unicast frames
> destined to eth0 (or eth1) MAC address end up to the bridge interface
> for local consumption, rather than being flooded to other ports on the
> bridge.
>
> Any trivial solutions to this? Can Linux bridge be configured in L2
> hub/repeater mode so that it simply floods every Rx frame to all other
> ports of the bridge?
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      parent reply	other threads:[~2013-02-25 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-23  0:10 How to hairpin two Ethernet interfaces together (L2 hub/repeater mode)? Petri Gynther
2013-02-23  1:42 ` Hannes Frederic Sowa
2013-02-25 19:16 ` Jamal Hadi Salim [this message]

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=512BB8A5.60103@mojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=petri.gynther@gmail.com \
    /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.