Scannex ip.buffer, Руководство пользователя

Страница: 68 / 152

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
10.2. TCP
There are two methods of connection with TCP. Either the ip.buffer behaves as a server
and waits for the device to connect, or the ip.buffer connects into the device.
In addition, there are options for Match & Send (to allow for login sequences) and a regular
heartbeat.
TCP/IP
Connect
“
ipbuffer to Device (active/client)
” – the device is
listening for the ip.buffer
“
Device to ipbuffer (passive/server)
” – the device will
connect into the ip.buffer (usually you have to program
the device with the IP address of the buffer)
[Device to ipbuffer (passive/server)]
Interface
“
LAN only
” – dial-in PPP connections are blocked
“
Modem only
” – Ethernet connections are blocked
“
LAN or Modem
” – either PPP or Ethernet can be used
[LAN only]
Address
For “
ipbuffer to Device (active/client)
” mode, this is
the name or IP address of the device you wish to collect
data from.
[blank]
Allow
For “
Device to ipbuffer (passive/server)
” mode, you
choose to enter a name, IP address, wildcarded IP address
to specify which devices can connect. You can also enter a
comma or semi-colon separated list
10 .
If this is blank then the ip.buffer will allow any device to
connect.
( Hint : start with a blank setting, get the configuration working
and then lock it down with a value) [blank]
TLS/SSL
“
No encryption
” - a regular TCP connection.
“
Implicit (by port)
” - starts with an SSL/TLS connection.
For devices that require SSL/TLS (e.g. Nortel BCM Live
Stream)
[No encryption]
TCP Port The port number for the TCP/IP socket [2001] , [2002] , etc
10 e.g. “192.168.0.*, device.scannex.com, 192.168.*”. Wildcards are “*” for anything, and “?” for
any single character.
Page 64
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
10.2. TCP
There are two methods of connection with TCP. Either the ip.buffer behaves as a server
and waits for the device to connect, or the ip.buffer connects into the device.
In addition, there are options for Match & Send (to allow for login sequences) and a regular
heartbeat.
TCP/IP
Connect
“
ipbuffer to Device (active/client)
” – the device is
listening for the ip.buffer
“
Device to ipbuffer (passive/server)
” – the device will
connect into the ip.buffer (usually you have to program
the device with the IP address of the buffer)
[Device to ipbuffer (passive/server)]
Interface
“
LAN only
” – dial-in PPP connections are blocked
“
Modem only
” – Ethernet connections are blocked
“
LAN or Modem
” – either PPP or Ethernet can be used
[LAN only]
Address
For “
ipbuffer to Device (active/client)
” mode, this is
the name or IP address of the device you wish to collect
data from.
[blank]
Allow
For “
Device to ipbuffer (passive/server)
” mode, you
choose to enter a name, IP address, wildcarded IP address
to specify which devices can connect. You can also enter a
comma or semi-colon separated list
10 .
If this is blank then the ip.buffer will allow any device to
connect.
( Hint : start with a blank setting, get the configuration working
and then lock it down with a value) [blank]
TLS/SSL
“
No encryption
” - a regular TCP connection.
“
Implicit (by port)
” - starts with an SSL/TLS connection.
For devices that require SSL/TLS (e.g. Nortel BCM Live
Stream)
[No encryption]
TCP Port The port number for the TCP/IP socket [2001] , [2002] , etc
10 e.g. “192.168.0.*, device.scannex.com, 192.168.*”. Wildcards are “*” for anything, and “?” for
any single character.
Page 64