[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG-2HqWeJKbipVm+1oxKQYQfFyqu4SdSH15BP-4OAaUbJBCVdg@mail.gmail.com>
Date: Thu, 15 May 2014 23:42:58 +0200
From: Tom Gundersen <teg@...m.no>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Patrick McHardy <kaber@...sh.net>, yoshfuji@...ux-ipv6.org,
jmorris@...ei.org, Alexey Kuznetsov <kuznet@....inr.ac.ru>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH] net: tunnels - enable module autoloading
On Thu, May 15, 2014 at 11:32 PM, Stephen Hemminger
<stephen@...workplumber.org> wrote:
> On Tue, 13 May 2014 10:48:28 +0200
> Tom Gundersen <teg@...m.no> wrote:
>
>> Enable the module alias hookup to allow tunnel modules to be autoloaded on demand.
>>
>> This is in line with how most other netdev kinds work, and will allow userspace
>> to create tunnels without having CAP_SYS_MODULE.
>>
>> Signed-off-by: Tom Gundersen <teg@...m.no>
>> Tested-by: Susant Sahani <susant@...hat.com>
>> ---
>> net/ipv4/ipip.c | 1 +
>> net/ipv6/ip6_tunnel.c | 1 +
>> net/ipv6/sit.c | 1 +
>> 3 files changed, 3 insertions(+)
>
> But tunnel modules are autoloaded now.
> If I create a tunnel with ip tunnel based on the existing MODULE_ALIAS_NETDEV().
Hm, please correct me if I'm wrong, but this only works if you create
a tunnel with one of the hardcoded tunnel names, right? And also, if I
read the code correctly, it only works if you use the ioctl interface
and not the rtnl interface?
What we'd like to do is to use the rtnl interface to create tunnels
with arbitrary names, is there a way this can already be done that I
have missed?
Cheers,
Tom
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists