[LUAU] ip alias

Seth Rightmer spun at lava.net
Thu Feb 4 17:53:27 PST 1999


On Thu, 4 Feb 1999, David C Eason Jr wrote:

> I have a question, I've set up IP aliasing for my slackware box, I know
> I've done it right (by right I mean its working so there :)) but I can't
> get it to re-issue those commands on boot.  I've added them to rc.local
> but when I reboot all the aliased ips don't work.  Any ideas?

When in the boot process is rc.local being run?  I'm not familiar with
slackware's init & rc setup, but look in /etc/inittab to see what script
is run to control startup, then check in that script to see when rc.local
is run. If the commands work after bootup is complete, they will surely
work if rc.local executes after all other initialization steps complete.

Also, from this process, you can tell whether slackware even runs
rc.local, and if so, where it expects it to be.  Make sure this is
correct.

Check that rc.local is executable.

If slackware uses the Sys V init process, there will be seperate rc.X
directories for each runlevel.  You could put all your ip aliasing into a
file in /etc/init.d (or /etc/rc/init.d/ or whatever) and then link to them
with S99ipalias in the appropriate rc.X directory.  That way, you can set
up some runlevels without IP aliasing, for maintenance purposes. 

If it uses a simpler (and, need I say faster) single script system, you
might need to rewrite the script.

Another neat trick is to use the logger command to add lines like
"Starting IP aliasing" to your system logs.  Makes figuring out what's
going wrong easier. And if you use lines like "start_ipaliasing&&logger
-p daemon.warn -t IPALIAS "could not start ip aliasing" then, if any of
the lines in your script fail to execute, you'll know. (Just replace the
start_ipaliasing with whatever command you would regularly use, I've never
set it up so I don't know)




More information about the LUAU mailing list