B&B Electronics Manufacturing shall not be liable for incidental or consequential damages resulting from the furnishing, performance, or use of this
manual. All brand names used in this manual are the registered trademarks of their respective owners. The use of trademarks or other designations
in this publication is for reference purposes only and does not constitute an endorsement by the trademark holder.
5.2 Serial ...........................................................................................................................................21
Airborne is a line of highly integrated 802.11 radios and device servers, designed to
address the demands of the complex M2M market. Utilizing the latest 802.11, CPU and
network technologies, the Airborne™ family of products provide a broad, encompassing
solution for wireless applications requiring performance, reliability and advanced
technology.
The Airborne Wireless Device Server family includes everything necessary to connect a
Serial or Ethernet device to a high-performance 802.11 network. The WLNN-XX-DP500
series includes a full featured 802.11a/b/g/n radio and a high performance 32bit ARM9
processor running an embedded OS and B&B Electronics‟ exclusive Airborne Device
Server firmware, allowing the wireless network enabling of almost any device or system.
WPA2-Enterprise (AES-CCMP + EAP) is the security standard for leading-edge
enterprise networks. The Airborne Enterprise Device Server supports the latest security
standards and more. Fully compliant to the WPA2-Enterprise specification, the device
includes a wide range of EAP methods (with certificates), including support for legacy
functionality (WPA, WEP and LEAP).
The best security and advanced networking is no good if you cannot connect your device
to the Airborne Enterprise Device Server. Airborne offers the widest range of Serial and
Ethernet based interfaces in the industry. With flexibility and performance the WLNN-XXDP500 series lets you decide how you want to use it.
Designed by the B&B Electronics engineers specifically to meet the demands of the
industrial, automotive and medical markets, the Airborne Enterprise Device Server has
the widest operating temperature range and highest level of reliability available, all
backed by a lifetime warranty. B&B Electronics also provides FCC Modular certification,
potentially removing the need for further regulatory work.
The previous generations of Airborne Wireless Device Servers have been integrated and
deployed into a wide range of applications and markets, including Medical, Industrial,
Telematics and Logistics.
B&B Electronics 4th Generation Wireless Device Server extends the reputation of the
family further by expanding the wireless connectivity to use the latest technologies. The
Airborne Enterprise Device Server family is the industry-leading solution, and represents
a breakthrough, in 802.11 connectivity for all M2M markets.
The following manual covers a detailed description of the Airborne Command Line
Interface (CLI) used for management, configuration and integration of the Airborne and
AirborneDirect Enterprise Device Server products into embedded systems.
14 Airborne Enterprise CLI Reference Manual
The area next to the indicator will identify the specific information and make any
references necessary.
The area next to the indicator will identify the specific information and make any
references necessary.
2.0 Conventions
The following section outlines the conventions used within the document, where
convention is deviated from, the deviation takes precedence and should be followed. If
you have any question related to the conventions used or clarification of indicated
deviation please contact B&B Electronics Sales or Wireless Support.
2.1 Terminology
Airborne Enterprise Device Server and AirborneDirect Enterprise Device
Server is used in the opening section to describe the devices detailed in this
document, after this section the term module will be used to describe the
devices.
2.2 Notes
A note contains information that requires special attention. The following
convention will be used. The area to the right of the indicator will identify the
specific information and make any references necessary.
2.3 Caution
A caution contains information that, if not followed, may cause damage to the
product or injury to the user. The area to the right of the indicator will identify the
specific information and make any references necessary.
2.4 File Format
These documents are provided as Portable Document Format (PDF) files. To
read them, you need Adobe Acrobat Reader 4.0.5 or higher. For your
convenience, Adobe Acrobat Reader is provided on the Radio Evaluation Kit CD.
Should you not have the CD, for the latest version of Adobe Acrobat Reader, go
to the Adobe Web site (www.adobe.com).
Airborne Enterprise CLI Reference Manual15
2.5 Courier Typeface
Commands and other input that a user is to provide are indicated with Courier
typeface. For example, typing the following command and pressing the Enter key
displays the result of the command:
wl-info <cr>
Module Firmware Version: 1.00
Radio Firmware Version: 5.0.21-210.p17
Link Status: Connected
SSID: Quatech_Connected
MAC Address: 000B6B77619E
BSSID: 0016B637880D
Transmit Rate (Mb/s): 54
Signal Level (dBm): -40
Noise Level (dBm): -92
IP Address: 192.168.1.100
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Primary DNS: 68.107.28.42
Secondary DNS: 68.107.29.42
Up Time (Sec): 48313
16 Airborne Enterprise CLI Reference Manual
3.0 Scope
The CLI Reference Manual documents the Command Line Interface (CLI) for the module.
This document replaces the Airborne CLI reference manual and includes the commands
introduced or updated with the Enterprise Class product family.
The CLI is one of a number of management interfaces for the product family and is
comprised of a set of ASCII text commands and parameters used to provision the
module, provide module status and environmental feedback, as well as support firmware
and file delivery to the module.
This reference manual includes the following sections.
3.1 CLI Overview
In this section we will review the different device configurations and basic
operation and functionality of the module. Support for a specific function is
dependent upon the device configuration chosen. It will be noted within each
section to which configuration it applies.
3.2 Understanding the CLI
This section will cover the use of the CLI and describe the action and reaction to
the specific functional calls and commands.
Methods of connection and delivery of the CLI will also be reviewed. CLI
conventions, data types and command responses will also be addressed in this
section.
3.3 Typical Development System
An outline and description of a basic development and evaluation system will be
covered in this section. It is not necessary to use this exact configuration;
however descriptions of connectivity and use, utilized on other sections of the
manual, will be based upon the system structure described in this section.
3.4 Serial Device Server Use
In this section the base functionality of the module will be described and
examples of use and configuration will be provided to highlight the use of the
both it and the CLI. Refer to this section to understand the differences between a
command port, data tunnel, TCP/IP vs. UDP use and server vs. device operation.
3.5 Ethernet Bridge Use
A full description of the operation of the Airborne Ethernet Bridge, its place in the
network infrastructure and the required parameters will be covered in this
section.
Airborne Enterprise CLI Reference Manual17
3.6 WLAN Security
This section will cover the use of the advanced security features available in the
module. Configuration of the module, requirements for successful deployment,
examples of configuration for the use of the advanced authentication and
wireless security options will be provided.
Descriptions of how to use WEP, WPA and WPA2 will be included. Outlines of
the authentication methods supported (EAP), certificate delivery and deployment
will be reviewed.
3.7 Using Configuration Files
This section will cover the use of configuration files to predefine device
configuration, to be delivered and stored on the module.
3.8 Protecting Configuration Settings
This section will cover the use of encryption to protect sensitive configuration
settings from prying eyes. This is used on the parts of the configuration that are
considered sensitive, like encryption keys, passwords, etc.
3.9 WLAN Roaming
This section will outline the commands that impact the roaming performance of
the module. Discussion of configuration options based upon application
requirements is also included.
3.10 FTP Configuration
The Airborne Enterprise Device Server family supports delivery of certificates,
private keys, configuration files and module firmware via FTP. This section
describes how to configure and use the FTP capabilities.
3.11 Firmware Update
The Airborne Enterprise Device Server family supports in-field updating of the
devices firmware. This allows devices already deployed access to the latest
feature updates and enhancements.
3.12 U-Boot Update
This section describes the ability to update the U-Boot. This should be an
infrequent event, however when required, a procedure exists to install an update.
3.13 Power Management
A review of the CLI commands impacting device power usage will include a
description of the power save modes and how to utilize them. A discussion on
the impact of power, data latency and module status will be included.
18 Airborne Enterprise CLI Reference Manual
3.14 Digital GPIO
The Airborne Enterprise Device Server family supports two Digital GPIO ports.
The two ports can be configured to be used as general IO. Some modules allow
the LED pins to be re-assigned as GPIO pins.
3.15 Command Line Descriptions
This section will describe in detail the syntax, arguments and use of the available
commands.
Airborne Enterprise CLI Reference Manual19
Part No.
Description
WLNN-SE-DP5XX
802.11 to RS232/422/485 and UART Serial Device Server Module,
Enterprise Class
WLNN-AN-DP5XX
802.11 to UART Serial Device Server Module, Enterprise Class
WLNN-SP-DP5XX
802.11 to SPI Serial Device Server Module, Enterprise Class
WLNN-ER-DP5XX
802.11 to 10/100 Ethernet Router (NAT Level3) Module, Enterprise Class
WLNN-EK-DP5XX
Enterprise Class Airborne Development and Evaluation Kit
ABDN-ER-DP5XX
802.11 to 10/100 Ethernet Router (NAT Level3), Enterprise Class
ABDN-ER-IN5XXX
802.11 to 10/100 Industrial Ethernet Router (NAT Level3), 5-36VDC ,
Enterprise Class
ABDN-SE-IN5XXX
802.11 to RS232/422/485 Device Server (Single and Dual Port), Ethernet,
5-36VDC , Enterprise Class
APXN-Q50xx
Industrial Access Point, Ethernet to 802.11, 5-36VDC, Enterprise Class
APXN-Q54xx
Industrial Access Point, Serial to 802.11, Ethernet, 5-36VDC, Enterprise
Class
4.0 Supported Devices
This manual supports the Enterprise set of CLI commands across all platforms. Not all
commands are supported on all platforms; the command descriptions in Section 19.0
provide guidance on which devices support it.
At the time of writing, the CLI command list represents the v3.16 release of the WLNNXX-DP500 series of Airborne Device Server firmware. The part numbers supporting the
commands described in this document include, but aren‟t limited to, the following:
Note: 802.11 includes 802.11a/b/g/n bands
20 Airborne Enterprise CLI Reference Manual
5.0 CLI Overview
The moduleincludes a Command Line Interface (CLI) Server. The CLI Server is the
primary user interface for configuring, controlling, and monitoring the module. Users and
OEM applications can establish CLI Sessions to the CLI Server via the serial interface or
a TCP connection on the wireless and Ethernet interfaces.
This document describes the Command Line Interface commands, including the
extensions introduced or updated with the introduction of the Enterprise module (WLNNXX-DP500 family). Since different Airborne™ modules differ in functionality, there may be
differences in the use of the CLI for each particular device. These differences are clearly
identified as part of this document.
There are four primary configurations supported by the module family: these are UART,
Serial, SPI and Ethernet. Each device type will be described below. In some cases
multiple interface options are available within a specific configuration; the functionality of
these interfaces does not vary between device configurations unless specifically noted
within the device description.
5.1 UART
The UART (Universal Asynchronous Receiver/Transmitter) interface is a digital
interface that supports full-duplex transfer of data serially between the module
and a connected host. It supports the following settings:
Flow Control: None, Hardware (CTS/RTS), Software (XON/XOFF)
Default settings: 9600, N, 8, 1, No Flow Control.
5.2 Serial
The Serial device includes both a UART interface control and I/O lines to
manage external logic for RS232/422/485 line drivers. It supports the following
settings:
Default settings: 9600, N, 8, 1, No Flow Control.
Note: the second serial port doesn‟t support Hardware Flow Control and only
supports a 4-wire interface for 422/485.
5.3 SPI
The SPI interface is a five (5) pin interface that supports full duplex operation.
The module acts as a SPI slave and requires the master to supply the SPI clock.
The default configuration for the interface is:
Airborne Enterprise CLI Reference Manual21
Master SPI Clock: up to 8MHz
Airborne SPI protocol (see WLNN DP500 Family Data Book, section 7.0 for
details)
5.4 Ethernet
The module supports a fully-compliant 10/100 Ethernet interface capable of
supporting all full- and half-duplex rates. The rates are configurable through the
CLI interface.
The module includes a Broadcom BCM5241A Ethernet PHY; please refer to the
manufacturer‟s datasheet for interface details and appropriate design guidelines.
The interface supports the following settings:
Auto Negotiate, 10Mbps Half Duplex, 10Mbps Full Duplex, 100Mbps Half
Duplex, 100Mbps Full Duplex
Default settings: Auto Negotiate.
22 Airborne Enterprise CLI Reference Manual
6.0 Understanding the CLI
CLI Sessions established to the CLI Server may operate in one of three modes: CLI,
PASS, or LISTEN. Not all modes are supported on all interfaces of the device. A CLI
Session established on the serial interface may operate in any of the three modes. CLI
Sessions established on the wireless or Ethernet interfaces are restricted to CLI or PASS
Modes.
6.1 Connecting to the CLI Server
Users may connect to the CLI Server on the serial interface using a terminal
emulation program such as HyperTerminal or TeraTerm. The module default
settings for the serial interface are:
Bits per second: 9600
Data bits: 8
Stop bits: 1
Parity: none
Flow control: none
Users may also connect to the CLI Server on the wireless or Ethernet interface
using a TCP client such as Windows Telnet or an SSH client. The Module‟s CLI
Server supports a Telnet connection with the following restrictions:
Telnet commands such as DO, WONT, and DON, must not be issued.
Network Virtual Terminal codes are not supported.
The CLI Server‟s network interface is characterized as follows:
The CLI Server listens on the TCP port specified by the wl-telnet-port
parameter. The default is 23.
The CLI Server listens on the SSH port specified by the wl-ssh-port
parameter. The default is 22.
The CLI Server inactivity timer is configured via the wl-telnet-timeout
command.
The CLI Server uses the wl-telnet-timeout value to timeout and close
TCP connections that are inactive.
The CLI Server supports multiple, simultaneous TCP sessions.
6.2 CLI Security
The CLI Server supports five (5) levels of security for each CLI Session. The
security levels provide a safeguard for the set of CLI commands that may be
executed by users. CLI Sessions that are authenticated at a particular security
level may execute all CLI commands specified for that security level and below.
The Module‟s five (5) levels of security are:
Level 0 (L0) = connectionless
Level 1 (L1) = connection, not logged in (default)
Level 0 is the connectionless access level. Access over UDP will use this access
level. The L0 level provides access to the name query services. It is not an
authenticated level.
Level 1 is the default security level for CLI Sessions over TCP or the serial
interface.
CLI Sessions must execute the CLI command auth in order to authenticate the
CLI Sessions to another security level. The CLI command logout returns the
CLI Session back to security Level 1.
6.3 CLI Session Modes
The mode of the CLI Session governs the set of actions allowed in the CLI
session. The following are descriptions of each mode:
6.3.1 CLI Mode
CLI Mode is the command processing mode of the CLI Session. CLI Mode allows
users and OEM applications to simply execute module commands as described
in the section, “CLI Commands.”
A CLI Session may transition into CLI Mode automatically at startup of the CLI
Session (if so configured). See section “CLI Session Startup Modes” for details
on startup modes.
CLI Sessions may transition manually to CLI Mode from the other modes via the
use of the CLI escape processing feature in the CLI Server. See section “CLI
Server Escape Processing” for details.
6.3.2 PASS Mode
PASS Mode is an active data bridging mode of the CLI Server. PASS Mode
allows the user or OEM application to transfer data between a CLI Session on
the network interface and the CLI Session on the serial interface.
A CLI Session may transition to PASS Mode automatically at startup of the CLI
session (if so configured) or manually from the CLI Mode using the CLI pass
command. See section “CLI Session Startup Modes” for details on startup
modes.
The transition from CLI Mode into PASS Mode differs depending on the attributes
of the CLI session. The following sections describe the two PASS Modes.
24 Airborne Enterprise CLI Reference Manual
6.3.3 PASS Mode for the Serial Interface
When the CLI Session on the serial interface attempts a transition to PASS
Mode, the CLI Server establishes an outbound connection from the module to a
user-specified TCP server and/or UDP server on the network interface. Once a
connection is established, data bridging becomes possible between the CLI
Session on the serial interface and the TCP Server and/or UDP server. If the
connection to the primary TCP server failed, the CLI Server will attempt to
connect to a secondary TCP server, if configured. If the transition to PASS Mode
was triggered by the automatic startup configuration, the CLI Server will use the
wl-retry-time configuration parameter to continuously retry connection to
the servers.
The IP addresses of the primary TCP and UDP servers are configured using wl-
tcp-ip and wl-udp-ip CLI commands. The secondary TCP server is
configured using the wl-tcp-ip2 command. The TCP server port is
configured using wl-tcp-port and wl-udp-port CLI commands. The retry
timer is configured using the wl-retry-timeCLI command. See section “CLI Commands” for more details on these commands.
6.3.4 PASS Mode for a TCP CLI Session
When the CLI Session on the network interface (TCP CLI session) attempts to
transition to PASS Mode, the CLI Server establishes a data bridge to the CLI
Session on the serial interface if the following conditions are both true:
The CLI Session on one or more of the serial interfaces is in LISTEN Mode.
The number of CLI Session on the network interface, in PASS Mode, is less
than the CLI sessions on the serial interfaces in LISTEN mode.
If more than one of the Serial interfaces is in LISTEN mode, it is possible to
direct the TCP CLI Session PASS mode connection to either of the available
sessions.
LISTEN Mode is a passive data bridging mode of the CLI Session. The LISTEN
Mode is only applicable on the serial, UART and SPI interfaces. When the CLI
Session on the serial interface enters LISTEN Mode, the module passively waits
for a data bridge to be established from a TCP CLI session. The data bridge
may be initiated using a CLI Session via the PASS Mode or using the tunneling
feature. The CLI Session may transition to CLI Mode using CLI Server escape
processing. See section “CLI Server Escape Processing” for details.
When the serial interface CLI Session is in LISTEN Mode, the following are
possible:
TCP connections on the network interface can use the CLI commands pass,
putget or putexpect to establish a data bridge.
TCP connection can establish a data bridge if tunneling is enabled.
Airborne Enterprise CLI Reference Manual25
The esc-str CLI command supersedes the escape command. It is recommended
that the esc-str be used.
6.3.6 CLI Session Startup Modes
The startup behavior of the CLI Session on each interface is determined as
follows:
The CLI Session on the serial interface startup behavior is determined by the
value of the serial-default parameter.
CLI Sessions on the network interface using the TCP port specified by wl-
telnet-port always start in CLI Mode.
CLI Sessions on the network interface using the TCP port specified by the
wl-tunnel-port or the UDP port specified by wl-udp-rxport, always
start in PASS Mode. However, if the CLI Session on the serial interface is not
in LISTEN Mode, the TCP connection on the wl-tunnel-port will be
rejected by the Module.
Each of the serial ports can have a different CLI Session startup behavior.
Each serial port can have different configuration settings for the tunnel port.
6.4 CLI Server Escape Processing
The CLI Server includes an escape processing feature which allows CLI
Sessions to transition from PASS or LISTEN (data bridging) Mode back to CLI
Mode. Escape processing is configurable to:
disable escape processing
process the receipt of a user-defined escape string as an escape signal
process the receipt of the BREAK signal as an escape signal
When escape processing is disabled, the CLI Server will not parse the data
stream for any escape sequence. When escape processing is configured to use
an escape string, the CLI Server will perform pattern matching for the userdefined escape string in the data stream. The escape sequence must be the last
characters delivered to the module for escape parse to be successful. The
escape string is a five (5)-character string configurable via the escape or esc-
str CLI commands. When escape processing is configured to use the BREAK
signal, the CLI Server will parse the data stream for the BREAK signal.
6.5 Detecting and Executing the Escape Sequence
Upon detection of the escape sequence, the CLI Server applies the follow rules
for transitions of the CLI Session on that interface:
If the CLI Session is in LISTEN Mode and there is no data bridge
established, the CLI Session will transition to CLI Mode and send an OK
response to the CLI Session.
If the CLI Session is in LISTEN Mode and there is an active data bridge
established, the CLI Server will terminate the active data bridge and the CLI
Session will remain in LISTEN Mode. Note that, two escapes are required to
transition from active data bridge to CLI mode.
26 Airborne Enterprise CLI Reference Manual
If the CLI Session is in PASS Mode, the CLI Server will send an OK response
to the CLI Session and transition to CLI Mode.
The following effects of escape processing require the attention of system
implementations:
If the escape sequence is an escape string, the escape string received on
one CLI Session is transmitted to the CLI Session on the other end of the
data bridge prior to performing the CLI Session transition. This allows the
other end to parse the received data and determine when the data bridge is
shutdown.
If the escape sequence is the BREAK signal, the BREAK received on the
serial interface is not transmitted to the wireless interface, but the transition
takes place internally.
The CLI Session that detects the escape sequence will post an OK response
on its interface if the escape sequence caused the CLI Session to transition
to the CLI Mode.
Escape detection does not close the TCP connection. It only terminates the
data bridge. Subsequent use of the pass CLI command will re-establish the
bridge for that interface.
The CLI Server allows independent configuration of escaping processing for
each serial port and for TCP CLI session. The serial interface escape processing
is configurable using the CLI parameter esc-mode-serial. The TCP CLI
Session escape processing is configurable using the CLI parameter esc-
mode-lan. See section “CLI Commands” for details on these parameters.
6.6 CLI Conventions
The CLI uses the following conventions:
All commands consist of a string of printable characters, including the
command and optional arguments delimited by one or more spaces or tabs.
Multiple consecutive spaces or tabs are generally considered as one
delimiter.
Commands and arguments are case sensitive, except hexadecimal values
and port IDs, which can be uppercase or lowercase.
Arguments enclosed within […] are optional.
All arguments are literal ASCII text, except where indicated.
Most commands that set the value of a parameter can also obtain the value
of the parameter by omitting the argument. Numeric values are returned in
aschex format.
A choice between arguments is indicated with the | character. Only one of
the choices can be selected.
All CLI commands are terminated with a <CR>.
The maximum length of a CLI command line is 256 characters, including
spaces and terminating characters.
Argument types include:
<ASCII Text> literal ASCII character string without delimiters (no
spaces or tabs).
Airborne Enterprise CLI Reference Manual27
The TCP CLI interface by default echoes back CLI session input. It is possible to turn
this feature off by issuing the telnet-echo disable command.
<integer> value represented as a decimal integer or as “aschex” value
in the form 0xhhh…hhh.
<aschex> one or more pairs of hexadecimal digits with no prefix in the
form hhh…hhh.
<portid> an I/O port bit number, from 0 to 7.
<IPadrs> - Internet Protocol address string in the format:
nnn.nnn.nnn.nnn; for example: 192.168.10.3.
6.7 ASCHEX vs. Binary Values
Data can be sent to the module as either binary data or a hexadecimal
representation of the actual data being transmitted.
When a LAN device or serial port Host issues a pass command, the data is
transmitted as binary data. By comparison, when the command putget or
putexpect is issued, the senddata content must be encoded as ASCII
hexadecimal digit pairs. The data is translated across the Module and received
as an ASCII representation of the actual data. This is true whether the
transmission initiates from the LAN device or from the Host.
For example, the digits 31 correspond to the ASCII character 1. If you issue a
putget or putexpect command with the senddata value of 314151, the
destination receives the ASCII characters 1, A, and Q.
6.8 Command Responses
The Module responds to CLI commands with a response indicating whether the
CLI command was executed successfully. All responses are terminated by
<CR><LF>.
Multiline responses have each line terminated with <LF><CR> with the response
terminated by <CR><LF>.
After the Module executes a CLI command successfully, it returns the response:
OK<CR><LF>
Otherwise, it returns an error response. Error responses are returned in the
following general format:
Error 0xhhhh: error text<CR><LF>
In the response the aschex value is the error code. A summary of error code can
be found in section 0.
28 Airborne Enterprise CLI Reference Manual
7.0 A Typical Development System
A typical evaluation system includes:
A Serial Host: A computer connected to of the serial ports of the Airborne™
Enterprise Development Board.
A LAN Host: A computer that communicates wirelessly with the Module through an
Access Point (AP).
An Access Point.
An Airborne™ Enterprise Development kit.
Airborne Enterprise CLI Reference Manual29
Only one CLI session on the network (802.11/Ethernet) interface may be bridged with
any single CLI session on the serial interface at a time.
8.0 Serial Device Server Use
In this section the base functionality of the module will be described, examples of use and
configuration will be provided. Refer to this section to understand the differences between
a command port, data tunnel, TCP/IP vs. UDP use and server vs. device operation.
The UART, Serial and SPI versions of the module provide the ability to connect a raw
serial data stream to a TCP/IP based network, using 802.11 or Ethernet as the primary
network connection media. To facilitate this functionality the module supports a number
of management and data bridging interfaces on both the serial (Serial/UART/SPI) and
network (802.11/Ethernet) interfaces. As described in section 3.2, there are multiple
states for the CLI interface; this section will describe the data bridging options and the
required CLI configuration for each.
8.1 Data Bridging
The module provides data bridging via the PASS and LISTEN Modes of the CLI
Session. During data bridging, the raw payload of an incoming TCP or UDP
packet is transmitted to the serial interface while the raw data stream from the
serial interface is transmitted as the payload of an outgoing TCP or UDP packet.
There are multiple ways to setup a data bridge using the module. A bridge may
be initiated from the Serial Host, from a TCP connection on the wl-telnet-port, from a TCP connection on the wl-tunnel-port, from a UDP message
on the wl-udp-rxport or from a Secure Shell (SSH) connection on the wl-ssh-port.
8.1.1 Bridging from the Serial Interface
The CLI Session on a serial interface may initiate a data bridge via the use of the
serial-defaultparameter set to “pass” or by manually issuing the pass CLI
command. Prior to establishing the data bridge, the module must be properly
configured to connect to a server on the network that will accept the
communications; Table 1 below identifies the parameters that need to be set.
30 Airborne Enterprise CLI Reference Manual
Loading...
+ 234 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.