From: David Ahern <dsahern@gmail.com>
To: Henry Shen <henry.shen@alliedtelesis.co.nz>, davem@davemloft.net
Cc: yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
chris.packham@alliedtelesis.co.nz
Subject: Re: [PATCH] net:ipv4: Packet is not forwarded if bc_forwarding not configured on ingress interface
Date: Sun, 28 Feb 2021 20:20:38 -0700 [thread overview]
Message-ID: <32dc320d-abb0-475d-ca94-bac3bd26f825@gmail.com> (raw)
In-Reply-To: <20210301005318.8959-2-henry.shen@alliedtelesis.co.nz>
On 2/28/21 5:53 PM, Henry Shen wrote:
> When an IPv4 packet with a destination address of broadcast is received
> on an ingress interface, it will not be forwarded out of the egress
> interface if the ingress interface is not configured with bc_forwarding
> but the egress interface is. If both the ingress and egress interfaces
> are configured with bc_forwarding, the packet can be forwarded
> successfully.
>
> This patch is to be inline with Cisco's implementation that packet can be
> forwarded if ingress interface is NOT configured with bc_forwarding,
> but egress interface is.
>
In Linux, forwarding decisions are made based on the ingress device, not
the egress device.
prev parent reply other threads:[~2021-03-01 3:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 0:53 [PATCH] net:ipv4: Packet is not forwarded when ingress interface is not configured with bc_forwarding Henry Shen
2021-03-01 0:53 ` [PATCH] net:ipv4: Packet is not forwarded if bc_forwarding not configured on ingress interface Henry Shen
2021-03-01 3:20 ` David Ahern [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=32dc320d-abb0-475d-ca94-bac3bd26f825@gmail.com \
--to=dsahern@gmail.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=henry.shen@alliedtelesis.co.nz \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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