Monroe Electronics R189se - Manual (Page 65)

- 60 -
EAS NET Event Transfer Protocol - Displays the Event Transfer protocol. This
is simply the LAN communication method used to send the alert event data.
Depending upon the Event transfer protocol, other configuration fields are
necessary or optional. Some protocols require passwords; others use encryption
keys. Most also provide for optional data file connections.
The event transfer protocol options are:
1. Secure Copy (SCP) – Uses the Secure Shell (SSH) network protocol for
both the data file transfers and event file transfer. No passwords are needed.
For all of the Secure Shell protocols (1.3), passwords are not used. Instead,
the One-Net public ssh key id (under /root/.ssh/id_dsa.pub and also
displayed at the bottom of the Server > Status > Network page) must be
added into the remote host's authorized ssh keys list. The keys provide for
encrypted data transfer and for secure authentication without a password.
2. Secure Shell STDIN Only (SSH) – Uses the Secure Shell (SSH) network
protocol for the event file transfer. No data files can be sent. This protocol
requires that the receiving device read the EAS NET event file from
Standard input from within the shell script. In such a configuration, SCP and
SSH login to the EAS NET user will not present to the remote platform
shell.
3. Secure Shell STDIN & Copy (SSH with SCP) – This is a variation on
protocol #2 above. The event file is sent as in #2. But the Web interface will
display a field to enter a second user account for sending data files to the
remote host. The Secure Shell (SSH) network protocol is used for both
transfers.
4. File Transfer Protocol (FTP) – Uses the File Transfer Protocol (FTP)
network protocol for both the data file transfers and event file transfer. A
password is required. FTP does not encrypt or secure passwords during
transmission. The password is sent in clear text to the remote host FTP
demon. If security is an issue, do not use or design an FTP based EAS NET
scheme. Some FTP daemons refuse passive port connections. Use the
provided checkbox to enable a non-passive connection if needed.
5. TCP event notification – Uses a TCP socket from the One-Net to the remote
host to send the alert event file. For sending the optional data files, one of
FTP or SSH SCP network protocols can be selected. A valid user account on
the remote host must be entered. The information described above for
passwords and keys apply depending upon the chosen data protocol.
6. DVS168/EARS – This is a special case of EAS NET. A TCP socket is used
to communicate an event notification, while FTP is used to send data files.
7. Legacy Mediaroom – This is a special protocol bundled under EAS NET
when the Microsoft© Mediaroom
TM
option is licensed.