[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190925060109.GG22507@unicorn.suse.cz>
Date: Wed, 25 Sep 2019 08:01:09 +0200
From: Michal Kubecek <mkubecek@...e.cz>
To: netdev@...r.kernel.org
Cc: David Ahern <dsahern@...il.com>,
Stephen Hemminger <stephen@...workplumber.org>
Subject: Re: Fw: [Bug 204903] New: unable to create vrf interface when
ipv6.disable=1
On Tue, Sep 24, 2019 at 08:28:52PM -0600, David Ahern wrote:
> 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@...zilla.kernel.org
> > To: stephen@...workplumber.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@...workplumber.org
> > Reporter: zhangyoufu@...il.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.
Not sure if it's the only problem but vrf_fib_rule() checks
ipv6_mod_enabled() for AF_INET6 but not for RTNL_FAMILY_IP6MR.
Michal
Powered by blists - more mailing lists