From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Chinmay Agarwal <chinagar@qti.qualcomm.com>
Cc: "Kernelnewbies@kernelnewbies.org" <Kernelnewbies@kernelnewbies.org>
Subject: Re: Understanding the working of Optimistic DAD Feature.
Date: Thu, 06 Feb 2020 12:12:42 -0500 [thread overview]
Message-ID: <291438.1581009162@turing-police> (raw)
In-Reply-To: <DM6PR02MB47791D09F641777AFAC0FA8BEB1D0@DM6PR02MB4779.namprd02.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 888 bytes --]
On Thu, 06 Feb 2020 12:19:26 +0000, Chinmay Agarwal said:
> To check the same there is a condition in kernel code wherein we check if ipv6.devconf_all is set.
> Now, my query is that we are checking if forwarding is enabled on all interfaces, then we consider the system to be a router.
> But even if forwarding is enabled from few interfaces(not all) isn't the system behaving like a router?
You can't actually configure "routing on some but not all" without setting the
global forwarding bit.
If you have the very odd use case where you have eth0, eth1, and eth2, and
you're routing between eth0 and eth1, but eth2 is a private net that should
*not* communicate with either eth0 or eth1, the way you configure that is to
turn on the global forwarding bit, and then use a combo of routing table and
firewall rules to prevent traffic going to eth2 unless it's from the local
host.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-02-06 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 12:19 Understanding the working of Optimistic DAD Feature Chinmay Agarwal
2020-02-06 17:12 ` Valdis Klētnieks [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=291438.1581009162@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=chinagar@qti.qualcomm.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;
as well as URLs for NNTP newsgroup(s).