netdev - Re: /proc/sys/net/ipv[46]/conf/ issue unsolved

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9c46321e0702131124q33b4e263ybc38555cf1544769@mail.gmail.com>
Date:	Tue, 13 Feb 2007 19:24:32 +0000
From:	"Hugo Santos" <hugosantos@...il.com>
To:	"Neil Horman" <nhorman@...driver.com>
Cc:	"Hasso Tepper" <hasso@...pak.ee>, netdev@...r.kernel.org
Subject: Re: /proc/sys/net/ipv[46]/conf/ issue unsolved

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.

  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