Not quite sure how Red Hat does these things but there ought to be some sort of a configuration file (somewhere in
/etc) named something like
inet1.conf, that file contains the configuration settings for your network interfaces (thus the "inet" name).
For fixed-IP; i.e., you're assigned an address, entries in that file should look something like this:
Code:
# Config information for eth0:
IPADDR[0]="192.168.1.10"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
GATEWAY="192.168.1.1"
In the above, the system address is 192.168.1.10, NETMASK is 255.255.255.0, not using DHCP (you don't use DHCP for fixed-IP addressing), and the GATEWAY is 192.168.1.1 (that's the address of the router the machine is connected to). Yours may, of course, vary.
This particular server is named "fubar.com" and, if that name and domain is not already
/etc/hosts, you would add a line in
/etc/hosts like this:
Code:
127.0.0.1 localhost
192.168.1.10 fubar.com fubar
This is to identify the server by name; that name and domain would also appear in
/etc/HOSTNAME.
Note that, if you're using DHCP for other purposes you can used fixed-IP for the server -- just set the address at a lower number than the starting addresses DHCP uses. In many cases, DHCP starts at xxx.xxx.x.100 and increment from there, so xxx.xxx.x.10 is just fine.
Using fixed-IP for server addresses is advantageous -- you always know what the address is and the server will be known to your intranet by name (you can fiddle with DCHP settings to make that happen as well, but why fiddle around when you don't have to).
If you add any of these to
inet1.conf, you will need to restart you network services; or simply reboot the server.
Hope this helps some.
