The server needs to be setup in readiness for the client in a number of ways
run the command /sbin/ifconfig
if your output is similar to below
then your loopback and ethernet card are correctly configured.
[cassie@snoball cassie]$ /sbin/ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:854 errors:0 dropped:0 overruns:0 frame:0 TX packets:854 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 eth0 Link encap:Ethernet HWaddr 00:AA:00:BB:BD:09 inet addr:192.168.53.1 Bcast:192.168.53.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:190369 errors:0 dropped:0 overruns:0 frame:0 TX packets:249267 errors:0 dropped:0 overruns:0 carrier:1 collisions:4793 Interrupt:5 Base address:0x320
If not ...
Here the server gives out IP numbers to requests by clients
/etc/dhcpd.conf
file assigns static IP numbers if you have
a matching MAC address, A MAC address is a unique 'number' given to the NIC.
The start of the 'number' is based on the manufacturer, if you don't have a
sticker on the card, attempt to load the rom image from eprom or floppy and
see what it reports. (see client setup)
#/etc/dhcpd.conf subnet 192.168.35.0 netmask 255.255.255.0 { option domain-name "gundog.net"; range dynamic-bootp 192.168.35.128 192.168.35.255; default-lease-time 21600; max-lease-time 43200; } host 286 { filename "/tftpboot/kermit.nb"; hardware ethernet 00:80:c8:22:ae:de; fixed-address 192.168.35.70; } host elite { filename "/tftpboot/vmlinuz.xterm"; hardware ethernet 00:00:79:80:34:c9; fixed-address 192.168.35.23; option host-name "elite";
/etc/hosts
file resolves IP numbers into host names
#etc/hosts 127.0.0.1 localhost localhost.localdomain 192.168.53.1 snoball snoball.gundog.net 192.168.53.23 elite elite.gundog.net
trivial ftp - after you have your IP number your client requests a kernal, this is delivered over ethernet.
/etc/inetd.conf
,
typical line
tftp dgram udp wait root /usr/sbin/tcpd in.tftpd -s /tftpboot
restart inetd, kill -HUP "process id of inetd"
You must compile a kernel for the Client that includes NFS support and the NIC driver for that client compiled in (not modules). Answer yes to Root file system on NFS? and BOOTP support?
After building the kernel, run mknbi-linux from the Etherboot distribution on it.(the mknbi program in the netboot/linux directory) Install this tagged image as /tftpdir/"vmlinuz.xterm".
see etherboot-4.2/doc/html/README-3.html
should i put a copy of mine somewhere for download RH6.0 ne2000 NIC
It's easiest to allow anybody and anything to run services and process on your computer, but one day you will be sorry. You restrict these by your /etc/hosts.deny and specifically restore rights by /etc/hosts.allow, indicative examples :
#hosts.deny # all except those in hosts.allow ALL:ALL #hosts.allow #only hosts within my domain and my host at home. ALL:LOCAL, 192.168.53. #<-- note:no space after :
more security - look for more information in the ldp-howto's and if your using etherboot, in it's security howto.