From: David Ahern <dsahern@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: Fw: [Bug 204903] New: unable to create vrf interface when ipv6.disable=1
Date: Tue, 24 Sep 2019 20:28:52 -0600 [thread overview]
Message-ID: <a15f9952-e5ed-8358-e28d-6325bf4d5801@gmail.com> (raw)
In-Reply-To: <20190919104628.05d9f5ff@xps13>
On 9/19/19 2:46 AM, Stephen Hemminger wrote:
>
>
> Begin forwarded message:
>
> Date: Wed, 18 Sep 2019 15:15:42 +0000
> From: bugzilla-daemon@bugzilla.kernel.org
> To: stephen@networkplumber.org
> Subject: [Bug 204903] New: unable to create vrf interface when ipv6.disable=1
>
>
> https://bugzilla.kernel.org/show_bug.cgi?id=204903
>
> Bug ID: 204903
> Summary: unable to create vrf interface when ipv6.disable=1
> Product: Networking
> Version: 2.5
> Kernel Version: 5.2.14
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> Assignee: stephen@networkplumber.org
> Reporter: zhangyoufu@gmail.com
> Regression: No
>
> `ip link add vrf0 type vrf table 100` fails with EAFNOSUPPORT when boot with
> `ipv6.disable=1`. There must be somewhere inside `vrf_newlink` trying to use
> IPv6 without checking availablity. Maybe `vrf_add_fib_rules` I guess.
>
ack. I'll take a look when I get a chance. Should be a simple fix.
next prev parent reply other threads:[~2019-09-25 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 8:46 Fw: [Bug 204903] New: unable to create vrf interface when ipv6.disable=1 Stephen Hemminger
2019-09-25 2:28 ` David Ahern [this message]
2019-09-25 6:01 ` Michal Kubecek
2019-09-25 14:22 ` David Ahern
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=a15f9952-e5ed-8358-e28d-6325bf4d5801@gmail.com \
--to=dsahern@gmail.com \
--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.