From: Ido Schimmel <idosch@idosch.org>
To: Nayan Gadre <beejoy.nayan@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Routing in case of GRE interface under a bridge
Date: Thu, 29 Jun 2023 14:12:35 +0300 [thread overview]
Message-ID: <ZJ1nIzt6IE0DSPKs@shredder> (raw)
In-Reply-To: <CABTgHBsEfgr8wQNF-YGR9mWMOb3bSESRdO4YVL+8+V6VA-PVuw@mail.gmail.com>
On Wed, Jun 28, 2023 at 07:06:45PM +0530, Nayan Gadre wrote:
> I have a "l2gre0" and "eth0" interface under the bridge "br0".
I assume "l2gre0" is a gretap, not ipgre.
> If a packet comes to eth0 interface with a destination IP address say
> 10.10.10.1 which is not known on the Linux system, as there is no
> route for 10.10.10.1, will the l2gre0 interface encapsulate this
> packet and send it across the tunnel ?
The bridge doesn't care about IP addresses when forwarding unicast
packets. Forwarding happens based on DMAC. Packet will be transmitted
through "l2gre0" if the bridge has a matching FDB entry for the DMAC
with "l2gre0" as the destination bridge port or if there is no FDB entry
at all, in which case the packet will be flooded.
One of the attributes of the GRE device is the remote address, which is
the encapsulating destination IP. Linux needs to have a route telling it
how to reach this destination address or the packet will be dropped.
> The other endpoint is on a different Linux system with another l2gre0
> interface having IP address 10.10.10.1
>
> Thanks
> N Gadre
>
next prev parent reply other threads:[~2023-06-29 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 13:36 Routing in case of GRE interface under a bridge Nayan Gadre
2023-06-29 11:12 ` Ido Schimmel [this message]
2023-06-29 15:30 ` Nayan Gadre
2023-06-29 15:37 ` Nayan Gadre
2023-06-29 16:59 ` Ido Schimmel
2023-07-03 5:44 ` Nayan Gadre
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=ZJ1nIzt6IE0DSPKs@shredder \
--to=idosch@idosch.org \
--cc=beejoy.nayan@gmail.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox