From: David Ahern <dsahern@gmail.com>
To: Andrea Claudi <aclaudi@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>
Subject: Re: [PATCH iproute2 0/3] do not set IPv6-only options on IPv4 addresses
Date: Mon, 24 Jun 2019 15:51:06 -0600 [thread overview]
Message-ID: <c344be9c-2194-c138-4fe2-cfaeb5d44cec@gmail.com> (raw)
In-Reply-To: <CAPpH65wG9OXhEnXd2LrL0wQc9P4G7MKQjQ4bUTHN1CVqAc6bMg@mail.gmail.com>
On 6/24/19 3:38 PM, Andrea Claudi wrote:
> I think that if a script wrongly uses some of these flags on a IPv4
> address, it most probably operates on an unexpected address, since
> everyone is aware that these flags are IPv6 only. In other words we
> are breaking a scripted setup that is already broken.
> In this case it's probably worth exiting with error and give the
> author the chance to fix the script, otherwise the error can go
> unnoticed.
>
> If you prefer, I can send a v2 with warnings instead of errors, just
> let me know.
Recent changes for strict mode have shown people do interesting things
with scripts and like the silent "ignores". :-(
prev parent reply other threads:[~2019-06-24 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 17:05 [PATCH iproute2 0/3] do not set IPv6-only options on IPv4 addresses Andrea Claudi
2019-06-24 17:05 ` [PATCH iproute2 1/3] ip address: do not set nodad option for " Andrea Claudi
2019-06-24 17:05 ` [PATCH iproute2 2/3] ip address: do not set home " Andrea Claudi
2019-06-24 17:05 ` [PATCH iproute2 3/3] ip address: do not set mngtmpaddr " Andrea Claudi
2019-06-24 17:20 ` [PATCH iproute2 0/3] do not set IPv6-only options on " Stephen Hemminger
2019-06-24 21:38 ` Andrea Claudi
2019-06-24 21:51 ` 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=c344be9c-2194-c138-4fe2-cfaeb5d44cec@gmail.com \
--to=dsahern@gmail.com \
--cc=aclaudi@redhat.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.