Re: using sysctl.conf to set hidden interfaces

To: Horms <horms@xxxxxxxxxxxx>
Subject: Re: using sysctl.conf to set hidden interfaces
Cc: Jeremy Hansen <jeremy@xxxxxxxxxxxx>, "lvs-users@xxxxxxxxxxxxxxxxxxxxxx" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: tc lewis <tcl@xxxxxxxxx>
Date: Mon, 19 Jun 2000 17:25:30 -0400 (EDT)

On Mon, 19 Jun 2000, Horms wrote:

> On Fri, Jun 16, 2000 at 08:05:25PM -0400, Jeremy Hansen wrote:
> > 
> > I've noticed that using rh's sysctl.conf (don't know if this is rh
> > specific) to set the sysctl parameters for hidden loopback interface for
> > direct method doesn't seem to really work for the loopback interface.  I
> > assume this is because sysctl is processed before the loopback interface
> > exists.  Is this the case.  Of course this isn't like a major deal, it's
> > just that in Ultramonkey docs it doesn't seem to mention this and it does
> > seem to rely on making these settings in sysctl.conf.
> Ouch.
> Can anyone (from RedHat) suggest how to configure interfaces
> using Red Hat style configuration files?


those should be brought up when the runlevel's "network" script is run on
redhat, if the files has an ONBOOT=yes.

or were you looking for more detail?  i'm not sure if those config files
support noarp options or stuff like that.

> In the mean time adding the following to /etc/rc.d/rc.local should help.
> sysctl -p /etc/sysctl.conf

action "Configuring kernel parameters" sysctl -p /etc/sysctl.conf

is already in redhat's rc.sysinit.
but rc.sysinit is executed before anything else--not sure if that would
cause problems.

(this is on rh6.2, at least).


<Prev in Thread] Current Thread [Next in Thread>