Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 11-28-2007, 09:36 PM   #1
LQ Newbie
Registered: Oct 2007
Distribution: CentOS 4.x
Posts: 12

Rep: Reputation: 0
Inquiries about eht0 and eht0:1


my /etc/sysconfig/network-scripts/eht0 is :

i wanted to add an ip to my linux server and i completely replicated the above file by the name of eth0:1 and only changed the


I have these questions:

  1. What are ONBOOT and BOOTPROTO ?
  2. And do I need to include them in eth0:1 ?
  3. And is this a problem if i have started configuring new ip from eth0:1 and not from eth0:0?

Last edited by thok; 11-28-2007 at 09:38 PM.
Old 11-28-2007, 10:57 PM   #2
Registered: Nov 2006
Location: Seattle, WA
Distribution: Fedora
Posts: 407

Rep: Reputation: 35
To answer your questions specifically:

1a. ONBOOT determines whether the interface is started when the system comes up (not strictly onBoot, but rather when you or your scripts say "network start"); the answers are "yes" or "no".

1b. BOOTPROTO determines how the interface acquires its IP address when it comes up. The choices are "static", "bootp", or "dhcp". The only two that are actually used much these days are "static", which means that you put the IP address in the config file, and "dhcp", which means that the IP address is handed out by a DHCP server somewhere on your network. That is handy for laptops and other machines that can't or won't handle fixed IP addresses.

2. If you want the virtual interface to come up and have an IP address, you need to include these parameters in the ifcfg-eth0:1 file.

3. You are allowed to name the virtual interface with any number after the colon.

There remains the question of why you want to do what you describe in the first place. If your ISP is supplying you with several IP addresses, it could be reasonable to try to set up your system to respond to them all. But if you are trying to overlay a (private) network on the same wires that face the public network, this is a *bad idea*. It would be much better to buy a second ethernet interface for your server, and keep the private network separate from the public Internet.
Old 11-29-2007, 05:12 AM   #3
LQ Newbie
Registered: Oct 2007
Distribution: CentOS 4.x
Posts: 12

Original Poster
Rep: Reputation: 0
no actually this is a web server and so it will be a public network. I need to setup multiple ips address on the webserver.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Redhat 9 eht0 fails on boot Hook99 Linux - Newbie 1 01-18-2005 06:19 AM
DHCP using eth1 for internet eht0 for router... Zero-0-Effect Linux - Networking 12 01-17-2004 04:06 PM
eht0 vs eth1 conflict CatSC Linux - Networking 7 01-04-2004 03:11 PM
changing eht0 with eth1 slano Linux - Networking 2 12-11-2003 05:13 PM
lag on eht0 activation CultFigure Linux - Networking 3 01-13-2003 02:04 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 11:18 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration