EndRun Tempus LX GPS, User Manual

Page: 26 / 116

T e m p u s L X G P S U s e r M a n u a l 14
C H A P T E R T W O
15 T e m p u s L X G P S U s e r M a n u a l
B A S I C I N S T A L L A T I O N
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:170 errors:0 dropped:0 overruns:0 frame:0
TX packets:170 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Pay particular attention to the settings shown for
eth0
and in particular the
Mask
: setting, which
should match that which is appropriate for your network. Now check the remaining configuration
parameters using
route
:
Tempus LX GPS(root@gntp:~)-> route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.248 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.241 0.0.0.0 UG 1 0 0 eth0
Here you are interested in the default gateway address. It should match the appropriate one for your
network. If so, then the ethernet interface of your Tempus LX has been successfully configured to
operate on your network and you are ready to check operation of the Tempus LX over the network. If
not, you should re-check your configuration and/or repeat the
netconfig
procedure.
If you have configured a nameserver(s) for your network, you may check that by issuing this shell
command:
Tempus LX GPS(root@gntp:~)-> cat /etc/resolv.conf
search your.domain
nameserver 192.168.1.1
nameserver 192.168.1.2
Which displays the contents of the /etc/resolv.conf file containing your domain name and the nam-
eserver IP address(es) to use for that domain.
Check Network Operation
With your Tempus LX network parameters properly configured, you are ready to test the setup using
ping
from a server or workstation that is able to access the network connected to the Tempus LX.
Alternatively, you could
ping
one of your servers or workstations from the Tempus LX shell prompt
to test the setup.
Once you have successfully established network communications with the Tempus LX, you may
perform all maintenance and monitoring activities via
telnet
and
ftp
. The Tempus LX provides
both client and server operation using
telnet
. For security reasons as well as to reduce the memory
footprint in the Tempus LX, only client operation is supported using
ftp
.
Security conscious users will want to use
ssh
, the secure shell replacement for
telnet
, as the login
means. The companion utility,
scp
provides a secure replacement for ftp as a means of transferring
files to and from the Tempus LX. Both of these protocols are supported in the Tempus LX via the
OpenSSH implementations for Linux. Refer to Appendix A - Security for more information about
the secure shell protocol.