<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Thin Client: New User Guide: Server setup</TITLE>
<LINK HREF="Thinclient-HOWTO-4.html" REL=next>
<LINK HREF="Thinclient-HOWTO-2.html" REL=previous>
<LINK HREF="Thinclient-HOWTO.html#toc3" REL=contents>
</HEAD>
<BODY>
<A HREF="Thinclient-HOWTO-4.html">Next</A>
<A HREF="Thinclient-HOWTO-2.html">Previous</A>
<A HREF="Thinclient-HOWTO.html#toc3">Contents</A>
<HR>
<H2><A NAME="Server"></A> <A NAME="s3">3. Server setup</A></H2>
<P>The server needs to be setup in readiness for the client in a number of ways
<P>
<H2><A NAME="ss3.1">3.1 Check your network services on your server</A>
</H2>
<P>run the command <CODE>/sbin/ifconfig</CODE> if your output is similar to below
then your loopback and ethernet card are correctly configured.
<P>
<HR>
<PRE>
[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
</PRE>
<HR>
<P>
<P>If not ...
<UL>
<LI> loopback, if this isn't here you need to activate it at start up,
</LI>
<LI> ethernet card, is it being detected,is the driver a module
</LI>
<LI> you can set these in linuxconf or netcfg
</LI>
</UL>
<P>
<H2><A NAME="ss3.2">3.2 Setting up a dhcpd daemon</A>
</H2>
<P>Here the server gives out IP numbers to requests by clients
<P>
<UL>
<LI>is DHCPD installed, maybe (as root) just run ntsysv and have it start at
boot time
</LI>
<LI>this <CODE>/etc/dhcpd.conf</CODE> 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)
<HR>
<PRE>
#/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";
</PRE>
<HR>
</LI>
<LI>the <CODE>/etc/hosts</CODE> file resolves IP numbers into host names
<HR>
<PRE>
#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
</PRE>
<HR>
</LI>
</UL>
<P>
<P>
<H2><A NAME="ss3.3">3.3 Tftpd setup</A>
</H2>
<P>trivial ftp - after you have your IP number your client requests a kernal,
this is delivered over ethernet.
<UL>
<LI>Install tftpd, make sure it's active in <CODE>/etc/inetd.conf</CODE>,
typical line
<HR>
<PRE>
tftp dgram udp wait root /usr/sbin/tcpd in.tftpd -s /tftpboot
</PRE>
<HR>
</LI>
</UL>
<P>restart inetd, kill -HUP "process id of inetd"
<P>
<H2><A NAME="ss3.4">3.4 Kernel image</A>
</H2>
<P>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
<EM>Root file system on NFS?</EM> and <EM>BOOTP support?</EM>
<P>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".
<P>see etherboot-4.2/doc/html/README-3.html
<P>should i put a copy of mine somewhere for download RH6.0 ne2000 NIC
<P>
<H2><A NAME="ss3.5">3.5 Security</A>
</H2>
<P>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 :
<HR>
<PRE>
#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 :
</PRE>
<HR>
<P>more security - look for more information in the ldp-howto's and if your
using etherboot, in it's security howto.
<P>
<HR>
<A HREF="Thinclient-HOWTO-4.html">Next</A>
<A HREF="Thinclient-HOWTO-2.html">Previous</A>
<A HREF="Thinclient-HOWTO.html#toc3">Contents</A>
</BODY>
</HTML>
