From: David Ahern <dsahern@gmail.com>
To: praveen chaudhary <praveen5582@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, corbet@lwn.net,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Zhenggen Xu <zxu@linkedin.com>
Subject: Re: [PATCH v2 net-next 1/1] Allow user to set metric on default route learned via Router Advertisement.
Date: Tue, 19 Jan 2021 21:22:40 -0700 [thread overview]
Message-ID: <7839be40-6555-3e5a-3459-c3f0e4726795@gmail.com> (raw)
In-Reply-To: <A2DE27CF-A988-4003-8A95-60CC101086DA@gmail.com>
On 1/19/21 3:17 PM, praveen chaudhary wrote:
>>> ----------------------------------------------------------------
>>> For IPv4:
>>> ----------------------------------------------------------------
>>>
>>> Config in etc/network/interfaces
>>> ----------------------------------------------------------------
>>> ```
>>> auto eth0
>>> iface eth0 inet dhcp
>>> metric 4261413864
>>
>> how does that work for IPv4? Is the metric passed to the dhclient and it
>> inserts the route with the given metric or is a dhclient script used to
>> replace the route after insert?
>>
>>
>
> Yes, DHCP client picks config under “iface eth0 inet dhcp” line and if metric is configured, then it adds the metric for all added routes.
As I recall ifupdown{2} forks dhclient as a process to handle dhcp
config, and I believe there is a script that handles adding the default
route with metric. Meaning ... it is not comparable to an RA.
>
> Thanks a lot again for spending time for this Review,
> This feature will help SONiC OS [and others Linux flavors] for better IPv6 support, so thanks again.
I think SONiC is an abomination, so that is definitely not the
motivation for my reviews. :-)
next prev parent reply other threads:[~2021-01-20 4:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 8:02 Praveen Chaudhary
2021-01-15 16:20 ` kernel test robot
2021-01-16 17:13 ` David Ahern
2021-01-19 22:17 ` praveen chaudhary
2021-01-20 4:22 ` David Ahern [this message]
2021-01-20 6:51 ` praveen chaudhary
2021-01-15 23:08 Praveen Chaudhary
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=7839be40-6555-3e5a-3459-c3f0e4726795@gmail.com \
--to=dsahern@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=praveen5582@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
--cc=zxu@linkedin.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
all inboxes | Powered by JetHome®