| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20070213194538.GF25362@hmsreliant.homelinux.net> Date: Tue, 13 Feb 2007 14:45:38 -0500 From: Neil Horman <nhorman@...driver.com> To: Hugo Santos <hugosantos@...il.com> Cc: Hasso Tepper <hasso@...pak.ee>, netdev@...r.kernel.org Subject: Re: /proc/sys/net/ipv[46]/conf/ issue unsolved On Tue, Feb 13, 2007 at 07:24:32PM +0000, Hugo Santos wrote: > Neil, > > On 2/13/07, Neil Horman <nhorman@...driver.com> wrote: > >Can't this simply be fixed by adding a custom udev rule? Correct me if I'm > >wrong, but the only reason that interfaces come up automatically after > >their > >appropriate module is inserted is because most distos udev rules issue an > >ifup > >$DEVICE when they get a creation event for $DEVICE. Why not add a custom > >rule > >in for net device creation events to set appropriate sysctl values before > >the > >ifup is issued. > > The issue is not as much with automatic auto-configuration but with > not being able to disable auto-configuration (and others) before > setting the interface up. > Yes, I understand that, but until the IFF_UP flag is set on the interface, it doesn't really have any effect on the system as a whole. You should be able to undo any default setting that you want before you call ifup on the interface, or am I missing something? Neil > Hugo - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists