I make another test with kernel 4.9.32-15.41
sysctl procps version 3.2.8
sysctl net.ipv4.conf.eth0.100.forwarding
error: "net.ipv4.conf.eth0.100.forwarding" is an unknown key
so I install busybox :
BusyBox v1.19.3
busybox sysctl net.ipv4.conf.eth0.100.forwarding
net.ipv4.conf.
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
uname -a
Linux ip-172-31-45-203 4.9.38-16.33.amzn1.x86_64 #1 SMP Thu Jul 20
01:31:29 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/issue
Amaz
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 wrote:
> On Tue, Aug 1, 2017 at 1:47 PM, Massimo Sala
> wrote:
3 matches
Mail list logo