What Files need to be edited and how to make an IP come up automatically on a reboot

I have a lot of IP's aliased on my server, the last two and most recent I have learned how to do myself, however the IP does not stay live if the server goes thru a reboot, I have to rerun ifconfig and route add, I already edited the file in /etc/rc.d to include the new routes and IPs but apparently there is another file somewhere that needs something added for the startup to bring these last two live... can anyone steer me in the right direction please?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you run RedHat 4.0 or higher, the answer is simple. Go to /etc/rc.d/sysconfig/network-scripts, use your ifcfg-eth0 as a skeleton to create ifcfg-eth0:0 , ifcfg-eth0:1 and as many ifcfg-ethx:n as you need for the "lot" of aliased addresses that you have. :) Edit then /etc/sysconfig/static-routes to add all the static routes that you need (use the ones already defined as an example). They will come up at boot.

If you run a Slackware system .. I don't know. I guess you gotta recursively grep the files in /etc for ifconfig commands and add _your_ commands next to them. You can also reject the answer, maybe someone more familiar with Slackware shows up. O:-)

lorenkiaAuthor Commented:
this is a slackware linux system with kernel 2.0.30 and yes I need someone familar with slackware  :) thanks anyway XMS

On slackware, the initial network setup is done form the file

I've made a seperate file with all the ifconfig and route add stuff, made it executable, and made rc.inet1 call this file.
Ofcours, this is not really necesary (sp?), but it keeps things

Check your /etc/rc.d/rc/inet1 for ifconfig commands (besides the one used to configure your primary IP), or for calls to some other file that may do the job.

Learn SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

lorenkiaAuthor Commented:
yes I put the lines in the rc.inet1 like I see the other ones there, and I know I saved the file but it did not ifconfig the last two IPs in the list, like it did the others so I thought there might be another file on the system somewhere? I was also told to go to rc.local but I am not sure what to put in rc.local as I do not see any entries there for the ifconfig stuff, just my quota stuff...??? it has to be really simple and I am missing it *grin*
Since you're aliasing the IP's you proabably need to use insmod to load the aliasing module before you setup any of your IP's.
With slackware I'd do it in the top or rc.inet1.

The aliasing module needs to be loaded first, befire you ifconfig
the alias IP's.

The doc for the alias module says you have to load it manually not rely on kerneld to load it automagically.

Either that or put the ifconfig commands in the rc.local script. That one gets run last, after the rest of the system is up. That's what I do for my masquerade server. I also manualy load the ailas module in rc.local too.


The answer to this is that the rc files are right.

What you have forgotten to do is add the entries to dns for the subdomains.

Check out /var/named/pz/kia-sequoia.com for the file you need to edit. Then kill -HUP named to fix this.

PS - It's Jason here!!!!
lorenkiaAuthor Commented:
HI Jason!! um, been there done that NEXT? *grin* hey when I got a question I really give you all a stumper don't I? LOL

i guess the best solution to your problem is to edit or view all the files off your rc.d directory and see if you can find the one that starts your deamon on bootup. Move youre routes to that section and then reboot. This should fix up your problem



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.