Re: sysctl, argument parsing, possible bug

2017-08-08 Thread Stephen Hemminger
On Tue, 8 Aug 2017 20:26:36 +0200 Massimo Sala wrote: > 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

Re: sysctl, argument parsing, possible bug

2017-08-08 Thread Stephen Hemminger
On Tue, 8 Aug 2017 20:26:36 +0200 Massimo Sala wrote: > 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

Re: sysctl, argument parsing, possible bug

2017-08-08 Thread Massimo Sala
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

Re: sysctl, argument parsing, possible bug

2017-08-08 Thread Massimo Sala
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

Re: sysctl, argument parsing, possible bug

2017-08-02 Thread Luis R. Rodriguez
On Tue, Aug 01, 2017 at 02:54:51PM -0700, Cong Wang wrote: > On Tue, Aug 1, 2017 at 2:34 PM, Massimo Sala > wrote: > > Do you confirm it is a sysctl parsing bug ? > > > > Bosybox handles these cases, so I think also standalone sysctl have to. > > > > Or at least

Re: sysctl, argument parsing, possible bug

2017-08-02 Thread Luis R. Rodriguez
On Tue, Aug 01, 2017 at 02:54:51PM -0700, Cong Wang wrote: > On Tue, Aug 1, 2017 at 2:34 PM, Massimo Sala > wrote: > > 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 /

Re: sysctl, argument parsing, possible bug

2017-08-01 Thread Stephen Hemminger
On Tue, 1 Aug 2017 14:27:37 -0700 Cong Wang wrote: > On Tue, Aug 1, 2017 at 1:47 PM, Massimo Sala > wrote: > > cat /proc/sys/net/ipv4/conf/eth0.100/forwarding > > 0 > > > > sysctl net.ipv4.conf.eth0.100.forwarding > > error:

Re: sysctl, argument parsing, possible bug

2017-08-01 Thread Stephen Hemminger
On Tue, 1 Aug 2017 14:27:37 -0700 Cong Wang wrote: > On Tue, Aug 1, 2017 at 1:47 PM, Massimo Sala > 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

Re: sysctl, argument parsing, possible bug

2017-08-01 Thread Cong Wang
On Tue, Aug 1, 2017 at 2:34 PM, Massimo Sala wrote: > 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. > Maybe, sysctl seems (I

Re: sysctl, argument parsing, possible bug

2017-08-01 Thread Cong Wang
On Tue, Aug 1, 2017 at 2:34 PM, Massimo Sala wrote: > 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. > Maybe, sysctl seems (I never look into it) just to

Re: sysctl, argument parsing, possible bug

2017-08-01 Thread Massimo Sala
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,

Re: sysctl, argument parsing, possible bug

2017-08-01 Thread Massimo Sala
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: >> cat

Re: sysctl, argument parsing, possible bug

2017-08-01 Thread Cong Wang
On Tue, Aug 1, 2017 at 1:47 PM, Massimo Sala 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

Re: sysctl, argument parsing, possible bug

2017-08-01 Thread Cong Wang
On Tue, Aug 1, 2017 at 1:47 PM, Massimo Sala 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.

sysctl, argument parsing, possible bug

2017-08-01 Thread Massimo Sala
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

sysctl, argument parsing, possible bug

2017-08-01 Thread Massimo Sala
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