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 v1
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.
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 /
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 e
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 inte
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
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.