[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKv20-VFcdZti=4a6QzVJH0wAYGpqo2umktRPr19tv+btSZY_w@mail.gmail.com>
Date: Tue, 1 Aug 2017 23:34:09 +0200
From: Massimo Sala <massimo.sala.71@...il.com>
To: Cong Wang <xiyou.wangcong@...il.com>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
Kees Cook <keescook@...omium.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: sysctl, argument parsing, possible bug
Do you confirm it is a sysctl parsing bug ?
Bosybox handles these cases, so I think also standalone sysctl have to.
Or at least someone must update sysctl docs / MAN about this.
Best regards, Sala
On 01/08/2017, Cong Wang <xiyou.wangcong@...il.com> wrote:
> On Tue, Aug 1, 2017 at 1:47 PM, Massimo Sala <massimo.sala.71@...il.com>
> wrote:
>> cat /proc/sys/net/ipv4/conf/eth0.100/forwarding
>> 0
>>
>> sysctl net.ipv4.conf.eth0.100.forwarding
>> error: "net.ipv4.conf.eth0.100.forwarding" is an unknown key
>>
>
> Use echo instead, sysctl doesn't understand eth0.100
> is a netdev name, sigh.
>
Powered by blists - more mailing lists