Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Cihangir Akturk <cakturk@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridge forwards ARP packets but not forwards IP datagrams
Date: Sun, 1 Jan 2017 10:22:22 -0800	[thread overview]
Message-ID: <20170101102222.3d34c6ab@xeon-e3> (raw)
In-Reply-To: <20170101153749.GA1639@mbp>

On Sun, 1 Jan 2017 18:37:49 +0300
Cihangir Akturk <cakturk@gmail.com> wrote:

> Now the problem I am experiencing is that br0 bridge forwards ARP
> packets but not IP datagrams when they are sent from the host box.
> When I say "host box", I mean the machine on which my test VM runs.
> It seems that ARP packets are forwarded no matter which host (host
> or guest box) they come from. But when it comes to IP datagrams,
> they are forwarded to tap0 as expected if I send them from the same
> host as tap0 interface (guest VM). If I send them from the host
> box (I mean the computer on which my VM runs), IP datagrams reach
> br0 bridge, but somehow they are not forwarded to tap0 interface,
> I can see this with tcpdump.
> 
> I know the bridging functionality is independent of layer 3
> protocols, and it should forward packets according to their layer
> 2 addresses, in this case their mac addresses.


Short answer. It looks like you put an IP address on one of the devices
enslaved into the bridge.  Because of how the kernel L3 stack works you need
to only put IP addresses on the bridge device and not the underlying Ethernet
device. The only exception is if you are doing tricky things with brouting
in iptables.

      reply	other threads:[~2017-01-01 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01 15:37 [Bridge] Bridge forwards ARP packets but not forwards IP datagrams Cihangir Akturk
2017-01-01 18:22 ` Stephen Hemminger [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=20170101102222.3d34c6ab@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=cakturk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox