wxman1
asked on
add 2nd network card
I need to put one of my Linux machines on 2 networks. It will need to have two different ips: 10.0.x.x and 192.168.X.X. I am running Redhat 8.0. I installed a second ethernet card (it is compatible w/ Linux accordinf to HOWTO). Now, I've booted the computer, and don't know what to do next. The original card is already configured properly. Both ethernet cards are differnt, therefore I am sure I need to do something with drivers, but don't know what. Then I would like to configure the 2nd ethernet card as eth1 but don't know how. The original card is eth0. Lastly, I am sure I need to edit etc/hosts, but don't know how?
Thanks in advance!
Brian
Thanks in advance!
Brian
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
paullamhkg
I changed ifcfg-eth1 as you said, with the correct settings. Now I probably need to edit the etc/hosts but I'm not sure how.
any suggestions?
I changed ifcfg-eth1 as you said, with the correct settings. Now I probably need to edit the etc/hosts but I'm not sure how.
any suggestions?
NAME
hosts - The static table lookup for host names
SYNOPSIS
/etc/hosts
DESCRIPTION
This manual page describes the format of the /etc/hosts file. This file
is a simple text file that associates IP addresses with hostnames, one
line per IP address. For each host a single line should be present with
the following information:
IP_address canonical_hostname aliases
Fields of the entry are separated by any number of blanks and/or tab
characters. Text from a "#" character until the end of the line is a
comment, and is ignored. Host names may contain only alphanumeric
characters, minus signs ("-"), and periods ("."). They must begin with
an alphabetic character and end with an alphanumeric character.
Aliases provide for name changes, alternate spellings, shorter host-
names, or generic hostnames (for example, localhost). The format of
the host table is described in RFC 952.
The Berkeley Internet Name Domain (BIND) Server implements the Internet
name server for UNIX systems. It augments or replaces the /etc/hosts
file or host name lookup, and frees a host from relying on /etc/hosts
being up to date and complete.
In modern systems, even though the host table has been superseded by
DNS, it is still widely used for:
bootstrapping
Most systems have a small host table containing the name and
address information for important hosts on the local network.
This is useful when DNS is not running, for example during sys-
tem bootup.
NIS Sites that use NIS use the host table as input to the NIS host
database. Even though NIS can be used with DNS, most NIS sites
still use the host table with an entry for all local hosts as a
backup.
isolated nodes
Very small sites that are isolated from the network use the host
table instead of DNS. If the local information rarely changes,
and the network is not connected to the Internet, DNS offers
little advantage.
EXAMPLE
127.0.0.1 localhost
192.168.1.10 foo.mydomain.org foo
192.168.1.13 bar.mydomain.org bar
216.234.231.5 master.debian.org master
205.230.163.103 www.opensource.org
The above is the man page of /etc/hosts so you can have some idea.
can you tell us what you are planning to do with your 2 NIC linux, so that we can more specify.
hosts - The static table lookup for host names
SYNOPSIS
/etc/hosts
DESCRIPTION
This manual page describes the format of the /etc/hosts file. This file
is a simple text file that associates IP addresses with hostnames, one
line per IP address. For each host a single line should be present with
the following information:
IP_address canonical_hostname aliases
Fields of the entry are separated by any number of blanks and/or tab
characters. Text from a "#" character until the end of the line is a
comment, and is ignored. Host names may contain only alphanumeric
characters, minus signs ("-"), and periods ("."). They must begin with
an alphabetic character and end with an alphanumeric character.
Aliases provide for name changes, alternate spellings, shorter host-
names, or generic hostnames (for example, localhost). The format of
the host table is described in RFC 952.
The Berkeley Internet Name Domain (BIND) Server implements the Internet
name server for UNIX systems. It augments or replaces the /etc/hosts
file or host name lookup, and frees a host from relying on /etc/hosts
being up to date and complete.
In modern systems, even though the host table has been superseded by
DNS, it is still widely used for:
bootstrapping
Most systems have a small host table containing the name and
address information for important hosts on the local network.
This is useful when DNS is not running, for example during sys-
tem bootup.
NIS Sites that use NIS use the host table as input to the NIS host
database. Even though NIS can be used with DNS, most NIS sites
still use the host table with an entry for all local hosts as a
backup.
isolated nodes
Very small sites that are isolated from the network use the host
table instead of DNS. If the local information rarely changes,
and the network is not connected to the Internet, DNS offers
little advantage.
EXAMPLE
127.0.0.1 localhost
192.168.1.10 foo.mydomain.org foo
192.168.1.13 bar.mydomain.org bar
216.234.231.5 master.debian.org master
205.230.163.103 www.opensource.org
The above is the man page of /etc/hosts so you can have some idea.
can you tell us what you are planning to do with your 2 NIC linux, so that we can more specify.
ASKER
This is what I am trying to do:
The original card will continue to be used as it has been. It connects the Linux PC to our LAN. It needs to be connected to our LAN, and it uses Samba to communicate with the Windows Computers that are on the LAN.
I put the 2nd card in the Linux PC because we have data that is transmitted to us via satellite. This data comes into a satellite modem, which in turn changes the data format to TCP/IP then broadcasts the data to a proprietary ip address inherant to the satellite modem. Because the satellite modem is looking for a particular ip address that does not conform to our LAN, I thought this would be the best way to go.
The original card will continue to be used as it has been. It connects the Linux PC to our LAN. It needs to be connected to our LAN, and it uses Samba to communicate with the Windows Computers that are on the LAN.
I put the 2nd card in the Linux PC because we have data that is transmitted to us via satellite. This data comes into a satellite modem, which in turn changes the data format to TCP/IP then broadcasts the data to a proprietary ip address inherant to the satellite modem. Because the satellite modem is looking for a particular ip address that does not conform to our LAN, I thought this would be the best way to go.
ASKER
thanks for your help. everything is working now!
Chapter 11. Network Configuration
http://www.redhat.com/docs/manuals/linux/RHL-8.0-Manual/custom-guide/ch-network-config.html