Configure local NIC

Introduction:

This procedure goes through configuring and testing an internal netwirk card.

Aim:

A configured Ethernet card that connects the server to the local (internal) network. This also names the server and establishes the domain name for your network.

Requirement:

Base Fedora Core 4 is installed.
You will need to invent three things:

1. The IP Address of your server. This should be taken from the Private IP Address range assigned to small networks - a.k.a. the 256*Class C Range. These are numbered; 192.168.0.0 - 192.168.255.255. I will use only two, one for the server (192.169.0.2) and one for the PC (192.169.0.3) (later,when I get around to connecting the network up).
2. Your domain name. For your network to work as a single entity, it needs a domain name. If you were a company, you - or marketing, god help us - would have made up something and, assuming that no-one else has already registered it, would use it publically and, in all likelihood, on your internal network, too. We, however, don't really need to register a name, unless, of course, we want to. As whichever name you choose will only be visible to your internal network it can be whatever you like. However, you don't really want something really famous - google.com, for example - because, if you do, you might mislead your net applications as to where services are available. I have chosen steveroach.org.
3. Your server name (a.k.a. alias): This can really be anything you like. Most people choose some variation on a theme for small networks. I have chosen "lisa" for my Linux server, and "homer" for my Windoze PC which, I reckon, is pretty appropriate.
   

NOTE: A full computer name looks like this: computer_name.domain_name. In my case, my server (lisa) full name is lisa.steveroach.org, and my PC (homer) full name is homer.steveroach.org.

Procedure:

• Log in as root
• -Applications-
• -System Tools-
• -Internet Configuration Wizard-
• Select Device Type:
• -Ethernet connection- [Forward]
• Select Ethernet Device:
  
• -Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (eth1)- [Forward]
• Configure Network Settings:
• Statically set IP addresses. (If you're not sure what to do here or you want to know why I'm using these particular settings, read the 'Requirement' section at the top of this post.)
• Address: 192.168.0.2
• Subnet mask: 255.255.255.0
• [Next]
  
• [Apply]
• Network Configuration:
  
• -Devices-
• -Inactive eth1 eth1 Ethernet-
• [Activate]
• Question: [Yes]
• Information: [OK]
• The device becomes active.
  
• Close Network Configuration window.

Testing:

• Check that you can ping yourself by alias and IP:
• Open Terminal
• # ping 192.168.0.2
• You should see something like this (this will run forever unless you stop it (type Ctrl-C to stop the display):

[root@localhost ~]# ping 192.168.0.2 PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data. 64 bytes from 192.168.0.2: icpm_seq=0 ttl=64 time=0.050 ms 64 bytes from 192.168.0.2: icpm_seq=1 ttl=64 time=0.042 ms 64 bytes from 192.168.0.2: icpm_seq=2 ttl=64 time=0.042 ms 64 bytes from 192.168.0.2: icpm_seq=3 ttl=64 time=0.043 ms 64 bytes from 192.168.0.2: icpm_seq=4 ttl=64 time=0.043 ms --- 192.168.0.2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3998ms rtt min/avg/max/mdev = 0.042/0.044/0.045/0.003 ms, pipe 2 [root@localhost ~]#

• # ping lisa
• You should see something like this:

[root@localhost ~]# ping lisa PING lisa.steveroach.org (192.168.0.2) 56(84) bytes of data. 64 bytes from lisa.steveroach.org (192.168.0.2): icmp_seq=0 ttl=64 time=0.051 ms 64 bytes from lisa.steveroach.org (192.168.0.2): icmp_seq=1 ttl=64 time=0.044 ms 64 bytes from lisa.steveroach.org (192.168.0.2): icmp_seq=2 ttl=64 time=0.044 ms 64 bytes from lisa.steveroach.org (192.168.0.2): icmp_seq=3 ttl=64 time=0.044 ms 64 bytes from lisa.steveroach.org (192.168.0.2): icmp_seq=4 ttl=64 time=0.043 ms --- lisa.steveroach.org ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3998ms rtt min/avg/max/mdev = 0.043/0.045/0.051/0.005 ms, pipe 2 [root@localhost ~]#

• Check that the server name is set:
• Close all windows and reboot.
• On the detailed process-start list, you should see: Bringing up interface eth1 [ OK ] (eth0 won't work if the ADSL cable is not plugged in to the server. That's fine for this test.)
  
• On the left-hand bottom of the login screen the server name should be: lisa.steveroach.org

It is a VERY good idea that you check inter-connectivity at this stage. Any problems with this bit; go here:

• The PC (Note your network settings as you do this. You will be putting them back later.):
• -Start-
• -My Network Places-
• -View Network Connections-
• Right-click; -Local Area Connection-
• -Properties-
• From the list; 'This connection uses the following items:', highlight -Internet Protocol (TCP/IP)-
• -Properties-
• Take a note of all IP addresses here.
• Use the following IP address:
• IP address: 192.168.0.3
• Subnet mask: 255.255.255.0
• Defauly gateway: 192.168.0.2
  
• Disconnect the cable from the ADSL Modem and plug it into the hub.
  
• The server:
• Plug a normal CAT5 cable into the network card you just configured (if you're not sure which one it is, a green LED should go on when you plug the other end in). Plug the other end into the hub.
  

• Alternative cabling:
• If you don't have a hub, just connect the network cards directly together with a crossover cable.
  
• Run the following ping commands:
• On the server: # ping 192.168.0.3
• See the green screen example, above. You should see similar times.
• On the PC: # ping 192.168.0.2
• -Start-
• -Run...-
• Type 'cmd' [OK]
• This opens a DOS screen.
• Type: ping 192.168.0.2
  
• See the green screen example, above. You should see similar times.
• If all this checks out, restore the PC network settings and move its cable back to the ADSL modem. You should be back on the net - if not, reboot.