Re: [patch net-next 3/5] ipv6: consider net.ipv6.conf.all sysctls when making decisions

2014-06-12 Thread Milos Vyletel
g conf.all.* altogether since it's no-op and pretty confusing for users (myself included). Milos On Wed, Jun 11, 2014 at 6:32 PM, David Miller wrote: > From: Milos Vyletel > Date: Tue, 10 Jun 2014 13:49:35 -0400 > >> On Tue, Jun 10, 2014 at 1:13 PM, Stephen Hemminger >> wrote: &g

Re: [patch net-next 3/5] ipv6: consider net.ipv6.conf.all sysctls when making decisions

2014-06-10 Thread Milos Vyletel
On Tue, Jun 10, 2014 at 1:13 PM, Stephen Hemminger wrote: > On Tue, 10 Jun 2014 12:19:11 -0400 > Milos Vyletel wrote: > >> As it is right now net.ipv6.conf.all.* are mostly ignored and instead >> we're only making decisions based on interface specific settings. These &g

Re: [patch net-next 3/5] ipv6: consider net.ipv6.conf.all sysctls when making decisions

2014-06-10 Thread Milos Vyletel
> Hello, > >> >> IN6_DEV_MAXCONF >> IN6_DEV_HOPLIMIT >> IN6_DEV_MTU > > I'm a little bit surprise to set the MTU as the maximum of all/dev > value. Since the default for "all" is IPV6_MIN_MTU, it is probably > harmless, but it could be a little bit surprising for administrators. > >> I