M e r i d i a n I I U s e r M a n u a l
14
C H A P T E R T W O
15
M e r i d i a n I I 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
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5808 errors:0 dropped:0 overruns:0 frame:0
TX packets:5808 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:728178 (711.1 KiB) TX bytes:728178 (711.1 KiB)
Pay particular attention to the settings shown for
eth0
and
eth1
, in particular the
Mask
: setting,
which should match that which is appropriate for your network. Now check the remaining configura-
tion parameters using
route
:
Meridian II GPS(root@Meridian II:~)-> route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 1 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
localnet * 255.255.255.0 U 0 0 0 eth0
192.168.5.0 * 255.255.255.0 U 0 0 0 eth1
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 Meridian II has been successfully configured to
operate on your network and you are ready to check operation of the Meridian II over the network. If
not, you should recheck 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 com-
mand:
Meridian II GPS(root@Meridian II:~)-> 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 the domain name you entered previ-
ously using
netconfig
, and the nameserver IP address(es) to use for that domain.
Check Network Operation
With your Meridian II 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 Meridian II.
Alternatively, you could
ping
one of your servers or workstations from the Meridian II prompt to test
the setup.
Once you have successfully established network communications with the Meridian II, you may per-
form all maintenance and monitoring activities via
telnet
and
ftp
. The Meridian II provides both
client and server operation using
telnet
. For security reasons, only client operation is supported us-
ing
ftp
. You may also monitor the Meridian II via the HTTPS interface (see
Chapter 7 - HTTPS
).
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 Meridian II. Both of these protocols are supported in the Meridian II via the
OpenSSH implementations for Linux. Refer to
Chapter 5 - Security, OpenSSH
for more information
about the secure shell protocol.
Summary of Contents for Meridian II
Page 2: ......
Page 20: ...M e r i d i a n I I U s e r M a n u a l This page intentionally left blank...
Page 139: ...119 M e r i d i a n I I U s e r M a n u a l R E A R P A N E L I O...
Page 216: ...M e r i d i a n I I U s e r M a n u a l 196 A P P E N D I X J...
Page 235: ...215 M e r i d i a n I I U s e r M a n u a l S P E C I F I C AT I O N S...
Page 236: ...M e r i d i a n I I U s e r M a n u a l 216 A P P E N D I X K...
Page 239: ......
