AdderLink XDIP

User Guide

Experts in Extender
Connectivity
Solutions Solutions
Contents
Introduction Admin menus.......................................................................................................21
Receiver node settings.................................................................................21

INSTALLATION
Welcome.................................................................................................................2
General Settings page.............................................................................21
AdderLink XDIP features....................................................................................4
OSD Settings page..................................................................................22
Supplied items (per node)...................................................................................5
Manage Ports page..................................................................................23
Optional extras......................................................................................................6
Advanced page.........................................................................................24
Installation Software Upgrade page..........................................................................26

CONFIGURATION
Locations.................................................................................................................7 Setup Channels page...............................................................................27
Mounting.................................................................................................................7 Transmitter node settings...........................................................................27
Connections...........................................................................................................7 General Settings page.............................................................................27
Computer connections..................................................................................8 Manage Ports pages................................................................................28
Video format conversion...............................................................................9 Advanced pages.......................................................................................29
Console connections....................................................................................11 Software Upgrade page..........................................................................30

OPERATION
Audio connections........................................................................................12
Link connection.............................................................................................12
Operation
Switching channels..............................................................................................31
Power connection.........................................................................................13
Switching channels from a receiver...........................................................31
Configuration Switching channels from an external system..........................................32
Initial configuration.............................................................................................14 Indicators..............................................................................................................33

INFORMATION
Navigating the configuration wizard, OSD and Admin menu..............14

FURTHER
To use the configuration wizard................................................................14
Further information
Getting assistance...............................................................................................34
To add a new transmitter............................................................................18
Appendix 1 - IGMP.............................................................................................35
Restoring a node.................................................................................................20
Appendix 2 - Layers............................................................................................36
Appendix 3 - Link cable interference protection.........................................37
Appendix 4 - XDIP API......................................................................................38

INDEX
Appendix 5 - Open source licenses................................................................40

Index
1
Introduction
WELCOME
Thank you for choosing the AdderLink XDIP extender nodes. At their simplest, Transmitter or receiver? Your call Feed through for flexibility

INSTALLATION
AdderLink XDIPs are high resolution, low latency digital KVM extenders which will Every XDIP node arrives in Start of Life Every XDIP node features a Feed through
operate just as easily across a direct 100 meter CATx connection as they will across (SoL) mode: it’s up to you to choose port. This allows you to add a local
your standard 1GbE local network. However, there’s much more to them than that. whether it becomes a transmitter or console that can access both nearby
Many hosts, one console Multiple consoles, one host a receiver. This ensures that your small and distant resources. When the local
XDIPs can form what might be termed Alternatively, a different grouping of XDIPs stock of nodes can efficiently meet your console is placed on an XDIP receiver,
a Distributed KVM switch, where you can form a ‘KVM Sharer’ to allow up to current requirements - and then be easily it will operate as its own KVM switch.
authorize a single XDIP receiver to access 256 receivers to access and control the redistributed, in any order, to satisfy future Alternatively, when the local console is

CONFIGURATION
up to sixteen separate XDIP transmitters resources of a single PC host system: issues too. attached to an XDIP transmitter, it will
and their connected PC host systems: TX also act as a video splitter:
KVM Sharer mode
A single XDIP PWR
transmitter can be
shared by up to
Start of Life (SoL) mode A D D E R L I N K

TX
LNK USB VID PWR

256 receivers
www.adder.com

The operation mode of each XDIP is signified

RX
TX
by the color of the front panel PWR indicator
mode
A D D E R L I N K A D D E R L I N K A D D E R L I N K A D D E R L I N K

TX
LNK USB VID PWR

www.adder.com
TX
LNK USB VID PWR

www.adder.com
TX
LNK USB VID PWR

www.adder.com
TX
LNK USB VID PWR

www.adder.com

Local Area
All HD video welcome A combined application of the Feed through
Network

OPERATION
HDMI is the native video port on each and KVM sharer features could be used, for
A D D E R L I N K

RX
LNK USB VID PWR
A D D E R L I N K

RX
LNK USB VID PWR
node, however, using suitable third party instance, to serve a lecture theater:
converters you can connect DVI, dual-
www.adder.com www.adder.com

Local Area mode DisplayPort® (DP++) or VGA signals TX

Network at either end of the links:

Presenter’s Lectern screen
laptop (on feed through
HDMI HDMI port)
Distributed KVM DVI DVI Local Area

INFORMATION
A D D E R L I N K A D D E R L I N K

Switch
TX
LNK USB VID PWR

www.adder.com
RX
LNK USB VID PWR

www.adder.com

Network
DP++ DP++

FURTHER
A single XDIP A D D E R L I N K

RX
LNK USB VID PWR

www.adder.com

receiver can choose VGA VGA

between up to sixteen
transmitters OSD
A D D E R L I N K

RX
LNK USB VID PWR

Power to perform: POE or adapter

www.adder.com

Efficiency is key to XDIP operation,

A D D E R L I N K A D D E R L I N K

RX
LNK USB VID PWR

www.adder.com
RX
LNK USB VID PWR

www.adder.com

sufficiently so that each node can Theater Theater

screen screen
comfortably function using only the Power Projector

Remote controlled matrix configuration - see next page over Ethernet (PoE) capabilities of your
network. Where that’s not an option, we

INDEX
also supply optional power adapters for
local mains operation.

continued
2
Remote controlled matrix
XDIPs can also form an audio-visual matrix where multiple receivers access content To ensure ease of configuration with third party controllers, the XDIP system is provided
from a choice of transmitters - all under external control. Such configurations are useful with a full REST API.
in distributed signage applications where a control system coordinates multiple displays New features have been added to XDIP units to enable remote control matrix operation:
(up to 256) and determines how each one derives its digital content. • Each XDIP module can be assigned a static IP address as well as its main (DHCP-
There are two methods for remotely controlling an XDIP matrix: provided) dynamic address, so that external systems have a separate, consistent

INSTALLATION
• Method 1 - Using third party controller system, such as those supplied by Crestron™, control pathway.
AMX™ and many others, to issue commands through our RESTful API (see page 38), • Each XDIP module has separate admin and access passwords; the latter providing
or selective access to content and switching controls.
• Method 2 - Using the browser on a connected PC to access the receivers and using • Full third-party switching support provided by REST API via the network connection.
the resulting OSD menu (see page 32). The YAML file for the API can be found at:
IMPORTANT:When using either method, you must first enable the remote control https://support.adder.com/tiki/tiki-index.php?page=XDIP%3A+Using+the+API
functionality on each receiver (this option is disabled by default).

CONFIGURATION
See Receiver > Advanced page on page 24.

Remote controlled matrix

An external control system or connected PC can determine how each
receiver should derive its content, from a choice of up to eight transmitters.

Remote control method 1: Remote control method 2:

• From your external control system, use the XDIP • Using a web browser, enter: https://<ip-address>:8443
RESTful API and send commands in the following where <ip-address> is the static address for the receiver.
format: https://<ip-address>:8443/api/<parameters>

OPERATION
A D D E R L I N K

TX
A D D E R L I N K

TX
A D D E R L I N K

TX
A D D E R L I N K

TX • Enter the access password when requested.

where <ip-address> is the static address for the receiver.
LNK USB VID PWR LNK USB VID PWR LNK USB VID PWR LNK USB VID PWR

www.adder.com www.adder.com www.adder.com www.adder.com

• See Appendix 4 for a list of the API parameters. • Choose the required transmitter from the list.

Third party control system

(e.g. Crestron™,AMX™, etc.) Local Area
Network

INFORMATION
via RESTful API

FURTHER
A D D E R L I N K A D D E R L I N K A D D E R L I N K A D D E R L I N K A D D E R L I N K A D D E R L I N K A D D E R L I N K A D D E R L I N K

RX
LNK USB VID PWR

www.adder.com
RX
LNK USB VID PWR

www.adder.com
RX
LNK USB VID PWR

www.adder.com
RX LNK USB VID PWR

www.adder.com
RX
LNK USB VID PWR

www.adder.com
RX
LNK USB VID PWR

www.adder.com
RX
LNK USB VID PWR

www.adder.com
RX
LNK USB VID PWR

www.adder.com

INDEX
For details of the XDIP Public REST API, see Appendix 4 - XDIP API. Note:The API control is contained within each receiver. Receivers operate
as separate entities and they are all controlled independently.
3
ADDERLINK XDIP FEATURES
AdderLink XDIP nodes are contained within slimline metal casings measuring just 169 x 112 x 31mm.

A D D E R L I N K

INSTALLATION
LNK USB VID PWR

www.adder.com

Recessed USB port Status indicators

reset Available for These provide visual confirmation of various system functions. See Indicators for

CONFIGURATION
button console use on further details.
See receiver and LNK - indicates the presence of a valid data link.
“Restoring transmitter nodes. USB and VID - indicate active USB and video connections.
a node” on
PWR - indicates the presence of input power (the color also indicates overall mode:
page 20.
TX: Green, RX: Blue, Start of Life: Red, Recovery mode:Yellow).

OPERATION
On TX: [Optional] Feed Data link - either
to a local console connect directly to
another node or
On RX: Feed to the indirectly to multiple
12VDC power
user console others via a supported
port
(PoE option USB HDMI network switch*
available) ports video port (PoE 802.3af supported)

INFORMATION
FURTHER
CONSOLE COMPUTER INDOOR USE ONLY

INDEX
USB HDMI
Audio Audio port video port
* The network switch used must:
line line
out in On TX: Link to the • Support 1Gb transfer rates.
jack jack main computer • Support IGMP (Internet Group Management
On RX: [Optional] Link Protocol) to at least level 2 (preferably level 3).
to a local computer • Have IGMP Fast Leave and IGMP Snooping enabled.
4
SUPPLIED ITEMS

ALL VARIANTS INCLUDE: XDIP-IEC VARIANTS

ALSO INCLUDE:

INSTALLATION
om
der.c
w.ad
ww

VID
PW
R
Power adapter with locking connector and
LN
K
USB
country-specific power cord
K
N
I
L
R
E
D
D
A

CONFIGURATION
AdderLink XDIP node

XDIP-RED VARIANTS
ALSO INCLUDE:

OPERATION
12VDC link cable (2m)
Part number:VSC48

USB cable 2m (type A to B)

HDMI cable 1.5m

INFORMATION
FURTHER
Audio cable 3m
(3.5mm stereo jacks)

INDEX
Information wallet
containing:
Quick setup guide
Eight self-adhesive rubber feet
Safety document

5
OPTIONAL EXTRAS

INSTALLATION
USB cable 2m (type A to B) Audio cable 2m (3.5mm stereo jacks) 12VDC link cable (2m)
Part number:VSC24 Part number:VSC22 Part number:VSC48

Replacement power adapter

with locking connector

CONFIGURATION
Part number: PSU-IEC-12VDC-1.5A

Country-specific power cords

CAB-IEC-AUS (Australia)
CAB-IEC-EURO (Central Europe)
CAB-IEC-UK (United Kingdom)
CAB-IEC-USA (United States)
CAB-IEC-JAPAN (Japan)

HDMI cable 1.5m

OPERATION
Part number: VSCD15 Lockable HDMI cable 1.5m
Part number:VSCD12

Wall/desk mounting kit (plus screws)

Part number: RMK10

INFORMATION
VESA mount kit (plus screws)
Part number: RMK5V

FURTHER
INDEX
Dual rack mount bracket
plus four retaining clamps and bolts
Part number: RMK8
6
Installation
LOCATIONS MOUNTING
Please consider the following important points when planning the position of the Before you begin making connections to the AdderLink XDIP nodes, it is advisable to

INSTALLATION
AdderLink XDIP nodes: first mount the nodes in place, either:
• Situate the transmitter node close to the system to which it will be connected and • On a horizontal surface using the supplied self adhesive feet, or
near to a source of mains power (if powering will not take place via PoE through the • On a vertical surface using the optional wall/desk mounting kit, or
network cable). Place the receiver node in similar close proximity to the peripherals
• Within an optional rack mount bracket.
that it will connect with, plus a source of mains power.
• Consult the precautions listed within the Safety information section.
• Connections do not need to be carried out in the order given within this guide,

CONFIGURATION
however, where possible connect the power in as a final step.

CONNECTIONS
Connections to each node will be determined by the nature of your installation

OPERATION
as well as their intended transmitter or receiver designations.
All connections are grouped into five main areas:

CONSOLE COMPUTER INDOOR USE ONLY

INFORMATION
FURTHER
Power Audio Console Computer Link
connection connections connections connections connection
(USB port also
available on the
front panel)

INDEX
The pages that follow discuss the various connections.

7
Computer connections
Computer connections are always made at the transmitter node, but can also optionally
be made at the receiver node, where channel switching between local and remote
computer sources is required.
Notes:
• When a local computer is connected to a receiver node, it can only be accessed from that

INSTALLATION
receiver, no other receivers can gain access to it.
• Video resolutions up to 1920 x 1200 @ 60Hz are supported.
• HDMI audio is not supported; please use the audio in/out ports to transfer audio signals.
To make computer connections
1 Insert the supplied HDMI cable between the HDMI video socket (in the COMPUTER
section) and the video output port on the computer.

CONFIGURATION

HDMI offers the great advantage that it is a straightforward task to convert its signals
to and from other common video formats (DisplayPort, DVI and VGA) - See page 9.
2 Insert the supplied USB type A to type B cable between the USB socket (in the
COMPUTER section) and a vacant USB port on the computer.

CO
MP
UT
ER

OPERATION
IND
OO
R US
EO
NL
Y

USB connection
to computer

INFORMATION
FURTHER
HDMI video
connection to
computer

INDEX
8
Video format conversion
One of the many advantages offered by the HDMI (High Definition Multimedia Interface)
standard is the ease with which it can be converted into- and out of- numerous other
video formats, including single link DVI-D, DisplayPort and VGA (see next page).
Note: HDMI conversion cables and adapters (apart from the Adder DVA) are not available from
Adder, but are widely sold elsewhere.

INSTALLATION
DVI monitor
or video port
on computer
DisplayPort
monitor

HDMI < > DVI

CONFIGURATION
HDMI to DisplayPort
(active)
HDMI to
DVI adapter

HDMI to
DisplayPort
HDMI video active adapter
cable

OPERATION
To
XDIP
‘CONSOLE’
or ‘COMPUTER’
ports
DisplayPort
To video port on
XDIP computer
‘CONSOLE’

INFORMATION
video port

FURTHER
DisplayPort to HDMI
DisplayPort/HDMI adapters - active or passive? (passive)
The choice of whether to use an active or passive adapter depends primarily
upon the signal source. DisplayPort
If your computer outputs Dual-mode DisplayPort (also known as DP++), then to HDMI
passive adapter
you can use a (cheaper) passive adapter to derive a Single-link HDMI feed.

INDEX
Conversely, when converting from HDMI to DisplayPort (to use with a
DisplayPort monitor), the adapter will always be active. Note: Adapters are not
bi-directional, specific models are required to go from DisplayPort to HDMI and
vice versa.
To
XDIP
‘COMPUTER’
video port 9
Video format conversion (continued)
XDIP
‘CONSOLE’
video port

HDMI to VGA

INSTALLATION
(active adapter)

HDMI to
VGA (active)
VGA video
adapter

CONFIGURATION
port on
computer

To
VGA

OPERATION
monitor VGA link
cable
CO
MP
UT
ER

VGA to HDMI
DIS
PLA
Y

INFORMATION
FURTHER
Adder DVA
VGA to DVI
adapter

HDMI to DVI
adapter

INDEX
To
XDIP
‘COMPUTER’
video port

10
Console connections
Console connections (video monitor and/or USB peripherals) are always made at the receiver node, but can also optionally be made at
the transmitter node, if local control (or monitoring) of the computer is required in addition to remote control.
Notes:
• Video resolutions up to 1920 x 1200 @ 60Hz are supported.

INSTALLATION
• HDMI audio is not supported; please use the audio in/out ports to transfer audio signals.
To make console connections
1 Insert the supplied HDMI cable between the HDMI video socket (in the CONSOLE section) and the video port on your monitor.

HDMI offers the great advantage that it is a straightforward task to convert its signals to and from other common video formats
(DisplayPort, DVI and VGA) - See page 9.
2 Connect the USB leads from your mouse and keyboard to the two sockets on the rear panel. The single socket on the front panel is
also available (all three USB ports operate in the same manner).

CONFIGURATION
CO K
NS I
N
OL L
E R
E
D
D
A

CO

OPERATION
USB
connections
from peripheral
devices
USB
connections
from peripheral
HDMI video
device

INFORMATION
connection to

FURTHER
monitor

INDEX
11
Audio connections Link connection
The transmitter and receiver nodes can transfer CD-quality stereo audio (16-bit As required, links between nodes can be made in two main ways, either:
sampling at 48kHz) in both directions. Headphones are supported up to 32 Ohms • Directly between two nodes, using a single cable up to 100 meters in length,
impedance.
Minimum cable specification: CAT5e, S/FTP preferred,
Note: HDMI audio is not supported. Audio transfer is handled exclusively by the audio in/out ports.
or

INSTALLATION
To make audio connections • Via a network switch to allow interaction between receiver/transmitter combinations.
1 Connect your audio input (e.g. line out from the local computer, etc.) to the audio
Minimum network switch specifications:
input (right hand) 3.5mm socket labeled on the rear panel.
• 1Gb transfer rates.
2 Connect your audio output (e.g. speakers or headphones, etc.) to the audio output
• IGMP (Internet Group Management Protocol) to at least level 2 (preferably level 3)
(left hand) 3.5mm socket labeled on the rear panel.
in order to allow efficient multicasting while keeping network bandwidth low.
• IGMP Fast Leave and IGMP Snooping must be enabled.

Optional network switch specification:

CONFIGURATION
• PoE 802.3af - The nodes also support the Power over Ethernet standard to allow
operation without separate power adapters when used with a supporting network
12V
switch.
1.5
A
To make a link connection
1 Insert a standard network cable into the socket on the far right of the rear panel.
2 Connect the other end of the cable either directly to another node, or to a suitable
network switch. OM

OPERATION
PU
TER

Audio output
Audio input IND
OO
R US
EO
NL
Y

INFORMATION
Link cable

FURTHER
either directly
to another node
or to a network
switch

INDEX
12
Power connection
Each node can be powered using its supplied power adapter or alternatively via the
Ethernet link connection, when used with network switches which support the PoE
802.3af standard. The power adapters supplied with the nodes use locking-type plugs to
help prevent accidental disconnections; please follow the instructions shown on the right
when disconnecting a power adapter.

INSTALLATION
To connect the power adapter To disconnect the power adapter
1 Attach the output plug of the supplied power adapter to the 1 Isolate the power adapter from the mains supply.
power input socket on the left side of the rear panel. As you 2 Grasp the outer body of the power adapter plug
insert the plug, pull back slightly on the outer body to assist where it connects with the node.
the locking mechanism until the plug is fully inserted.
3 Gently pull the body of the outer plug away from
the node. As the body of the plug slides back, it will
12V
release from the socket and you can fully withdraw

CONFIGURATION
1.5 12V
A
the whole plug. 1.5
A

Gently pull back the plug outer

From the body to release the lock
power adapter

OPERATION
2 Insert the IEC connector of the supplied country-specific power cord to the socket of
the power adapter.

IMPORTANT: Please read and adhere to the electrical safety information

given within the Safety information section of this guide. In particular, do not

INFORMATION
use an unearthed power socket or extension cable.

FURTHER
Note: Both the nodes and the power supplies generate heat when in operation and will
become warm to the touch. Do not enclose them or place them in locations where air cannot
circulate to cool the equipment. Do not operate the equipment in ambient temperatures
exceeding 40 degrees Centigrade. Do not place the products in contact with equipment whose
surface temperature exceeds 40 degrees Centigrade.

INDEX
3 Connect the power cord to a nearby mains supply socket.

13
Configuration
INITIAL CONFIGURATION To use the configuration wizard
To streamline the initial installation procedure, AdderLink XDIP nodes use a Note: If you are creating a transmitter to add into an existing installation, skip to page 18.

INSTALLATION
configuration wizard to guide you through the necessary stages. For the simplest 1 Connect your various AdderLink XDIP nodes as discussed in the Installation section.
installations, this may be all that is necessary to completely tailor the nodes to your
2 Power on all nodes. Nodes that are currently in their Start of Life state will show
requirements. However, for more complicated installations you may also need to access
their front panel PWR indicators in red (configured transmitters show green while
the main Admin menu (see page 21) once the initial configuration is complete.
receivers show blue). To return a node to its Start of Life state, you need to Restore it,
AdderLink XDIP configuration is primarily driven via the receiver(s). During the see page 20.
initial configuration and subsequent post-installation alterations, a transmitter can be
3 Using a monitor, keyboard and mouse connected to the Console ports of an intended
configured via a receiver, but not vice versa. Also, one receiver cannot configure another

CONFIGURATION
receiver node, you should see the following opening page:
receiver. Where two or more receiver nodes will be required, run the wizard from the
first receiver node and, once complete (including all transmitter nodes), move to the
console of the next required receiver node and run the configuration wizard again from
there. Transmitters configured in the first run can be associated with multiple receivers,
as required. Welcome
Please choose your language and keyboard layout.

Navigating the configuration wizard, OSD and Admin menu English

The AdderLink XDIP user interface has been carefully designed to be easily navigated

OPERATION
by either mouse, keyboard or a combination of both. gb

When using the mouse, you merely need to point and click on screen items. As the
OK
mouse hovers over a screen item, if it is clickable it will become highlighted.
When using the keyboard to navigate, use the following keys:
• Tab key - To move forward between sections.
• Shift + Tab keys - To move backward between sections.

INFORMATION
00:0F:58:02:DF:3B | v1.05D
• Arrow keys - To change between the options within a section.

FURTHER
• Enter key - To select the highlighted option. Note:The node’s PWR indicator should be red at this stage. If not, restore the node to its
• Esc key - To exit the current page. default settings (see page 20).
On a receiver node, to display the OSD: 4 If necessary, change the language and keyboard layout.
• Press CTRL + ALT + C * 5 Click OK to continue.
Once the OSD is displayed, to enter the Admin menu:
• Select the icon in the top right corner of the page.

INDEX
continued
To view explanatory text about the page that you are viewing:
• Click the icon in the top right corner of the page.
See page 31 for more details about keyboard navigation during operation.

* Note:The standard hotkey combinations can be changed. See page 22.

14
INITIAL CONFIGURATION (continued)
You will now be given a choice of turning this Start of Life node into either a receiver If you chose the RECEIVER option, you will now be given the opportunity to enter
or a transmitter: details for the node to which your console peripherals are currently connected:
SETUP - Receiver or Transmitter? SETUP - Basic Information
Is this node a receiver or transmitter? After restoring to defaults Enter the names, descriptions and admin password for this
you can change this in the future. receiver.

INSTALLATION
Receiver Name Receiver 1

Description
Receiver Description

Computer Name Local Computer

Description
Computer Description

New Admin Password Password for Node Configuration

CONFIGURATION
Confirm Admin Password Password for Node Configuration
RECEIVER TRANSMITTER New Access Password Password for User Access

Confirm Access Password Password for User Access

Cancel OK

Note:When using the configuration wizard to create a full installation, it is quicker and more 7 Enter the details for this receiver, including the admin password (required to
efficient to configure all transmitters via a node that will become a receiver, rather than administer the configuration details) and an access password (required for user access).

OPERATION
configuring each of the intended transmitters separately. The Computer Name/Description fields refer to a local computer connected directly to
6 Choose the required setting: this receiver, if present.
• If you are setting up a mixture of receiver(s) and transmitter(s), click Note: Passwords can be left blank, but this is not recommended.
the RECEIVER option. 8 Click OK.
• If you are creating a transmitter to add into an existing installation, click
the TRANSMITTER option. See page 18.
continued

INFORMATION
FURTHER
INDEX
15
INITIAL CONFIGURATION (continued)
You will now see a list of all discovered nodes. If an entry shows SoL (Start of Life) 10 Enter the details for this transmitter, including two separate passwords:
then it is unconfigured (that node’s PWR indicator will also show red). Otherwise, any • The Admin Password is required to administer the configuration details only,
discovered transmitter node, that is already configured, will show TX:
• The Access Password allows you to restrict who is allowed to connect to this
SETUP - Channel Selection transmitter. When the Access Password is set, a user will be prompted to enter

INSTALLATION
Select which nodes to add as channels.‘SoL’ marks nodes that are
yet to be configured and ‘TX’ denotes available transmitters.
it when first attempting to add this transmitter node to their receiver node’s
channels list; if the Access Password is left blank, there will be no access restrictions.
# Name Description
Note:The Name and Description fields for each entry cannot be left blank.
TX Transmitter 1 Description
SoL AdderLink XDIP 02DF3B Description
11 Click OK. The discovered nodes will be again listed, showing any changes you have
made to the name(s) and description(s):

SETUP - Channel Selection

CONFIGURATION
Select which nodes to add as channels.‘SoL’ marks nodes that are
yet to be configured and ‘TX’ denotes available transmitters.

# Name Description
1 Transmitter 1 Description
TX Transmitter 2 Description

BACK NEXT

Notes

OPERATION
• If you are adding several nodes at once and need to identify a particular node, click the
icon to flash the front panel indicators of the chosen node in the list.
• If nodes have been added since displaying the list, click the icon to refresh the list.
9 Click an entry marked SoL to configure it as a transmitter: BACK NEXT

SETUP - Basic Information

Enter the name, description, and admin and access password for 12 Repeat steps 9 to 11 for each listed SoL node.

INFORMATION
this transmitter.
13 Ensure that all the transmitters (8 maximum), to which you wish to connect from this

FURTHER
receiver, show a number in the left hand column. If an entry shows TX, it is yet to be
Transmitter 2
connected. Click on the entry to connect it with this receiver; if an access password
Transmitter Name
Description
is set on the transmitter, you will be asked to enter it. Once successfully connected,
Transmitter Description
the TX for the entry will change to a number.
New Admin Password Password for Node Configuration
14 When all transmitters have been connected, click NEXT.
Confirm Admin Password Password for Node Configuration

New Access Password Password for User Access

Confirm Access Password Password for User Access

INDEX
continued
Cancel OK

16
INITIAL CONFIGURATION (continued)
15 You can now optionally change the order of transmitters in the channel list. Click, 17 The receiver will now show the Channel List:
hold and drag an entry to the required slot:
Receiver 1
Description
SETUP - Customise the Channel Order
Drag and drop the channels into your preferred order.

INSTALLATION
# Name Description
# Name Description 0 Local Computer Description
1 Transmitter 1 Description 1 Transmitter 1 Description
2 Transmitter 2 Description 2 Transmitter 2 Description
3 3
4 4
5 5

CONFIGURATION
6 6
7 7
8 8

1 2 BACK DONE

From here you can choose between a local computer (if connected to your receiver)
16 When all transmitters are in the required order, click DONE. or any of the associated transmitters. See page 31 for details about operation.

OPERATION
INFORMATION
FURTHER
INDEX
17
INITIAL CONFIGURATION (continued)
To add a new transmitter
Use this procedure to configure a new Start of Life node into a transmitter for inclusion You will now be given a choice of turning this Start of Life node into either a receiver
within an existing installation: or a transmitter:
1 Connect your console devices (video monitor, USB keyboard and/or mouse) plus SETUP - Receiver or Transmitter?
power input to the new Start of Life node (as discussed in the Installation section).

INSTALLATION
Is this node a receiver or transmitter? After restoring to defaults
you can change this in the future.

For this procedure the new node can be configured either in isolation or fully linked
into your XDIP installation, as required.
2 You should see the following opening page:

CONFIGURATION
Welcome
Please choose your language and keyboard layout.
RECEIVER TRANSMITTER

English

gb

OK
5 Click the TRANSMITTER option.You can now enter the details for the node to which

OPERATION
your console peripherals are currently connected:
SETUP - Basic Information
Enter the name, description, and admin and access password for
this transmitter.
00:0F:58:02:DF:3B | v1.05D

3 If necessary, change the language and keyboard layout.

Note:The node’s PWR indicator should be red at this stage. If not, restore the node to its Transmitter Name Transmitter 2

INFORMATION
default settings (see page 20). Transmitter Description
Description

FURTHER
4 Click OK to continue. New Admin Password Password for Node Configuration

Confirm Admin Password Password for Node Configuration

New Access Password Password for User Access

Confirm Access Password Password for User Access

Alternative shortcut for adding a new transmitter
1 Connect your new node fully into the XDIP installation.
2 From a receiver, enter the OSD and then enter the Admin menu. Cancel OK

3 Choose the Setup Channels page and click the icon in the lower right corner.

INDEX
4 Click the new SoL entry in the list.
5 Configure the necessary transmitter details and click OK.
6 Click the Back button to return to the Channels List and, if necessary, adjust the
position of the new transmitter within the list.
7 Click the icon to exit to the OSD channel list. continued
18
INITIAL CONFIGURATION (continued)
6 Enter the details for this transmitter, including two separate passwords: 10 Click the icon in the lower right corner to list all available transmitter (and SoL) nodes:
• The Admin Password is required to administer the configuration details only,
ADMIN - Channel Selection
• The Access Password allows you to restrict who is allowed to connect to this Select which nodes to add as channels.‘SoL’ marks nodes that are yet to be configured and ‘TX’
denotes available transmitters.
transmitter. When the Access Password is set, a user will be prompted to enter it RECEIVER

INSTALLATION
when first attempting to add this transmitter node to their receiver node’s channels Receiver 1 Select which nodes to add as channels
list; if the Access Password is left blank, there will be no access restrictions. General # Name Description
The Access Password is also used by external systems when creating matrix control OSD Settings 1 Transmitter 1 Description
installations. TX Transmitter 2 Description
Setup Channels
Note:The Name and Description fields for each entry cannot be left blank. Manage Ports
7 The basic configuration for this node is now complete but it still needs to be Advanced
registered within the XDIP network. If the new node is not already physically linked

CONFIGURATION
Software Upgrade
into your XDIP installation, connect it now (see page 12).
8 Using the console peripherals connected to a receiver node within the installation,
enter the receiver’s OSD: Press CTRL + ALT + C *
9 Click the icon in the top right corner and then choose the Setup Channels page:
Back
ADMIN - Channel List
Drag and drop the channels or use the return and arrow keys to reorder the list. Identify, configure

RECEIVER
or delete the selected channels or add other transmitters to the channels list.
11 Move the highlight to your new node and select it so that the TX prefix becomes a
channel number (the shade of the highlight will also change). Repeat this step for any

OPERATION
Receiver 1 Administer the Selected Channels
other new nodes that need to be included.
General # Name Description
1 Transmitter 1 Description
12 Click the Back button to return to the Channel List:
OSD Settings
2 ADMIN - Channel List
Setup Channels Drag and drop the channels or use the return and arrow keys to reorder the list. Identify, configure
3 or delete the selected channels or add other transmitters to the channels list.
Manage Ports RECEIVER
4
Advanced 5 Receiver 1 Administer the Selected Channels

INFORMATION
Software Upgrade 6 General # Name Description

FURTHER
7 OSD Settings 1 Transmitter 1 Description
8 2 Transmitter 2 Description
Setup Channels
Add Channels 3
Manage Ports
4
Advanced 5
Software Upgrade 6
7
8

INDEX
Add Channels

Your new node is now integrated and ready to be selected. Click the icon in the top
* Note:The standard hotkey combinations can be changed. See page 22. right corner to exit from the Admin menu. See page 31 for details about Operation.
19
RESTORING A NODE
In order to obtain the full benefit of the configuration wizard when creating a new
installation, it may be necessary to restore the default settings to your XDIP nodes.
Note: A restore operation will reset all configuration settings and cannot be undone. • [Transmitters] From any connected receiver node, display the channel list and then click
A restore operation can be invoked in various ways: the icon in the top right corner. If requested, enter the admin password and then
• [Receivers] Display the channel list and then click the icon in the top right corner. If choose the Setup Channels page.

INSTALLATION
requested, enter the admin password and then choose the Software Upgrade page. • Click the icon shown next to the name of the transmitter that you wish to restore,
Click the Restore button: then choose the Software Upgrade page and click the Restore button:

ADMIN - Software Settings and Upgrade ADMIN - Software Settings and Upgrade
Review the software versions present on this node. Upgrade, switch to the alternative software Review the software versions present on this node. Upgrade, switch to the alternative software
version, restore or reboot this node. version, restore or reboot this node.
RECEIVER TRANSMITTER

Receiver 1 Software Settings and Upgrade Transmitter 2 Software Settings and Upgrade

CONFIGURATION
General Bootloader v1.04 - 18:15 30/08/19 Recovery v1.04 - 18:15 30/08/19 General Bootloader v1.05D - 18:15 30/07/19 Recovery v1.05D - 18:15 30/07/19
Active v1.05D - 13:37 21/04/20 Alternate v1.0021 - 18:15 19/06/17 Manage Ports Active v1.05D - 18:15 30/07/19 Alternate v1.05D - 18:15 30/07/19
OSD Settings
Setup Channels Select Upgrade File Check USB Media Device Upgrade Advanced Select Upgrade File Select File Upgrade

Manage Ports Software Upgrade

Switch to Alternative Version Switch Switch to Alternative Version Switch
Advanced
Software Upgrade Restore Default Settings Restore Restore Default Settings Restore

Reboot Node Reboot Reboot Node Reboot

OPERATION
• [Receivers or transmitters] Use a narrow implement
RECOVERY - Software Settings and Upgrade
Review the software versions present on this node. Upgrade, (such as a straightened out paper clip) to press and

INFORMATION
switch to the alternative software version, restore or reboot this
hold the recessed reset button on the front panel

FURTHER
node.

Bootloader: v1.05D - 18:15 30/07/19 Recovery: v1.05D - 18:15 30/07/19 (while power is applied) for just over ten seconds
Preferred: v1.05D - 18:15 30/07/19 Alternate: v1.05D - 18:15 30/07/19 until the front panel PWR indicator flashes; then
release the button and wait for the node to
Select Upgrade File Select File Upgrade reboot and display the Recovery page. Click the
Restore button.
Switch to Alternative Version Switch
Notes:
Restore Default Settings Restore • The reset button is within the hole to the left of the

INDEX
USB socket.
Reboot Node Reboot • You will need a minimum of a monitor and either
keyboard/mouse connected to the node being
restored.

20
ADMIN MENUS
Once an AdderLink XDIP installation has undergone its initial configuration, if necessary The various parts of the Admin menu are detailed on the following pages:
you can make further alterations using the Admin menu. An Admin menu is accessible Receiver node Transmitter node
via each receiver, wherein changes can be made to that receiver and/or any of the linked
transmitters. General Settings this page General Settings page 27
OSD Settings page 22 Manage Ports page 28
To enter the Admin menu

INSTALLATION
1 From any connected receiver node, enter the receiver’s OSD: Press CTRL + ALT + C* Setup Channels page 27 Advanced page 29
2 Click the icon in the top right corner to display the receiver’s General Settings Manage Ports page 23 Software Upgrade page 30
page (see below), you will be requested to enter an admin password. Advanced page 24

Most pages have an Apply button which must be clicked after making changes in order Software Upgrade page 26
to save them. Alternatively, you can select the Cancel button to exit a page without
retaining your latest changes.

CONFIGURATION

To exit any Admin page, click the icon in the top right corner.

To view the configuration details for a transmitter node, see page 27.
* Note:The standard hotkey combinations can be changed, see page 22

Receiver node settings

General Settings page

OPERATION
When you enter the Admin Menu, the first page to be displayed will be the General Name and Description
Settings page for the receiver to which you are directly connected. This page provides These tags are useful for differentiation purposes when numerous nodes are being used.
basic information for this node: Use the Receiver Name and Receiver Description fields to change them.
ADMIN - General Settings Time and Date
Review this node’s general information and update its details.
These are shown only if access to an NTP server is available. The current time and date
RECEIVER
are frozen within this page and do not automatically update.
Receiver 1 Receiver General Settings

INFORMATION
Serial Number

FURTHER
General Name Node Name Description Description Shows the unique hardware identity applied to this node.
OSD Settings Uptime 25 mins Serial Number 1701A0000001
MAC Address 00:0F:58:02:DF:3A Software Version 1.05D MAC Address
Setup Channels
Receiver Name Node Name Shows the unique network identity applied to this node.
Manage Ports Receiver Description Description
Software Version
Advanced
Admin password Change Shows the current main version of internal firmware.
Software Upgrade
Access password Change Receiver Name and Receiver Description
These fields allow you to change the name and description tags for this node.

INDEX
Admin Password
Allows you to change the administration password (that protects this menu).
Cancel Apply
Access Password
Allows you to change the password that restricts access to this node by transmitters and
also external control systems.
21
OSD Settings page
This page contains all settings related directly to the On Screen Display menu:
Language
ADMIN - OSD Settings
Update this node’s OSD timeout and hotkeys. Determines the language used for all OSD menu text. Options are: English, Français,
RECEIVER Español and Deutsch.
Configure OSD Settings Keyboard

INSTALLATION
Receiver 1
General Language English
Determines the layout styles used for the keyboard attached to the receiver. Options
OSD Settings Keyboard gb include: gb, us, fr, de and es.
Setup Channels OSD Mouse Launch None OSD Mouse Launch
Hotkeys Left Ctrl Left Alt Allows you to optionally choose mouse button combinations that will launch the OSD
Manage Ports
Next Channel Hotkey Left Ctrl + Left Alt + Letter menu.
Advanced Previous Channel Hotkey Left Ctrl + Left Alt + Letter
Hotkeys

CONFIGURATION
Software Upgrade OSD Hotkey Left Ctrl + Left Alt + c
Disconnect Hotkey Left Ctrl + Left Alt + x Allows you to change the two main hotkeys which are used to indicate that you wish to
OSD Timeout 1 min communicate with the receiver itself rather than any of the connected computers.
Next and Previous Channel Hotkey
Allows you to define keyboard buttons which, when used together with the chosen main
Cancel Apply hotkeys, will move to the next or previous channel (based on the receiver node’s channel
list). Options include Tab, Backspace, Enter, Space, the arrow keys or any keyboard Letter
(which needs to be defined in the white box on the right). Note: If the Letter option is
selected, but no letter is defined within the white box, then the functionality is disabled.

OPERATION
OSD Hotkey
Defines the key which, when used together with the chosen main hotkeys, will display the
OSD menu.
Disconnect Hotkey
Defines the key which, when used together with the chosen main hotkeys, will
disconnect the receiver from the currently chosen channel.

INFORMATION
OSD Timeout

FURTHER
Defines the period of inactivity (in whole minutes) that should pass before the OSD
menu is automatically exited (0 disables the OSD timeout). Note:The automatic timeout
from the Admin menu is fixed at 15 minutes.

INDEX
22
Manage Ports page
All settings within these pages relate to the video monitor, USB devices and/or local
computer that are connected to this receiver node.

ADMIN - Port Settings ADMIN - Port Settings ADMIN - Port Settings

Review
Review this node’s local computer, USB and video port information and change its this node’s local computer, USB and video port information and change its settings.
settings. Review this node’s local computer, USB and video port information and change its settings.

RECEIVER RECEIVER RECEIVER

INSTALLATION
Receiver 1 Local Video Receiver 1
USB Local Video USB Receiver 1 Local Video USB
General Computer Name General
Computer Name Enable Video Output General Connected Devices ABC Ltd USB Hub Details
OSD Settings Computer Description OSD Settings
Description Connected Monitor DEL 61462OSD Settings
Details HAL Inc. USB Keyboard Details

Connected MonitorSetup Channels

Setup Channels Setup Channels Choose the video EDID that will be XYZ USB Mouse Details
presented to the attached computer
Manage Ports Manage Ports Manage Ports
Advanced

CONFIGURATION
Advanced Advanced
Software Upgrade Software Upgrade Software Upgrade

Computer Name and Computer Description Cancel Connected

Apply Monitor Cancel Apply Connected Devices Cancel Apply
These tags are useful for differentiation purposes when Lists the basic details for the monitor connected to the Lists the USB devices which are currently connected
numerous nodes are being used. These fields allow you to console video output of this receiver node. Click on to this receiver node. Click the Details button to view

OPERATION
change the name and description tags for the computer that the Details button to view more information about the more information about the device.
is directly attached to this receiver node (shown on the OSD connected video monitor:
as channel 0).
Monitor Details
Manufacturer: DEL
Model ID: 61462
Serial Number: F525M098046L

INFORMATION
Manufacture Date (week/year): 37/2010

FURTHER
EDID Version: 1.3
Preferred Resolution: 1920x1080p@60Hz 148.50MHz

1920x1080p@60Hz 148.50MHz
1152x864p@75Hz 108.00MHz
1280x1024p@60Hz 108.00MHz
EDID Details
1600x900p@60Hz 97.75MHz
1920x1080p@60Hz 138.50MHz
720x400p@70Hz 28.32MHz

OK

Choose the video EDID....

INDEX
Allows you to choose to rely upon the Automatic EDID
configuration for the connected monitor or to manually
select one of the listed modes.

23
Advanced page
The items within these pages relate to the network settings, network test, diagnostic
tools and statistics for the chosen receiver node.

ADMIN - Network Settings ADMIN - Network Diagnostics

Review this node’s network information. XDIP selects IP addresses automatically using DHCP (when Ping a selected node or run IGMP tests on this node.
available) or Link-Local addresses (169.254.x.x) on private networks without DHCP.
RECEIVER RECEIVER

INSTALLATION
Receiver 1 Network Info Network Test Diagnostics Statistics Receiver 1 Network Info Network Test Diagnostics Statistics
General Dynamic IP Address 192.168.1.34 Static IP Address 0.0.0.0 General
Select a Node Ping
OSD Settings Dynamic Netmask 255.255.255.0 Static Netmask 255.255.255.0 OSD Settings
Dynamic Gateway 192.168.1.1 Static Gateway 192.168.20.1
Setup Channels Setup Channels
MAC Address 00:0F:58:02:DF:3A
Manage Ports Manage Ports
DHCP Server 91.134.24.29
Select a Node IGMP
Advanced NTP Server 93.0.123.145 Advanced

CONFIGURATION
Software Upgrade DNS Address 128.0.124.53 Software Upgrade
Enable Remote Control

Cancel Apply

Dynamic IP details This page provides basic network testing tools to allow you to test and confirm the link
between this receiver node and any chosen transmitter node.

OPERATION
Dynamic IP address details are configured automatically in either of two ways:
• With the use of a DHCP server, if one is available during configuration, or Choose a node and click the Ping button to obtain packet loss and speed details.
• Using Link-Local addresses (169.254.x.x). Choose a transmitter node and click the IGMP button to view test results.
Note: IGMP Fast Leave and Snooping must be supported and enabled on your network switch,
Static IP details otherwise these tests will produce a ‘Failed’ result. A ‘Marginal’ result indicates that packets are
In addition to the main Dynamic IP address used by each receiver, a separate set still arriving after an allotted cut off period.
of static IP address details are available for use when an XDIP installation will be Results are provided in the manner shown below:
externally controlled. The static IP address provide a consistent control channel into

INFORMATION
FURTHER
the receiver, protected by the Access Password. ADMIN - Network Diagnostics
Ping a selected node or run IGMP tests on this node.

Enable Remote Control RECEIVER

When ticked, this function allows the receiver to be controlled by external systems Receiver 1 Network Info Network Test Diagnostics Statistics
in order to coordinate the actions of multiple XDIP units; either using the Adder
General
XDIP Public REST API or by web browser access to the OSD on the chosen receiver. Transmitter 1 Ping
OSD Settings
See pages 3, 32 and 38 for details.
Packet Loss 0% Minimum Response Time 0.178 ms
Setup Channels
Average Response Time 1.441 ms Maximum Response Time 6.478 ms
Manage Ports

INDEX
Advanced Transmitter 1 IGMP

Software Upgrade IGMP Version 3

IGMP Fast Leave Status Marginal IGMP Snooping Status Passed
Multicast Leave Duration 3410.059 ms

24
Advanced page (continued)

ADMIN - Diagnostic Tools Settings ADMIN - Statistics

Change the settings for this node’s diagnostic tools. Review this node’s video and audio information.

RECEIVER RECEIVER

Receiver 1 Network Info Network Test Diagnostics Statistics Receiver 1 Network Info Network Test Diagnostics Statistics

INSTALLATION
General Remote Logging Address 0.0.0.0 General Video Performance Audio Performance
OSD Settings Severity Level 5 OSD Settings Frame Width (px) 1920 Encoding Linear
Frame Height (px) 1080 Bits per Sample 16
Setup Channels Enable Remote Logging Setup Channels
Frames per Second 60 Samples per Second 48000
Manage Ports Capture Log to USB Trigger Manage Ports
Bit Rate (Mbps) 43.380 Bit Rate (Mbps) 1.615661
Advanced Remote Support 22 Enable Advanced Underflows 0
Video Errors
Software Upgrade Software Upgrade Packet loss 0 Overflows 0

CONFIGURATION
Dropped Images 0 Audio Errors
Decode Errors 0 Packet loss 0
Discontinuities 0

Cancel Apply

Remote Logging Address This page provides statistical details regarding the video and audio performance.
Enter a valid IP address for a syslog server on the local network where status logs

OPERATION
can be sent.
Severity Level
Defines the level of messages that will be logged (according to RFC5424). Level
5 (Notice: normal but significant condition) is the default setting; XDIP currently
supports levels 1 to 7. Choosing levels 6 (Informational) or 7 (Debug) will cause
larger numbers of lesser events to also be logged, with a potential impact to
overall performance. These levels should only be used if working with the support

INFORMATION
team to diagnose a specific issue.

FURTHER
Enable Remote Logging
Tick to send log files to the chosen Remote Logging Address.
Capture Log to USB
Click the Trigger button to save the activity log to a local USB memory stick. The
resulting compressed file can then be sent to Adder support when diagnosing an
issue.

INDEX
Remote Support
When using the Adder remote server, this option determines which port will be
used. Multiple options are offered in case one or more ports are blocked by your
firewall.
Note:This option should only be enabled when requested by Adder, for support purposes.

25
Software Upgrade page
The items within this page relate to the software settings, restore/reboot and firmware
upgrade option for the chosen receiver node.
Firmware details
ADMIN - Software Settings and Upgrade
Review the software versions present on this node. Upgrade, switch to the alternative software Lists the current and recovery Bootloader versions plus the Active image that is currently
version, restore or reboot this node.
RECEIVER running as well as the Alternate (the previously active) image version details.

INSTALLATION
Receiver 1 Software Settings and Upgrade Select Upgrade File
General Bootloader v1.04 - 18:15 30/08/19 Recovery v1.04 - 18:15 30/08/19 Any valid firmware upgrade files held (only in the root menu) on a memory stick in one
OSD Settings Active v1.05D - 13:37 21/04/20 Alternate v1.0021 - 18:15 19/06/17 of the USB sockets will be listed here (if necessary click the icon to update after
insertion). Select the required file name and click the Upgrade button. The new firmware
Setup Channels Select Upgrade File Check USB Media Device Upgrade
will be made current and the pre-existing code moved to the recovery/alternate location.
Manage Ports
Switch to Alternative Version Switch Switch to Alternative Version
Advanced

CONFIGURATION
Allows you to change back to the previous firmware version that was running before the
Software Upgrade Restore Default Settings Restore
last upgrade.
Reboot Node Reboot Restore Default Settings
Click to restore this receiver to its default Start of Life (SoL) condition.
Note: A restore operation will reset all configuration settings and cannot be undone.
Reboot Node
Click to reboot this receiver.

OPERATION
Supported file systems
When using USB memory sticks, the following file systems are supported:
• FAT
• NTFS
• Non-journaled HFS+

INFORMATION
FURTHER
INDEX
26
Setup Channels page
Transmitter nodes can be configured via the Setup Channels page, accessible via any receiver. (Enter the
receiver’s OSD: Press CTRL + ALT + C*, click the icon in the top right corner and then choose the
Setup Channels page). Here you can:
• Change the channel order - drag and drop a node entry into the required slot (or use the arrow keys).
• Add a transmitter node to the list - click the icon in the lower right corner.

INSTALLATION
• Flash the front panel indicators of any transmitter node - click the node’s icon.
• Remove a transmitter node from the list - click the node’s icon.
• Configure a transmitter node - click the node’s icon: Transmitter node settings
1 From any connected receiver node, enter the receiver’s OSD: Press CTRL + ALT + C*,
ADMIN - Channel List then click the icon in the top right corner.
Drag and drop the channels or use the return and arrow keys to reorder the list. Identify, configure

RECEIVER
or delete the selected channels or add other transmitters to the channels list. 2 Choose the Setup Channels page and click the icon shown next to the name of the
transmitter that you wish to configure.

CONFIGURATION
Receiver 1 Administer the Selected Channels
3 You will be requested to enter the admin password. The transmitter’s General Settings
General # Name Description
page will be shown.
OSD Settings 1 Transmitter 1 Description
2 Transmitter 2 Description
Note: All Admin menu pages related directly to transmitter configuration use a green highlight
Setup Channels
3ADMIN - Channel List to match the color of the PWR indicator of nodes when they are in transmitter mode.
Manage Ports Drag and drop the channels or use the return and arrow keys to reorder the list. Identify, configure
4or delete the selected channels or add other transmitters to the channels list.
RECEIVER
Advanced 5
General Settings page
Receiver
Software 1Upgrade 6Administer the Selected Channels This page provides basic information for this node:
Admin Login
General 7# Name TRANSMITTERDescription Name and Description

OPERATION
OSD Settings 81 Transmitter 1
Transmitter 2
Description These tags are useful for differentiation purposes when numerous nodes are being used.
2 Transmitter 2
Admin password Description
Password for Node Configuration Add Channels Use the Transmitter Name and Transmitter Description fields to change them.
Setup Channels
3
Manage Ports Cancel OK Time and Date
4
Advanced These are shown only if access to an NTP server is available. The current time and date
5
are frozen within this page and do not automatically update.
Software Upgrade 6
ADMIN
7 - General Settings Serial Number

INFORMATION
Review this node’s general information and update its details.
Shows the unique hardware identity applied to this node.

FURTHER
8
TRANSMITTER
Add Channels MAC Address
Transmitter 2 Transmitter General Settings
Shows the unique network identity applied to this node.
General Name Node Name Description Description
Uptime 25 mins Serial Number 1701A0000001 Software Version
Manage Ports
MAC Address 00:0F:58:02:DF:3A Software Version 1.05D Shows the current main version of internal firmware.
Advanced
Transmitter Name Transmitter 2
Software Upgrade
Transmitter Name and Transmitter Description
Transmitter Description Description
These fields allow you to change the name and description tags for this node.

INDEX
Admin password Change Admin Password
Access password Change Allows you to change the administration password (that protects this menu).
Access Password
Allows you to change the password that restricts access to this node by receivers and
also external control systems.
Cancel Apply
* Note:The standard hotkey combinations can be changed. See page 22. 27
Manage Ports pages
To access these pages: From a receiver, enter the OSD menu: Press CTRL + ALT + C hotkeys,
then click the icon to show the Admin menu. Choose the Setup Channels page, click the
icon for the required transmitter node and then click the Manage Ports option. See page 27.
All settings within these pages relate to the optional video monitor, USB devices and/or
audio devices that are connected to the chosen transmitter node.

INSTALLATION
ADMIN - Port Settings ADMIN - Port Settings ADMIN - Port Settings
Review this node’s USB, audio, and video port information and change its settings. Review this node’s USB, audio, and video port information and change its settings. Review this node’s USB, audio, and video port information and change its settings.

TRANSMITTER TRANSMITTER TRANSMITTER

Transmitter 2 Video USB Audio Transmitter 2 Video USB Audio Transmitter 2 Video USB Audio
General Disable Local Video Ports General Disable Local USB Ports General Disable Local Audio Ports
Manage Ports Connected Monitor DEL 61462
Manage Ports
Details Contention Timeout (secs) 2
Manage Ports

CONFIGURATION
Advanced Advanced Connected Devices ABC Ltd
Advanced Details
USB Hub
Choose the video EDID that will be Connected Monitor
Software Upgrade presented to the attached computer Software Upgrade Software Upgrade
Details
HAL Inc. USB Keyboard
XYZ USB Mouse Details

OPERATION
Disable Local Video Ports Cancel Apply Disable Local USB Ports Cancel Apply Disable Local Audio Ports Cancel Apply
Allows you to temporarily disable the video output to the optional console Allows you to temporarily disable the USB Allows you to disable the audio signals
connection on the transmitter node. signals to any devices optionally connected to the to devices optionally connected to the
transmitter node. transmitter node.
Connected Monitor
Lists the basic details for the Monitor Details Contention Timeout (secs)
monitor connected to the USB links to the host computer are shared
console video output of the Manufacturer: DEL
Model ID: 61462
between multiple receivers in a first come first

INFORMATION
transmitter node. Click on Serial Number: F525M098046L served manner. The first receiver to access a USB

FURTHER
Manufacture Date (week/year): 37/2010
the Details button to view EDID Version: 1.3 peripheral will be given control access, while all
Preferred Resolution: 1920x1080p@60Hz 148.50MHz
more information about the others are temporarily prevented, until the first
connected video monitor: 1920x1080p@60Hz 148.50MHz
1152x864p@75Hz 108.00MHz
receiver has completed its actions. The contention
EDID Details
1280x1024p@60Hz 108.00MHz timeout is the time delay, after the last USB activity
1600x900p@60Hz 97.75MHz
1920x1080p@60Hz 138.50MHz of the first receiver, before USB access becomes
720x400p@70Hz 28.32MHz available again to all.
OK
Connected Devices
Lists the USB devices which are currently

INDEX
Choose the video EDID.... connected to the transmitter node. Click the
Allows you to choose between the Automatic EDID configuration for the Details button to view more information about the
connected monitor or to choose one of the listed modes. device.

28
 Advanced pages
To access these pages: From a receiver, enter the OSD menu: Press CTRL + ALT + C hotkeys, then click the icon to show the
Admin menu. Choose the Setup Channels page, click the icon for the required transmitter node and then click the Advanced option.
See page 27.
The items within these pages relate to the network settings, diagnostic tools and statistics for the chosen transmitter node.

INSTALLATION
ADMIN - Network Settings ADMIN - Diagnostic Tools Settings ADMIN - Statistics
Review this node’s network information and set its multicast addresses. XDIP selects IP addresses Change the settings for this node’s diagnostic tools. Review this node’s video and audio information.
automatically using DHCP (when available) or Link-Local addresses (169.254.x.x).
TER TRANSMITTER TRANSMITTER

ter 2 Network Info Diagnostics Statistics Transmitter 2 Network Info Diagnostics Transmitter
Statistics 2 Network Info Diagnostics Statistics

Dynamic IP Address 192.168.1.34 Static IP Address 0.0.0.0General Remote logging Address 0.0.0.0 General Video Performance Audio Performance
Ports Dynamic Netmask 255.255.255.0 Manage Ports
Static Netmask 255.255.255.0 Severity Level 5 Manage Ports Frame Width (px) 1920 Encoding Linear
Dynamic Gateway 192.168.1.1 Static Gateway 192.168.20.1 Enable Remote Logging Frame Height (px) 1080 Bits per Sample 32
d Advanced Advanced

CONFIGURATION
MAC Address 00:0F:58:02:DF:3B Capture Log to USB Trigger Frames per Second 60 Samples per Second 48000
e Upgrade Software Upgrade Software Upgrade
DHCP Server 91.134.24.29 Remote Support 22 Enable Bit Rate (Mbps) 43.480 Bit Rate (Mbps) 1.615661
NTP Server 93.0.123.145 Luma Quality Factor 99 Underflows 0
DNS Address 92.0.124.53 Chroma Quality Factor 97 Overflows 0
Default Multicast
Audio Multicast 239.191.6.105
Video Multicast 239.255.6.105

Cancel Apply Cancel Apply Cancel Apply

OPERATION
Dynamic IP details Remote Logging Address This page provides
Dynamic IP address details are configured automatically in either Enter a valid IP address for a syslog server on the local network where status logs can statistical details
of two ways: be sent. regarding the
• With the use of a DHCP server, if one is available during video and audio
Severity Level
configuration, or performance.
Defines the level of messages that will be logged (according to RFC5424). Level 5

INFORMATION
• Using Link-Local addresses (169.254.x.x). (Notice: normal but significant condition) is the default setting; XDIP currently supports Note:Video statistics

FURTHER
levels 1 to 7. Choosing levels 6 (Informational) or 7 (Debug) will cause larger numbers of will only be available
Static IP details if no other receiver
lesser events to also be logged, with a potential impact to overall performance. These
In addition to the main Dynamic IP address used by each receiver, node is viewing the
levels should only be used if working with the support team to diagnose a specific issue.
a separate set of static IP address details are available for use same video source.
when an XDIP installation will be externally controlled. The Enable Remote Logging
static IP address provide a consistent control channel into the Tick to send log files to the chosen Remote Logging Address.
transmitter, protected by the Access Password.
Capture Log to USB
Default Multicast Click the Trigger button to save the activity log to a local USB memory stick (must be

INDEX
Tick this option and click the Apply button to re-apply the default plugged directly into a port on the transmitter node in question - not the receiver you
Audio and Video Multicast addresses (as shown in the two fields are using for access). The resulting compressed file can then be sent to Adder support
below). when diagnosing an issue.
Remote Support
When using the Adder remote server, this option determines which port will be used.
Multiple options are offered in case one or more ports are blocked by your firewall.
29
Software Upgrade page
To access this page: From a receiver, enter the OSD menu: Press CTRL + ALT + C hotkeys, then
click the icon to show the Admin menu. Choose the Setup Channels page, click the icon
for the required transmitter node and then click the Software Upgrade option. See page 27.
The items within this page relate to the software settings, restore/reboot and firmware
upgrade option for the chosen transmitter node.

INSTALLATION
Firmware details
ADMIN - Software Settings and Upgrade
Review the software versions present on this node. Upgrade, switch to the alternative software Lists the current and recovery Bootloader versions plus the Active image that is currently
TRANSMITTER
version, restore or reboot this node.
running as well as the Alternate (the previously active) image version details.
Transmitter 2 Software Settings and Upgrade Select Upgrade File
General Bootloader v1.05D - 18:15 30/07/19 Recovery v1.05D - 18:15 30/07/19
Any valid firmware upgrade files held (only in the root menu) on a memory stick in one
Manage Ports Active v1.05D - 18:15 30/07/19 Alternate v1.05D - 18:15 30/07/19 of the USB sockets, of the receiver node being used for access, will be listed here (if
necessary click the icon to update after insertion). Select the required file name and

CONFIGURATION
Advanced Select Upgrade File Select File Upgrade
click the Upgrade button. The new firmware will be made current and the pre-existing
Software Upgrade code moved to the recovery/alternate location.
Switch to Alternative Version Switch
Switch to Alternative Version
Restore Default Settings Restore
Allows you to change back to the previous firmware version that was running before the
last upgrade.
Reboot Node Reboot
Restore Default Settings
Click to restore this receiver to its default Start of Life (SoL) condition.

OPERATION
Note: A restore operation will reset all configuration settings and cannot be undone.
Reboot Node
Click to reboot this transmitter node.
Supported file systems
When using USB memory sticks, the following file systems are supported:
• FAT
• NTFS

INFORMATION
• Non-journaled HFS+

FURTHER
INDEX
30
Operation
AdderLink XDIP nodes provide great flexibility in operation, supporting a variety of
connection topologies as discussed in the Introduction chapter (see page 2). Where

INSTALLATION
switching between channels is required, user control is always centered upon the
receiver node(s).

SWITCHING CHANNELS
Switching channels from a receiver
To select a channel (using the channel list) To select a channel (using hotkeys)
1 Using the console keyboard and/or mouse on your receiver node, either: The quickest way to switch between channels is to use hotkeys. This is where the order

CONFIGURATION
• Use the OSD hotkey: Press and hold CTRL and ALT, then press C * of transmitter nodes within the channel list really comes into play.
• Use the mouse OSD launch (this needs to be pre-configured - see page 22). 1 Press and hold the CTRL + ALT * keys,

The channel list page should be displayed: 2 Press the number of the required channel (1 to 8 for the transmitters, 0 for the local
computer).
Receiver 1
Description
The output of the chosen channel will be shown on your console monitor.
To switch between channels (using hotkeys)
# Name Description Before you can use this method, you will need to define which keys to use, see page

OPERATION
0 Local Computer Description 32. For the purposes of this example, we will assume that the letters L and K have
1 Transmitter 1 Description been set for next and previous, respectively.
2 Transmitter 2 Description
1 Press and hold the CTRL + ALT * keys,
3
4
2 Press L to change to the next available channel in the list or K to select the previous
one.
5
6 To disconnect from a channel (using hotkeys)

INFORMATION
7 To disconnect your console from the current channel, without switching to another:

FURTHER
8 1 Press and hold the CTRL + ALT, then press X *,
2 Press the number of the required channel (1 to 8 for the transmitters, 0 for the local
computer).

2 Using the mouse, click the required entry (or use cursor up/down keys and Enter).

The channel list will disappear and the output of the chosen channel will be shown on
your console monitor.

INDEX
3 To change to another channel, repeat steps 1 and 2.
To disconnect from a channel (using the channel list)
To disconnect your console from the current channel, without switching to another:
1 Display the channel list (as above).
2 Click the icon shown next to the currently selected channel.
* Note:The standard hotkey combinations can be changed, see next page
31
To set channel switching hotkeys Switching channels from an external system
Hotkey combinations are possible that allow you to change channels without invoking XDIP installations can be externally controlled either by a control system or a PC
the channel list. The necessary hotkey combinations are not set as standard, but can connected to the XDIP network. This method is most often used when the XDIP
easily be done so from the OSD Settings page of the receiver’s Admin menu. modules form an audio-visual matrix, where multiple receivers access content from a
1 Using the console keyboard and/or mouse on your receiver node, press choice of transmitters - see page 3.
CTRL + ALT + C * When using an external system to control the actions of receivers, you will need to

INSTALLATION
2 Click the icon in the top right corner to display the opening page of the receiver’s know the following for the receivers being accessed:
Admin menu, you will be requested to enter a valid admin password. • The static IP addresses,
3 Choose the OSD Settings option: • The access passwords that have been assigned.

ADMIN - OSD Settings To switch channel using an external PC

Update this node’s OSD timeout and hotkeys. 1 From a PC connected to the XDIP network, use a web browser and enter the static IP
RECEIVER address of the required receiver and the port 8443: https://<ip-address>:8443

CONFIGURATION
Receiver 1 Configure OSD Settings 2 When requested, enter the access password for the receiver and click OK:
General Language English
Receiver 1
OSD Settings Keyboard gb Description

Setup Channels OSD Mouse Launch None

Hotkeys Left Ctrl Left Alt
Manage Ports # Name Description
Next Channel Hotkey Left Ctrl + Left Alt + Letter Access password
0 Local Computer Description
Advanced Previous Channel Hotkey Left Ctrl + Left Alt + Letter RX1
1 Transmitter 1 Description
Software Upgrade OSD Hotkey Left Ctrl + Left Alt + c
2 Transmitter 2 Description
Access password Password for User Access
Disconnect Hotkey Left Ctrl + Left Alt + x

OPERATION
3
OSD Timeout 1 min Cancel OK
4
5
6
Cancel Apply
7
8
4 Configure the Next Channel Hotkey and Previous Channel Hotkey combinations.

Note:When using the Letter option, choose only standard alpha characters and avoid using

INFORMATION
the characters used for OSD and Disconnect hotkeys. If required, you can change the Letter

FURTHER
option to Tab, Backspace, Enter, Space or any of the arrow keys.
3 Select the required transmitter from the list.

Within this page you can also optionally change the main two hotkeys (Ctrl and Alt).
5 Click the Apply button and then the icon in the top right corner (or press the Esc
key on your keyboard) to exit.

INDEX
32
INDICATORS
The transmitter and receiver nodes contain various indicators to provide you with status
information. Both nodes have four red indicators on their front panels.

Front panel status indicators Green and amber status indicators

The status indicators on the front panel of every node provide important feedback on The indicators on the link port of the node’s rear panel provide link status information:

INSTALLATION
current operation:

LNK USB VID PWR

CONFIGURATION
LNK USB VID PWR Amber Green
This indicator will be Indicates an active Indicates an active This indicator will be on This indicator will flash This indicator will be on
on for the receiver USB connection. video connection. when power is supplied when data is being whenever there is a valid
and transmitter On transmitter nodes: to the node. Its color transferred. link between this node and
nodes which have These indicators will be on when there’s reflects the overall another, or to a network
established a link. a local USB/video connection for the PC, status of the node: switch.
regardless of whether a receiver node is Start of Life

OPERATION
connected. Transmitter
On receiver nodes: Receiver
These indicators will be on if there is a
Recovery mode:
USB/video feed from a PC either at the
the node is temporarily
connected transmitter node or at the local
running recovery
feed through port (i.e. channel 0) of the
software with reduced
receiver node.
functionality.

INFORMATION
FURTHER
INDEX
33
Further information
This chapter contains a variety of information, including the following: GETTING ASSISTANCE
• Getting assistance - see right If you are still experiencing problems after checking the information contained within this

INSTALLATION
• Appendix 1 - IGMP guide, then please refer to the Support section of our website:
• Appendix 2 - Layers www.adder.com
• Appendix 3 - Link cable interference protection
• Appendix 4 - XDIP API
• Appendix 5 - Open source licenses

CONFIGURATION
OPERATION
INFORMATION
FURTHER
INDEX
34
APPENDIX 1 - IGMP
Internet Group Management Protocol
Where an AdderLink XDIP transmitter node is required IGMP Snooping
to stream video to two or more receiver nodes, The IGMP messages are effective but only operate at
multicasting is used. layer 2 - intended for routers to determine whether
Multicasting involves the delivery of identical data to multicast data should enter a subnet. A relatively recent

INSTALLATION
multiple receivers simultaneously without the need to development has taken place within the switches that
maintain individual links. When multicast data packets enter glue together all of the hosts within each subnet: IGMP
a subnet, the natural reaction of the switches that bind Snooping. IGMP snooping means these layer 2 devices
all the hosts together within the subnet, is to spread the now have the ability to take a peek at the IGMP messages.
multicast data to all of their ports. This is referred to as As a result, the switches can then determine exactly
Multicast flooding and means that the hosts (or at least which of their own hosts have requested to receive a
their network interfaces) are required to process plenty of multicast – and only pass on multicast data to those hosts.

CONFIGURATION
data that they didn’t request. IGMP offers a partial solution. IGMP Querier
The Internet Group Management Protocol (IGMP) is When IGMP is used, each subnet requires one Layer 3
designed to prevent multicast flooding by allowing Layer switch to act as a Querier. In this lead role, the switch
3 switches to check whether host computers within periodically sends out IGMP Query messages and in
their care are interested in receiving particular multicast response all hosts report which multicast streams they
transmissions.They can then direct multicast data only to wish to receive. The Querier device and all snooping
those points that require it and can shut off a multicast Layer 2 switches, then update their lists accordingly (the
stream if the subnet has no recipients. lists are also updated when Join Group and Leave Group

OPERATION
There are currently three IGMP versions: 1, 2 and 3, with (IGMP v2 or v3) messages are received).
each version building upon the capabilities of the previous IGMP Fast-Leave (aka Immediate Leave)
one: When a device/host no longer wishes to receive a
• IGMPv1 allows host computers to opt into a multicast multicast transmission, it can issue an IGMP Leave Group
transmission using a Join Group message, it is then message as mentioned above. This causes the switch to
incumbent on the router to discover when they no issue an IGMP Group-Specific Query message on the
longer wish to receive; this is achieved by polling port (that the Leave Group was received on) to check

INFORMATION
them (see IGMP Querier below) until they no longer no other receivers exist on that connection that wish to

FURTHER
respond. remain a part of the multicast. This process has a cost in
• IGMPv2 includes the means for hosts to opt out as well terms of switch processor activity and time.
as in, using a Leave Group message. Where AdderLink XDIP nodes are connected directly
• IGMPv3 encompasses the abilities of versions 1 and 2 to the switch (with no other devices on the same port)
but also adds the ability for hosts to specify particular then enabling IGMP Fast-Leave mode means that switches
sources of multicast data. can immediately remove receivers without going through
a full checking procedure. Where multiple nodes are
AdderLink XDIP nodes make use of IGMP v2 and v3 (v3
regularly joining and leaving multicasts, this can speed up

INDEX
is used by default unless the XDIP nodes see v2 used by
performance considerably.
the network, in which case they will automatically drop
down to IGMP v2) when performing multicasts to ensure
that no unnecessary congestion is caused.

35
APPENDIX 2 - LAYERS
Layer 2 and Layer 3:The OSI model
When discussing network switches, the terms Layer 2 So why are Layer 2 and Layer 3 of particular importance
and Layer 3 are very often used. These refer to parts when discussing AdderLink XDIP? Because the successful
of the Open System Interconnection (OSI) model, a transmission of data relies upon fast and reliable passage
standardised way to categorize the necessary functions of through network switches – and most of these operate at

INSTALLATION
any standard network. either Layer 2 or Layer 3.
There are seven layers in the OSI model and these define The job of any network switch is to receive each
the steps needed to get the data created by you (imagine incoming network packet, strip away only the first few
that you are Layer 8) reliably down onto the transmission wrappers to discover the intended destination then
medium (the cable, optical fibre, radio wave, etc.) that rewrap the packet and send it in the correct direction.
carries the data to another user; to complete the picture, In simplified terms, the wrapper that is added at Layer
consider the transmission medium is Layer 0. In general, 2 (by the sending system) includes the physical address

CONFIGURATION
think of the functions carried out by the layers at the top of the intended recipient system, i.e. the unique MAC
as being complex, becoming less complex as you go lower address (for example, 09:f8:33:d7:66:12) that is assigned
down. to every networking device at manufacture. Deciphering
recipients at this level is more straightforward than at
Layer 3, where the address of the recipient is represented
by a logical IP address (e.g. 192.168.0.10) and requires
greater knowledge of the surrounding network structure.
Due to their more complex circuitry, Layer 3 switches are

OPERATION
more expensive than Layer 2 switches of a similar build
quality and are used more sparingly within installations.

As your data travel down from you towards the

transmission medium (the cable), they are successively

INFORMATION
FURTHER
encapsulated at each layer within a new wrapper (along
with a few instructions), ready for transport. Once
transmission has been made to the intended destination,
the reverse occurs: Each wrapper is stripped away and the
instructions examined until finally only the original data
are left.

INDEX
36
APPENDIX 3 - LINK CABLE INTERFERENCE PROTECTION
While the Category rating (e.g. CAT 5e, CAT 6a, CAT 7, etc.)
determines the electrical performance of a cable, another vital part
of the overall cable specification is its protection from interference.
As cabling distances and data rates increase, so too does the
susceptibility to interference, from both external and internal

INSTALLATION
sources.
U/UTP
Proximity to other electromagnetic sources are the main external
threat and these can be subdued using overall screening that
surrounds all four of the cable pairs. However, interference is also
possible from neighbouring twisted pairs within the same cable
and this can be just as hazardous to data integrity. Such crosstalk is
countered by shielding each cable pair separately. Name Overall Screening Pair Shielding
F/UTP

CONFIGURATION
Within each Category rating, you can specify different
combinations of external screening and internal shielding to suit
U/UTP û û
the environment into which the link is being placed.
F/UTP ü û
Interference protection codes
Interference protection is classified in the following manner: U/FTP û ü
U/UTP S/FTP
or S/STP
ü ü U/FTP

OPERATION
or PiMF
Overall Twisted
screening Pair

Pair
shielding S/FTP
S/STP
PiMF
where General cable anatomy

INFORMATION
FURTHER
U = unshielded Outer sheath
F = foil shielding
Overall screening
S = braided shielding
PiMF = Pairs in Metal Foil Pair shielding

INDEX
37
APPENDIX 4 - XDIP API /channels/connected
Adder Technology XDIP Public REST API Get the channel this node is currently connected to.
The API gives the user the ability to control the channel a receiver is connected Type: Get
to, obtain all the necessary information relating to the connected channel and gain
Responses
an authorization access token required to switch channels, given knowledge of the
200 OK
node’s ‘Access’ password. It does not give the user the ability to change the channel
304 Not Modified

INSTALLATION
configuration or any other part of the node’s configuration, in order to do this a user
must log in to the OSD directly and access the admin screen - which will require 404 Channel Id Not In Supported Range
knowledge of the ‘Admin’ password. 500 Operation Failed
Note: Before receivers can be controlled by external systems, the ‘Enable Remote Control’ option
must be checked within the Advanced page of each receiver’s configuration. See page 24. /channels/{id}/switch
Switch node to the specified channel.
YAML download
Type: Post
The YAML file for the API can be found at:

CONFIGURATION
• https://support.adder.com/tiki/tiki-index.php?page=XDIP%3A+Using+the+API Parameters
id Channel Id. An id of 0x7fffffff will cause the receiver to disconnect from the
API version 1.05 current channel.
Schemes: HTTPS Authrorization Access / Admin JSON Web Token (JWT). Format ‘Bearer JWT’.
• The API uses SSL/TLS version 1.2 Responses
• Commands are sent over port 8443, for example: 204 Successful Operation (No Content)
https://<ip-address>:8443/api/<parameters> 401 Unauthorized. Invalid Access Credentials Provided.

OPERATION
404 Channel Id Not In Supported Range
Channels
500 Operation Failed
/channels
Returns a list of channels configured in the system. For future use, each channel will have /channels/maximumAllowed
a list of nodes. Currently only one node is returned in this list. Get the maximum number of channels supported by this node.
Type: Get Type: Get

INFORMATION
Responses Responses

FURTHER
200 OK 200 OK
304 Not Modified 304 Not Modified
500 Operation Failed 500 Operation Failed

/channels/{id} /channels/status
Get details of a single channel. Get the status for the currently selected channel.
Type: Get Type: Get
Responses

INDEX
Responses
200 OK 200 OK
304 Not Modified 304 Not Modified
404 Channel Id Not In Supported Range 500 Operation Failed
500 Operation Failed
38
Nodes Access
/nodes/{uuid} /nodes/self/access
Get details of a single node. Obtain an Access / Admin JSON Web Token (JWT).
Type: Get Type: Post
Parameters Parameters

INSTALLATION
uuid The node’s unique identifier (or ‘self’ for the local node). authData Password attributes.
Responses Responses
200 OK 200 OK
304 Not Modified 400 Invalid Content (Schema)
404 UUID Not Found 401 Unauthorized
500 Operation Failed 404 UUID Not Found

CONFIGURATION
500 Operation Failed
/nodes/selected
Returns a list and details of the configured Channel nodes.
LocalComputer
Type: Get
/localComputer
Responses
Get information relating to the computer that is connected to this node.
200 OK
304 Not Modified Responses
200 OK
500 Operation Failed

OPERATION
304 Not Modified
500 Operation Failed

INFORMATION
FURTHER
INDEX
39
APPENDIX 5 - OPEN SOURCE LICENSES
This product includes binaries that are derived from the open BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT,
source community. OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
The modules listed below are licenced under the GNU General CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) * OF THE POSSIBILITY OF SUCH DAMAGE.
Public License v2 and must be provided, in source form, on ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE * ============================================================
POSSIBILITY OF SUCH DAMAGE. *
request: This program is based on the Generalized Timing Formula (GTF TM) * This product includes cryptographic software written by Eric Young

INSTALLATION
u-boot linux-arm-freescale busybox termcap util-linux Standard Version: 1.0, Revision: 1.0 * ([email protected]). This product includes software written by Tim
* Hudson ([email protected]).
udev e2fsprogs kobs-ng freetype glib dbus-1 qt5 The GTF Document contains the following Copyright information:
*
libfftw Copyright (c) 1994, 1995, 1996 - Video Electronics Standards Association. Duplication of this */
document within VESA member companies for review purposes is permitted. All other rights
The modules listed below are licenced under the GNU Lesser reserved. Original SSLeay License
While every precaution has been taken in the preparation of this standard, the Video Electronics -----------------------
General Public License v2.1 and must be provided, in source Standards Association and its contributors assume no responsibility for errors or omissions,
form, on request: and make no warranties, expressed or implied, of functionality of suitability for any purpose. The /* Copyright (C) 1995-1998 Eric Young ([email protected])
sample code contained within this standard may be used without restriction. * All rights reserved.
kmod libalsa libgpg-error nettle libgcrypt gnutls *
----------------------------------------------------------------------------
libmicrohttpd libjwt libdaemon nss-mdns avahi * This package is an SSL implementation written

CONFIGURATION
Module: openssl * by Eric Young ([email protected]).
In addition to the GPL modules listed, this product also includes ---------------------------------------------------------------------------- * The implementation was written so as to conform with Netscapes SSL.
LICENSE ISSUES *
binaries derived from 3rd party open sources that have their ============== * This library is free for commercial and non-commercial use as long as
own license requirements. Each module is listed below with their The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License * the following conditions are aheared to. The following conditions
and the original SSLeay license apply to the toolkit. See below for the actual license texts. * apply to all code found in this distribution, be it the RC4, RSA,
required Copyright statement and distribution conditions. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to * lhash, DES, etc., code; not just the SSL code. The SSL documentation
OpenSSL please contact [email protected]. * included with this distribution is covered by the same copyright terms
You may obtain the complete Corresponding Source OpenSSL License * except that the holder is Tim Hudson ([email protected]).
Code from Adder for a period of three years after the --------------- *
* Copyright remains Eric Young’s, and as such any Copyright notices in
last shipment of this product, which will be no earlier than /* ============================================================
* Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved. * the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution
2028, by contacting [email protected] or writing to: *
* as the author of the parts of the library used.

OPERATION
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions * This can be in the form of a textual message at program startup or
Attn: ACD/Open Source Request, * are met: * in documentation (online or textual) provided with the package.
*
Adder Technology Ltd, *
* Redistribution and use in source and binary forms, with or without
* 1. Redistributions of source code must retain the above copyright
Saxon Way, Bar Hill, * notice, this list of conditions and the following disclaimer. * modification, are permitted provided that the following conditions
* are met:
*
Cambridge, CB23 8SL, * 2. Redistributions in binary form must reproduce the above copyright * 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
United Kingdom * notice, this list of conditions and the following disclaimer in
* 2. Redistributions in binary form must reproduce the above copyright
* the documentation and/or other materials provided with the
* distribution. * notice, this list of conditions and the following disclaimer in the
Please write “Source for product XXXXXXXX” in the * * documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software

INFORMATION
subject line (where XXXXXXXX is the model and version * 3. All advertising materials mentioning features or use of this
* software must display the following acknowledgment: * must display the following acknowledgement:

FURTHER
number). This offer is valid to anyone in receipt of this * “This product includes software developed by the OpenSSL Project * “This product includes cryptographic software written by
* Eric Young ([email protected])”
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)”
information. * * The word ‘cryptographic’ can be left out if the rouines from the library
* 4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to * being used are not cryptographic related :-).
* endorse or promote products derived from this software without * 4. If you include any Windows specific code (or a derivative thereof) from
----------------------------------------------------------------------------
* prior written permission. For written permission, please contact * the apps directory (application code) you must include an acknowledgement:
Module: libcvt
* [email protected]. * “This product includes software written by Tim Hudson ([email protected])”
----------------------------------------------------------------------------
* *
Copyright (c) 2001, Andy Ritger [email protected] All rights reserved.
* 5. Products derived from this software may not be called “OpenSSL” * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS’’ AND
Redistribution and use in source and binary forms, with or without modification, are permitted
* nor may “OpenSSL” appear in their names without prior written * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
provided that the following conditions are met:
* permission of the OpenSSL Project. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
Redistributions of source code must retain the above copyright notice, this list of conditions and * PURPOSE
the following disclaimer. * 6. Redistributions of any form whatsoever must retain the following * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

INDEX
Redistributions in binary form must reproduce the above copyright notice, this list of conditions * acknowledgment:
and the following disclaimer in the documentation and/or other materials provided with the * “This product includes software developed by the OpenSSL Project * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
distribution. * for use in the OpenSSL Toolkit (http://www.openssl.org/)” GOODS
* * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
Neither the name of NVIDIA nor the names of its contributors may be used to endorse or * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
promote products derived from this software without specific prior written permission. * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS’’ AND ANY
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE STRICT
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
“AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SUCH DAMAGE.
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT *
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * The licence and distribution terms for any publically available version or
40
* derivative of this code cannot be changed. i.e. this code cannot simply be * Redistributions of source code must retain the above copyright notice, 1. Unicode Data Files and Software
* copied and put under another distribution licence this list of conditions and the following disclaimer.
* [including the GNU Public Licence.] * Redistributions in binary form must reproduce the above copyright notice, this list of conditions COPYRIGHT AND PERMISSION NOTICE
*/ and the following disclaimer in the documentation and/or other materials provided with the
---------------------------------------------------------------------------- distribution. Copyright © 1991-2016 Unicode, Inc. All rights reserved.
- Module: libev * Neither name of Intel Corporation nor the names of its contributors may be used to endorse Distributed under the Terms of Use in
---------------------------------------------------------------------------- or promote products derived from this software without specific prior written permission. http://www.unicode.org/copyright.html.

All files in libev are THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS Permission is hereby granted, free of charge, to any person obtaining a copy of the Unicode data
Copyright (c)2007,2008,2009,2010,2011,2012,2013 Marc Alexander Lehmann. IS’’ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE files and any associated documentation (the “Data Files”) or Unicode software and any associated

INSTALLATION
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR documentation (the “Software”) to deal in the Data Files or Software without restriction,
Redistribution and use in source and binary forms, with or without PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL INTEL OR CONTRIBUTORS BE LIABLE including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell
modification, are permitted provided that the following conditions are FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL copies of the Data Files or Software, and to permit persons to whom the Data Files or Software
met: DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS are furnished to do so, provided that
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER (a) this copyright and permission notice appear with all copies
* Redistributions of source code must retain the above copyright CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT of the Data Files or Software,
notice, this list of conditions and the following disclaimer. LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY (b) this copyright and permission notice appear in associated documentation, and
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH (c) there is clear notice in each modified Data File or in the Software as well as in the
* Redistributions in binary form must reproduce the above DAMAGE. documentation associated with the Data File(s) or Software that the data or software has been
copyright notice, this list of conditions and the following modified.
disclaimer in the documentation and/or other materials provided ----------------------------------------------------------------------------
with the distribution. - THE DATA FILES AND SOFTWARE ARE PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY
- Module: libjpeg KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

CONFIGURATION
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS
IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE - WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR ---------------------------------------------------------------------------- NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, This software is based in part on the work of the Independent JPEG Group. SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, ---------------------------------------------------------------------------- CONTRACT, NEGLIGENCE OR OTHER
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY - TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT - Module: icu PERFORMANCE OF THE DATA FILES OR SOFTWARE.
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF -
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ---------------------------------------------------------------------------- Except as contained in this notice, the name of a copyright holder shall not be used in advertising
or otherwise to promote the sale, use or other dealings in these Data Files or Software without
---------------------------------------------------------------------------- ICU License - ICU 1.8.1 and later prior written authorization of the copyright holder.
-
COPYRIGHT AND PERMISSION NOTICE 2. Chinese/Japanese Word Break Dictionary Data (cjdict.txt)

OPERATION
- Module: libaes
-
---------------------------------------------------------------------------- Copyright (c) 1995-2016 International Business Machines Corporation and others # The Google Chrome software developed by Google is licensed under
# the BSD license. Other software included in this distribution is
Copyright (c) 1998-2008, Brian Gladman, Worcester, UK. All rights reserved. All rights reserved. # provided under other licenses, as set forth below.
#
LICENSE TERMS Permission is hereby granted, free of charge, to any person obtaining a copy of this software and # The BSD License
associated documentation files (the “Software”), to deal in the Software without restriction, # http://opensource.org/licenses/bsd-license.php
The redistribution and use of this software (with or without changes) is allowed without the including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell # Copyright (C) 2006-2008, Google Inc.
payment of fees or royalties provided that: copies of the Software, and to permit persons to whom the Software is furnished to do so, #
provided that the above copyright notice(s) and this permission notice appear in all copies of the # All rights reserved.
1. source code distributions include the above copyright notice, this Software and that both the above copyright notice(s) and this permission notice appear in #
supporting documentation. # Redistribution and use in source and binary forms, with or without

INFORMATION
list of conditions and the following disclaimer;
# modification, are permitted provided that the following conditions are met:

FURTHER
2. binary distributions include the above copyright notice, this list THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, #
of conditions and the following disclaimer in their documentation; EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF # Redistributions of source code must retain the above copyright notice,
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF # this list of conditions and the following disclaimer.
3. the name of the copyright holder is not used to endorse products THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS # Redistributions in binary form must reproduce the above
built using this software without specific written permission. INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR # copyright notice, this list of conditions and the following
CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS # disclaimer in the documentation and/or other materials provided with
DISCLAIMER OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR # the distribution.
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR # Neither the name of Google Inc. nor the names of its
This software is provided ‘as is’ with no explicit or implied warranties PERFORMANCE OF THIS SOFTWARE. # contributors may be used to endorse or promote products derived from
in respect of its properties, including, but not limited to, correctness # this software without specific prior written permission.
and/or fitness for purpose. Except as contained in this notice, the name of a copyright holder shall not be used in advertising #
or otherwise to promote the sale, use or other dealings in this Software without prior written #
---------------------------------------------------------------------------- authorization of the copyright holder. # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
# CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,

INDEX
-
- Module: libupnp All trademarks and registered trademarks mentioned herein are the # INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
- property of their respective owners. # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
---------------------------------------------------------------------------- # DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
--------------------- # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
Copyright (c) 2000-2003 Intel Corporation # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
All rights reserved. Third-Party Software Licenses # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
Redistribution and use in source and binary forms, with or without This section contains third-party software notices and/or additional terms for licensed # LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
modification, are permitted provided that the following conditions are met: third-party software components included within ICU libraries. # NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
41
# # * REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, # modification, copying and distribution of the program and the
# The word list in cjdict.txt are generated by combining three word lists # * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES # production of secondary products from the program.
# listed below with further processing for compound word breaking. The # * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR #
# frequency is generated with an iterative training against Google web # * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # In the case where the program, whether in its original form or
# corpora. # * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, # modified, was distributed or delivered to or received by a user from
# # * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) # any person, organization or entity other than ICOT, unless it makes or
# * Libtabe (Chinese) # * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED # grants independently of ICOT any specific warranty to the user in
# - https://sourceforge.net/project/?group_id=1519 # * OF THE POSSIBILITY OF SUCH DAMAGE. # writing, such person, organization or entity, will also be exempted
# - Its license terms and conditions are shown below. # */ # from and not be held liable to the user for any such damages as noted
# # # above as far as the program is concerned.

INSTALLATION
# * IPADIC (Japanese) # Copyright 1996 Chih-Hao Tsai @ Beckman Institute, #
# - http://chasen.aist-nara.ac.jp/chasen/distribution.html # University of Illinois
# - Its license terms and conditions are shown below. # [email protected] http://casper.beckman.uiuc.edu/~c-tsai4 3. Lao Word Break Dictionary Data (laodict.txt)
# #
# ---------COPYING.libtabe ---- BEGIN-------------------- # Copyright 2000, 2001, 2002, 2003 Nara Institute of Science # Copyright (c) 2013 International Business Machines Corporation
# # and Technology. All Rights Reserved. # and others. All Rights Reserved.
# /* # #
# * Copyrighy (c) 1999 TaBE Project. # Use, reproduction, and distribution of this software is permitted. # Project: http://code.google.com/p/lao-dictionary/
# * Copyright (c) 1999 Pai-Hsiang Hsiao. # Any copy of this software, whether in its original form or modified, # Dictionary: http://lao-dictionary.googlecode.com/git/Lao-Dictionary.txt
# * All rights reserved. # must include both the above copyright notice and the following # License: http://lao-dictionary.googlecode.com/git/Lao-Dictionary-LICENSE.txt
# * # paragraphs. #
# * Redistribution and use in source and binary forms, with or without # # This file is derived from the above dictionary, with slight
# * modification, are permitted provided that the following conditions # Nara Institute of Science and Technology (NAIST), # modifications.

CONFIGURATION
# * are met: # the copyright holders, disclaims all warranties with regard to this # ----------------------------------------------------------------------
# * # software, including all implied warranties of merchantability and # Copyright (C) 2013 Brian Eugene Wilson, Robert Martin Campbell.
# * . Redistributions of source code must retain the above copyright # fitness, in no event shall NAIST be liable for # All rights reserved.
# * notice, this list of conditions and the following disclaimer. # any special, indirect or consequential damages or any damages #
# * . Redistributions in binary form must reproduce the above copyright # whatsoever resulting from loss of use, data or profits, whether in an # Redistribution and use in source and binary forms, with or without
# * notice, this list of conditions and the following disclaimer in # action of contract, negligence or other tortuous action, arising out # modification,
# * the documentation and/or other materials provided with the distribution. # of or in connection with the use or performance of this software. # are permitted provided that the following conditions are met:
# * . Neither the name of the TaBE Project nor the names of its # #
# * contributors may be used to endorse or promote products derived # A large portion of the dictionary entries # Redistributions of source code must retain the above copyright notice, this
# * from this software without specific prior written permission. # originate from ICOT Free Software. The following conditions for ICOT # list of conditions and the following disclaimer. Redistributions in
# * # Free Software applies to the current dictionary as well. # binary form must reproduce the above copyright notice, this list of
# * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND # # conditions and the following disclaimer in the documentation and/or
CONTRIBUTORS # Each User may also freely distribute the Program, whether in its # other materials provided with the distribution.
# * “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT # original form or modified, to any third party or parties, PROVIDED #

OPERATION
# * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS # that the provisions of Section 3 (“NO WARRANTY”) will ALWAYS appear # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
# * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE # on, or be attached to, the Program, which is distributed substantially # “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
# * REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, # in the same form as set out herein and that such intended # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
# * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES # distribution, if actually made, will neither violate or otherwise # FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
# * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR # contravene any of the laws and regulations of the countries having # COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
# * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # jurisdiction over the User or the intended distribution itself. # INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
# * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, # # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
# * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) # NO WARRANTY # SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF # # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
THE POSSIBILITY OF SUCH DAMAGE. # The program was produced on an experimental basis in the course of the # STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
# */ # research and development conducted during the project and is provided # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
# # to users as so produced on an experimental basis. Accordingly, the # OF THE POSSIBILITY OF SUCH DAMAGE.

INFORMATION
# /* # program is provided without any warranty whatsoever, whether express, 4. Burmese Word Break Dictionary Data (burmesedict.txt)

FURTHER
# * Copyright (c) 1999 Computer Systems and Communication Lab, # implied, statutory or otherwise. The term “warranty” used herein
# * Institute of Information Science, Academia # includes, but is not limited to, any warranty of the quality, # Copyright (c) 2014 International Business Machines Corporation
# * Sinica. All rights reserved. # performance, merchantability and fitness for a particular purpose of # and others. All Rights Reserved.
# * # the program and the nonexistence of any infringement or violation of #
# * Redistribution and use in source and binary forms, with or without # any right of any third party. # This list is part of a project hosted at:
# * modification, are permitted provided that the following conditions # # github.com/kanyawtech/myanmar-karen-word-lists
# * are met: # Each user of the program will agree and understand, and be deemed to #
# * # have agreed and understood, that there is no warranty whatsoever for # --------------------------------------------------------------------------
# * . Redistributions of source code must retain the above copyright # the program and, accordingly, the entire risk arising from or # Copyright (c) 2013, LeRoy Benjamin Sharon
# * notice, this list of conditions and the following disclaimer. # otherwise connected with the program is assumed by the user. # All rights reserved.
# * . Redistributions in binary form must reproduce the above copyright # #
# * notice, this list of conditions and the following disclaimer in # Therefore, neither ICOT, the copyright holder, or any other # Redistribution and use in source and binary forms, with or without
# * the documentation and/or other materials provided with the # organization that participated in or was otherwise related to the # modification, are permitted provided that the following conditions
# * distribution. # development of the program and their respective officials, directors, # are met: Redistributions of source code must retain the above

INDEX
# * . Neither the name of the Computer Systems and Communication Lab # officers and other employees shall be held liable for any and all # copyright notice, this list of conditions and the following
# * nor the names of its contributors may be used to endorse or # damages, including, without limitation, general, special, incidental # disclaimer. Redistributions in binary form must reproduce the
# * promote products derived from this software without specific # and consequential damages, arising out of or otherwise in connection # above copyright notice, this list of conditions and the following
# * prior written permission. # with the use or inability to use the program or any product, material # disclaimer in the documentation and/or other materials provided
# * # or result produced or otherwise obtained by using the program, # with the distribution.
# * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND # regardless of whether they have been advised of, or otherwise had #
CONTRIBUTORS # knowledge of, the possibility of such damages at any time during the # Neither the name Myanmar Karen Word Lists, nor the names of its
# * “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT # project or thereafter. Each user will be deemed to have agreed to the # contributors may be used to endorse or promote products derived
# * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS # foregoing by his or her commencement of use of the program. The term # from this software without specific prior written permission.
# * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE # “use” as used herein includes, but is not limited to, the use, #
42
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND Permission to use, copy, modify, distribute, and sell this software and its ----------------------------------------------------------------------------
# CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, documentation for any purpose is hereby granted without fee, provided that
# INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF the above copyright notice appear in all copies and that both that copyright Copyright 1996 by Joseph Moss
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE notice and this permission notice appear in supporting documentation, and Copyright (C) 2002-2007 Free Software Foundation, Inc.
# DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS that the name of the copyright holders not be used in advertising or Copyright (C) Dmitry Golubev <[email protected]>, 2003-2004
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, publicity pertaining to distribution of the software without specific, Copyright (C) 2004, Gregory Mokhin <[email protected]>
# EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED written prior permission. The copyright holders make no representations Copyright (C) 2006 Erdal Ronahî
# TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, about the suitability of this software for any purpose. It is provided “as
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON is” without express or implied warranty. Permission to use, copy, modify, distribute, and sell this software and its
# ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR documentation for any purpose is hereby granted without fee, provided that

INSTALLATION
# TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS the above copyright notice appear in all copies and that both that
# THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND copyright notice and this permission notice appear in supporting
# SUCH DAMAGE. FITNESS, IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY SPECIAL, documentation, and that the name of the copyright holder(s) not be used in
# -------------------------------------------------------------------------- INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER advertising or publicity pertaining to distribution of the software without
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF specific, written prior permission. The copyright holder(s) makes no
5. Time Zone Database CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN representations about the suitability of this software for any purpose. It
CONNECTION WITH THE USE OR PERFORMANCE is provided “as is” without express or implied warranty.
ICU uses the public domain data and code derived from Time Zone OF THIS SOFTWARE.
Database for its time zone support. The ownership of the TZ database THE COPYRIGHT HOLDER(S) DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
is explained in BCP 175: Procedure for Maintaining the Time Zone The following license is from a Linux kernel header file and there is no GPL code this package SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
Database section 7. links to. FITNESS, IN NO EVENT SHALL THE COPYRIGHT HOLDER(S) BE LIABLE FOR ANY SPECIAL,
INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
# 7. Database Ownership Copyright (c) 1999-2002 Vojtech Pavlik RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF

CONFIGURATION
# CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
# The TZ database itself is not an IETF Contribution or an IETF This program is free software; you can redistribute it and/or modify it CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
# document. Rather it is a pre-existing and regularly updated work under the terms of the GNU General Public License version 2 as published by
# that is in the public domain, and is intended to remain in the the Free Software Foundation. Copyright (c) 1996 Digital Equipment Corporation
# public domain. Therefore, BCPs 78 [RFC5378] and 79 [RFC3979] do ----------------------------------------------------------------------------
# not apply to the TZ Database or contributions that individuals make - Permission is hereby granted, free of charge, to any person obtaining
# to it. Should any claims be made and substantiated against the TZ - Module: libinput a copy of this software and associated documentation files (the
# Database, the organization that is providing the IANA - “Software”), to deal in the Software without restriction, including
# Considerations defined in this RFC, under the memorandum of ---------------------------------------------------------------------------- without limitation the rights to use, copy, modify, merge, publish,
# understanding with the IETF, currently ICANN, may act in accordance distribute, sublicense, and sell copies of the Software, and to
# with all competent court orders. No ownership claims will be made Copyright © 2006-2009 Simon Thum permit persons to whom the Software is furnished to do so, subject to
# by ICANN or the IETF Trust on the database or the code. Any person Copyright © 2008-2012 Kristian Høgsberg the following conditions:
# making a contribution to the database or code waives all rights to Copyright © 2010-2012 Intel Corporation
# future claims in that contribution or in the TZ Database. Copyright © 2010-2011 Benjamin Franzke The above copyright notice and this permission notice shall be included

OPERATION
Copyright © 2011-2012 Collabora, Ltd. in all copies or substantial portions of the Software.
---------------------------------------------------------------------------- Copyright © 2013-2014 Jonas Ådahl
- Copyright © 2013-2015 Red Hat, Inc. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- Module: mtdev IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- Permission is hereby granted, free of charge, to any person obtaining a FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
---------------------------------------------------------------------------- copy of this software and associated documentation files (the “Software”), DIGITAL EQUIPMENT CORPORATION BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
to deal in the Software without restriction, including without limitation LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
mtdev - Multitouch Protocol Translation Library (MIT license) the rights to use, copy, modify, merge, publish, distribute, sublicense, FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
and/or sell copies of the Software, and to permit persons to whom the DEALINGS IN THE SOFTWARE.
Copyright (C) 2010 Henrik Rydberg <[email protected]> Software is furnished to do so, subject to the following conditions:
Copyright (C) 2010 Canonical Ltd. Except as contained in this notice, the name of the Digital Equipment
The above copyright notice and this permission notice (including the next Corporation shall not be used in advertising or otherwise to promote

INFORMATION
paragraph) shall be included in all copies or substantial portions of the the sale, use or other dealings in this Software without prior written

FURTHER
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the “Software”), to deal in the Software without restriction, Software. authorization from Digital Equipment Corporation.
including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the Software is furnished to THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR Copyright 1996, 1998 The Open Group
do so, subject to the following conditions: IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL Permission to use, copy, modify, distribute, and sell this software and its
The above copyright notice and this permission notice (including the next paragraph) shall be THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR documentation for any purpose is hereby granted without fee, provided that
included in all copies or substantial portions of the Software. OTHER the above copyright notice appear in all copies and that both that
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING copyright notice and this permission notice appear in supporting
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER documentation.
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, DEALINGS IN THE SOFTWARE.
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL The above copyright notice and this permission notice shall be
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR libinput ships a copy of the GPL-licensed Linux kernel’s linux/input.h included in all copies or substantial portions of the Software.
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, header file. [1] This does not make libinput GPL.
This copy is provided to provide consistent behavior regardless which kernel THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,

INDEX
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE. version libinput is compiled against. The header is used during compilation EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
---------------------------------------------------------------------------- only, libinput does not link against GPL libraries. MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
- NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- Module: libevdev [1] http://cgit.freedesktop.org/wayland/libinput/tree/include/linux/input.h LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
- FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
---------------------------------------------------------------------------- DEALINGS IN THE SOFTWARE.
----------------------------------------------------------------------------
Copyright © 2013 Red Hat, Inc. - Except as contained in this notice, the name of The Open Group shall
Copyright © 2013 David Herrmann <[email protected]> - Module: xkeyboard-config not be used in advertising or otherwise to promote the sale, use or
- other dealings in this Software without prior written authorization
43
from The Open Group.
Copyright 2004-2005 Sun Microsystems, Inc. All rights reserved. The above copyright notice and this permission notice shall be included in all copies or The above copyright notice and this permission notice shall be included in
substantial portions of the Software. all copies or substantial portions of the Software.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the “Software”), THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
to deal in the Software without restriction, including without limitation EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
the rights to use, copy, modify, merge, publish, distribute, sublicense, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
and/or sell copies of the Software, and to permit persons to whom the NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
Software is furnished to do so, subject to the following conditions: LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

INSTALLATION
The above copyright notice and this permission notice (including the next paragraph) shall be OTHER DEALINGS IN THE SOFTWARE. SOFTWARE.
included in all copies or substantial portions of the Software.
Except as contained in this notice, the name of a copyright holder shall Except as contained in this notice, the names of the authors or their
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR not be used in advertising or otherwise to promote the sale, use or institutions shall not be used in advertising or otherwise to promote the
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, other dealings in this Software without prior written authorization of sale, use or other dealings in this Software without prior written
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL the copyright holder. authorization from the authors.
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, -------------------------------------------------------------------------------
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR Copyright (C) 1999, 2000 by Anton Zinoviev <[email protected]> Copyright (c) 1993, 1994, 1995, 1996 by Silicon Graphics Computer Systems, Inc.
OTHER DEALINGS IN THE SOFTWARE.
Copyright (c) 1996 by Silicon Graphics Computer Systems, Inc. This software may be used, modified, copied, distributed, and sold, Permission to use, copy, modify, and distribute this
in both source and binary form provided that the above copyright software and its documentation for any purpose and without
Permission to use, copy, modify, and distribute this and these terms are retained. Under no circumstances is the author fee is hereby granted, provided that the above copyright

CONFIGURATION
software and its documentation for any purpose and without responsible for the proper functioning of this software, nor does notice appear in all copies and that both that copyright
fee is hereby granted, provided that the above copyright the author assume any responsibility for damages incurred with its notice and this permission notice appear in supporting
notice appear in all copies and that both that copyright use. documentation, and that the name of Silicon Graphics not be
notice and this permission notice appear in supporting used in advertising or publicity pertaining to distribution
documentation, and that the name of Silicon Graphics not be Permission is granted to anyone to use, distribute and modify of the software without specific prior written permission.
used in advertising or publicity pertaining to distribution this file in any way, provided that the above copyright notice Silicon Graphics makes no representation about the suitability
of the software without specific prior written permission. is left intact and the author of the modification summarizes of this software for any purpose. It is provided “as is”
Silicon Graphics makes no representation about the suitability the changes in this header. without any express or implied warranty.
of this software for any purpose. It is provided “as is”
without any express or implied warranty. This file is distributed without any expressed or implied warranty. SILICON GRAPHICS DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
SILICON GRAPHICS DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS ---------------------------------------------------------------------------- AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SILICON
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY - GRAPHICS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL
AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SILICON DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,

OPERATION
- Module: libxkbcommon
GRAPHICS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL - DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, ---------------------------------------------------------------------------- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE THE USE OR PERFORMANCE OF THIS SOFTWARE.
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH Copyright © 2009-2012, 2016 Daniel Stone
THE USE OR PERFORMANCE OF THIS SOFTWARE. Copyright © 2012 Ran Benita <[email protected]> -------------------------------------------------------------------------------
Copyright (c) 1996 X Consortium Copyright © 2010, 2012 Intel Corporation Copyright 1987, 1988 by Digital Equipment Corporation, Maynard, Massachusetts.
Copyright © 2008, 2009 Dan Nicholson
Permission is hereby granted, free of charge, to any person obtaining Copyright © 2010 Francisco Jerez <[email protected]> All Rights Reserved
a copy of this software and associated documentation files (the
“Software”), to deal in the Software without restriction, including Permission is hereby granted, free of charge, to any person obtaining a Permission to use, copy, modify, and distribute this software and its
without limitation the rights to use, copy, modify, merge, publish, copy of this software and associated documentation files (the “Software”), documentation for any purpose and without fee is hereby granted,
distribute, sublicense, and/or sell copies of the Software, and to

INFORMATION
to deal in the Software without restriction, including without limitation provided that the above copyright notice appear in all copies and that
permit persons to whom the Software is furnished to do so, subject to

FURTHER
the rights to use, copy, modify, merge, publish, distribute, sublicense, both that copyright notice and this permission notice appear in
the following conditions: and/or sell copies of the Software, and to permit persons to whom the supporting documentation, and that the name of Digital not be
Software is furnished to do so, subject to the following conditions: used in advertising or publicity pertaining to distribution of the
The above copyright notice and this permission notice shall be software without specific, written prior permission.
included in all copies or substantial portions of the Software. The above copyright notice and this permission notice (including the next
paragraph) shall be included in all copies or substantial portions of the DIGITAL DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, Software. ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF DIGITAL BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR SOFTWARE.
OTHER DEALINGS IN THE SOFTWARE. OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR -------------------------------------------------------------------------------
Except as contained in this notice, the name of the X Consortium shall

INDEX
OTHER DEALINGS IN THE SOFTWARE. Copyright (C) 2011 Joseph Adams <[email protected]>
not be used in advertising or otherwise to promote the sale, use or
other dealings in this Software without prior written authorization Permission is hereby granted, free of charge, to any person obtaining a copy
from the X Consortium. -------------------------------------------------------------------------------
Copyright 1985, 1987, 1988, 1990, 1998 The Open Group of this software and associated documentation files (the “Software”), to deal
in the Software without restriction, including without limitation the rights
Copyright (C) 2004, 2006 Ævar Arnfjörð Bjarmason <[email protected]> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the “Software”), copies of the Software, and to permit persons to whom the Software is
Permission to use, copy, modify, distribute, and sell this software and its furnished to do so, subject to the following conditions:
documentation for any purpose is hereby granted without fee, provided that to deal in the Software without restriction, including without limitation
the above copyright notice appear in all copies and that both that the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the The above copyright notice and this permission notice shall be included in
copyright notice and this permission notice appear in supporting all copies or substantial portions of the Software.
documentation. Software is furnished to do so, subject to the following conditions:
44
 Copyright (C) 1994 X Consortium 1.4 “Software Implementation” means any practice of any invention
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR claimed in the Licensed Patents that takes the form of software executing on
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, Permission is hereby granted, free of charge, to any person obtaining a copy a user-programmable, general-purpose computer or that takes the form of a
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL of this software and associated documentation files (the “Software”), to computer-readable medium storing such software. Software Implementation does
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR deal in the Software without restriction, including without limitation the not include, for example, application-specific integrated circuits (ASICs),
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, rights to use, copy, modify, merge, publish, distribute, sublicense, and/or field-programmable gate arrays (FPGAs), embedded systems, or IP cores.
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR sell copies of the Software, and to permit persons to whom the Software is 1.5 “Open Source Software” means software whose source code is published
OTHER DEALINGS IN THE SOFTWARE. furnished to do so, subject to the following conditions: and made available for inspection and use by anyone because either (a) the
source code is subject to a license that permits recipients to copy, modify,
------------------------------------------------------------------------------- The above copyright notice and this permission notice shall be included in and distribute the source code without payment of fees or royalties, or

INSTALLATION
- all copies or substantial portions of the Software. (b) the source code is in the public domain, including code released for
- Module: libgcrypt public use through a CC0 waiver. All licenses certified by the Open Source
- THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR Initiative at opensource.org as of January 9, 2013 and all Creative Commons
---------------------------------------------------------------------------- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, licenses identified on the creativecommons.org website as of January 9,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL 2013, including the Public License Fallback of the CC0 waiver, satisfy these
Additional license notices for Libgcrypt. -*- org -*- THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, requirements for the purposes of this license.
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
This file contains the copying permission notices for various files in OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 1.6 “Open Source Software Implementation” means a Software
the Libgcrypt distribution which are not covered by the GNU Lesser THE SOFTWARE. Implementation in which the software implicating the Licensed Patents is
General Public License (LGPL) or the GNU General Public License (GPL). Open Source Software. Open Source Software Implementation does not include
Except as contained in this notice, the name of the X Consortium shall not be used in advertising any Software Implementation in which the software implicating the Licensed
These notices all require that a copy of the notice be included or otherwise to promote the sale, use or other dealings in this Software without prior written Patents is combined, so as to form a larger program, with software that is
in the accompanying documentation and be distributed with binary authorization from the X Consortium. not Open Source Software.

CONFIGURATION
distributions of the code, so be sure to include this file along #+end_quote
with any binary distributions derived from the GNU C Library. 2 License Grant
* Public domain
* BSD_3Clause 2.1 License. Subject to your compliance with the term s of this license,
For files: including the restriction set forth in Section 2.2, Licensor hereby
For files: - cipher/arcfour-amd64.S grants to you a perpetual, worldwide, non-exclusive, non-transferable,
- cipher/sha256-avx-amd64.S non-sublicenseable, no-charge, royalty-free, irrevocable license to practice
- cipher/sha256-avx2-bmi2-amd64.S #+begin_quote any invention claimed in the Licensed Patents in any Open Source Software
- cipher/sha256-ssse3-amd64.S Author: Marc Bevand <bevand_m (at) epita.fr> Implementation.
- cipher/sha512-avx-amd64.S Licence: I hereby disclaim the copyright on this code and place it
- cipher/sha512-avx2-bmi2-amd64.S in the public domain. 2.2 Restriction. If you or your affiliates institute patent litigation
- cipher/sha512-ssse3-amd64.S #+end_quote (including, but not limited to, a cross-claim or counterclaim in a lawsuit)
against any entity alleging that any Use authorized by this license
#+begin_quote * OCB license 1 infringes another patent, then any rights granted to you under this license

OPERATION
Copyright (c) 2012, Intel Corporation For files: automatically terminate as of the date such litigation is filed.
- cipher/cipher-ocb.c
All rights reserved. 3 Disclaimer
#+begin_quote YOUR USE OF THE LICENSED PATENTS IS AT YOUR OWN RISK AND UNLESS REQUIRED
Redistribution and use in source and binary forms, with or without OCB is covered by several patents but may be used freely by most BY APPLICABLE LAW, LICENSOR MAKES NO REPRESENTATIONS OR WARRANTIES OF
modification, are permitted provided that the following conditions are software. See http://web.cs.ucdavis.edu/~rogaway/ocb/license.htm . ANY KIND CONCERNING THE LICENSED PATENTS OR ANY PRODUCT EMBODYING
met: In particular license 1 is suitable for Libgcrypt: See ANY LICENSED PATENT, EXPRESS OR IMPLIED, STATUT ORY OR OTHERWISE, INCLUDING,
http://web.cs.ucdavis.edu/~rogaway/ocb/license1.pdf for the full WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A
* Redistributions of source code must retain the above copyright license document; it basically says: PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL LICENSOR BE
notice, this list of conditions and the following disclaimer. LIABLE FOR ANY
License 1 — License for Open-Source Software Implementations of OCB CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
* Redistributions in binary form must reproduce the above copyright (Jan 9, 2013) ARISING FROM OR RELATED TO ANY USE OF THE LICENSED PATENTS, INCLUDING,

INFORMATION
notice, this list of conditions and the following disclaimer in the WITHOUT LIMITATION, DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE

FURTHER
documentation and/or other materials provided with the Under this license, you are authorized to make, use, and OR SPECIAL DAMAGES, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF
distribution. distribute open-source software implementations of OCB. This SUCH DAMAGES PRIOR TO SUCH AN OCCURRENCE.
license terminates for you if you sue someone over their #+end_quote
* Neither the name of the Intel Corporation nor the names of its open-source software implementation of OCB claiming that you have ----------------------------------------------------------------------------
contributors may be used to endorse or promote products derived from a patent covering their implementation. -
this software without specific prior written permission. - Module: jansson
THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION “AS IS” AND ANY License for Open Source Software Implementations of OCB -
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE January 9, 2013 ----------------------------------------------------------------------------
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION OR 1 Definitions Copyright (c) 2009-2014 Petri Lehtinen <[email protected]>
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, 1.1 “Licensor” means Phillip Rogaway.
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, Permission is hereby granted, free of charge, to any person obtaining a copy
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 1.2 “Licensed Patents” means any patent that claims priority to United of this software and associated documentation files (the “Software”), to deal
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF in the Software without restriction, including without limitation the rights

INDEX
States Patent Application No. 09/918,615 entitled “Method and Apparatus
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING for Facilitating Efficient Authenticated Encryption,” and any utility, to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS divisional, provisional, continuation, continuations-in-part, reexamination, copies of the Software, and to permit persons to whom the Software is
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. reissue, or foreign counterpart patents that may issue with respect to the furnished to do so, subject to the following conditions:
#+end_quote aforesaid patent application. This includes, but is not limited to, United
States Patent No. 7,046,802; United States Patent No. 7,200,227; United The above copyright notice and this permission notice shall be included in
* X License States Patent No. 7,949,129; United States Patent No. 8,321,675 ; and any all copies or substantial portions of the Software.
For files: patent that issues out of United States Patent Application No. 13/669,114.
- install.sh THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1.3 “Use” means any practice of any invention claimed in the Licensed Patents. IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
#+begin_quote FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
45
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR - MD5 is now external, in the OpenSSL library *
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, - RC4 support has been replaced with ARC4 support from OpenSSL * Optimised ANSI C code for the Rijndael cipher (now AES)
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR - Blowfish is now external, in the OpenSSL library *
OTHER DEALINGS IN THE SOFTWARE. * @author Vincent Rijmen <[email protected]>
Note that any information and cryptographic algorithms used in this * @author Antoon Bosselaers <[email protected]>
---------------------------------------------------------------------------- software are publicly available on the Internet and at any major * @author Paulo Barreto <[email protected]>
- bookstore, scientific library, and patent office worldwide. More *
- Module: libcurl information can be found e.g. at “http://www.cs.hut.fi/crypto”. * This code is hereby placed in the public domain.
- *
---------------------------------------------------------------------------- The legal status of this program is some combination of all these * THIS SOFTWARE IS PROVIDED BY THE AUTHORS ‘’AS IS’’ AND ANY EXPRESS

INSTALLATION
permissions and restrictions. Use only at your own responsibility. * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
COPYRIGHT AND PERMISSION NOTICE You will be responsible for any legal consequences yourself; I am not * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
making any claims whether possessing or using this is legal or not in * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE
Copyright (c) 1996 - 2016, Daniel Stenberg, <[email protected]>, and many your country, and I am not taking any responsibility on your behalf. * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
contributors, see the THANKS file. * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
All rights reserved. OF
Permission to use, copy, modify, and distribute this software for any purpose NO WARRANTY * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
with or without fee is hereby granted, provided that the above copyright * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
notice and this permission notice appear in all copies. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 5)

CONFIGURATION
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY
RIGHTS. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS One component of the ssh source code is under a 3-clause BSD license,
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE held by the University of California, since we pulled these parts from
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE PROGRAM PROVE DEFECTIVE,YOU ASSUME THE COST OF ALL NECESSARY SERVICING, original Berkeley code.
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. REPAIR OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL * Copyright (c) 1983, 1990, 1992, 1993, 1995
Except as contained in this notice, the name of a copyright holder shall not ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR * The Regents of the University of California. All rights reserved.
be used in advertising or otherwise to promote the sale, use or other dealings REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, *
in this Software without prior written authorization of the copyright holder. INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES * Redistribution and use in source and binary forms, with or without
ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT * modification, are permitted provided that the following conditions
---------------------------------------------------------------------------- LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES * are met:
- SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE * 1. Redistributions of source code must retain the above copyright
- Module: openssh WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN * notice, this list of conditions and the following disclaimer.
- ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. * 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the

OPERATION
----------------------------------------------------------------------------
2) * documentation and/or other materials provided with the distribution.
The licences which components of this software fall under are as The 32-bit CRC compensation attack detector in deattack.c was * 3. Neither the name of the University nor the names of its contributors
follows. First, we will summarize and say that all components contributed by CORE SDI S.A. under a BSD-style license. * may be used to endorse or promote products derived from this software
are under a BSD licence, or a licence more free than that. * without specific prior written permission.
* Cryptographic attack detector for ssh - source code *
OpenSSH contains no GPL code. * * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS’’ AND
* Copyright (c) 1998 CORE SDI S.A., Buenos Aires, Argentina. * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
1) * * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* Copyright (c) 1995 Tatu Ylonen <[email protected]>, Espoo, Finland * All rights reserved. Redistribution and use in source and binary PURPOSE
* All rights reserved * forms, with or without modification, are permitted provided that * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE
* * this copyright notice is retained. LIABLE
* * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

INFORMATION
* As far as I am concerned, the code I have written for this software
* THIS SOFTWARE IS PROVIDED ``AS IS’’ AND ANY EXPRESS OR IMPLIED CONSEQUENTIAL

FURTHER
* can be used freely for any purpose. Any derived versions of this
* software must be clearly marked as such, and if the derived work is * WARRANTIES ARE DISCLAIMED. IN NO EVENT SHALL CORE SDI S.A. BE * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
* incompatible with the protocol description in the RFC file, it must be * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY OR GOODS
* called by a name other than “ssh” or “Secure Shell”. * CONSEQUENTIAL DAMAGES RESULTING FROM THE USE OR MISUSE OF THIS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* SOFTWARE. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
[Tatu continues] * STRICT
* However, I am not implying to give any licenses to any patents or * Ariel Futoransky <[email protected]> * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
* copyrights held by third parties, and the software includes parts that * <http://www.core-sdi.com> WAY
* are not under my direct control. As far as I know, all included * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* source code is used in accordance with the relevant license agreements 3) * SUCH DAMAGE.
* and can be used freely for any purpose (the GNU license being the most ssh-keyscan was contributed by David Mazieres under a BSD-style
* restrictive); see below for details. license. 6)
Remaining components of the software are provided under a standard
[However, none of that term is relevant at this point in time. All of * Copyright 1995, 1996 by David Mazieres <[email protected]>. 2-term BSD licence with the following names as copyright holders:
*

INDEX
these restrictively licenced software components which he talks about
have been removed from OpenSSH, i.e., * Modification and redistribution in source and binary forms is Markus Friedl
* permitted provided that due credit is given to the author and the Theo de Raadt
- RSA is no longer included, found in the OpenSSL library * OpenBSD project by leaving this copyright notice intact. Niels Provos
- IDEA is no longer included, its use is deprecated Dug Song
- DES is now external, in the OpenSSL library 4) Aaron Campbell
- GMP is no longer used, and instead we call BN code from OpenSSL The Rijndael implementation by Vincent Rijmen, Antoon Bosselaers Damien Miller
- Zlib is now external, in a library and Paulo Barreto is in the public domain and distributed Kevin Steves
- The make-ssh-known-hosts script is no longer included with the following license: Daniel Kouril
- TSS has been removed Wesley Griffin
* @version 3.0 (December 2000) Per Allansson
46
 Nils Nordman * The above copyright notice and this permission notice shall be included *
Simon Wilkinson Apart from the previously mentioned licenses, various pieces of code * in all copies or substantial portions of the Software. *
in the openbsd-compat/ subdirectory are licensed as follows: * *
Portable OpenSSH additionally includes code from the following copyright * THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS *
holders, also under the 2-term BSD license: Some code is licensed under a 3-term BSD license, to the following * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF *
copyright holders: * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
Ben Lindstrom *
Tim Rice Todd C. Miller * IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, *
Andre Lucas Theo de Raadt * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
Chris Adams Damien Miller *

INSTALLATION
Corinna Vinschen Eric P. Allman * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
Cray Inc. The Regents of the University of California *
Denis Parker Constantin S. Svintsoff * THE USE OR OTHER DEALINGS IN THE SOFTWARE. *
Gert Doering * *
Jakob Schlyter * Redistribution and use in source and binary forms, with or without * Except as contained in this notice, the name(s) of the above copyright *
Jason Downs * modification, are permitted provided that the following conditions * holders shall not be used in advertising or otherwise to promote the *
Juha Yrjölä * are met: * sale, use or other dealings in this Software without prior written *
Michael Stone * 1. Redistributions of source code must retain the above copyright * authorization. *
Networks Associates Technology, Inc. * notice, this list of conditions and the following disclaimer. ****************************************************************************/
Solar Designer * 2. Redistributions in binary form must reproduce the above copyright ----------------------------------------------------------------------------
Todd C. Miller * notice, this list of conditions and the following disclaimer in the -
Wayne Schroeder * documentation and/or other materials provided with the distribution. - Module: freebsd-libc
William Jones * 3. Neither the name of the University nor the names of its contributors -

CONFIGURATION
Darren Tucker * may be used to endorse or promote products derived from this software ----------------------------------------------------------------------------
Sun Microsystems * without specific prior written permission.
The SCO Group * # @(#)COPYRIGHT 8.2 (Berkeley) 3/21/94
Daniel Walsh * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS’’ AND
Red Hat, Inc * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite
Simon Vallet / Genoscope * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR Releases is copyrighted by The Regents of the University of California.
PURPOSE
* Redistribution and use in source and binary forms, with or without * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
* modification, are permitted provided that the following conditions * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL The Regents of the University of California. All rights reserved.
* are met: * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
* 1. Redistributions of source code must retain the above copyright GOODS Redistribution and use in source and binary forms, with or without
* notice, this list of conditions and the following disclaimer. * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) modification, are permitted provided that the following conditions
* 2. Redistributions in binary form must reproduce the above copyright * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, are met:
* notice, this list of conditions and the following disclaimer in the * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN 1. Redistributions of source code must retain the above copyright

OPERATION
* documentation and/or other materials provided with the distribution. ANY notice, this list of conditions and the following disclaimer.
* * WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 2. Redistributions in binary form must reproduce the above copyright
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS’’ AND ANY EXPRESS OR * SUCH DAMAGE. notice, this list of conditions and the following disclaimer in the
* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED documentation and/or other materials provided with the distribution.
WARRANTIES Some code is licensed under an ISC-style license, to the following copyright holders: 3. All advertising materials mentioning features or use of this software
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE must display the following acknowledgement:
DISCLAIMED. Internet Software Consortium. This product includes software developed by the University of
* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, Todd C. Miller California, Berkeley and its contributors.
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, Reyk Floeter 4. Neither the name of the University nor the names of its contributors
BUT Chad Mynhier may be used to endorse or promote products derived from this software
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF without specific prior written permission.
USE, * Permission to use, copy, modify, and distribute this software for any

INFORMATION
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON * purpose with or without fee is hereby granted, provided that the above THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS’’ AND

FURTHER
ANY * copyright notice and this permission notice appear in all copies. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE * THE SOFTWARE IS PROVIDED “AS IS” AND TODD C. MILLER DISCLAIMS ALL PURPOSE
OF * WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL TODD C. MILLER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
8) Portable OpenSSH contains the following additional licenses: DAMAGES OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
a) md5crypt.c, md5crypt.h ACTION STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
* OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* “THE BEER-WARE LICENSE” (Revision 42): * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. SUCH DAMAGE.
* <[email protected]> wrote this file. As long as you retain this
* notice you can do whatever you want with this stuff. If we meet Some code is licensed under a MIT-style license to the following copyright holders: The Institute of Electrical and Electronics Engineers and the American
* some day, and you think this stuff is worth it, you can buy me a National Standards Committee X3, on Information Processing Systems have

INDEX
* beer in return. Poul-Henning Kamp Free Software Foundation, Inc. given us permission to reprint portions of their documentation.

b) snprintf replacement * Permission is hereby granted, free of charge, to any person obtaining a * In the following statement, the phrase ``this text’’ refers to portions
* copy of this software and associated documentation files (the * of the system documentation.
* Copyright Patrick Powell 1995 * “Software”), to deal in the Software without restriction, including *
* This code is based on code written by Patrick Powell * without limitation the rights to use, copy, modify, merge, publish, * Portions of this text are reprinted and reproduced in electronic form in
* ([email protected]) It may be used for any purpose as long as this * distribute, distribute with modifications, sublicense, and/or sell * the second BSD Networking Software Release, from IEEE Std 1003.1-1988, IEEE
* notice remains intact on all source code distributions * copies of the Software, and to permit persons to whom the Software is * Standard Portable Operating System Interface for Computer Environments
* furnished to do so, subject to the following conditions: * (POSIX), copyright C 1988 by the Institute of Electrical and Electronics
c) Compatibility code (openbsd-compat) * * Engineers, Inc. In the event of any discrepancy between these versions
47
and the original IEEE Standard, the original IEEE Standard is the referee ---------------------------------------------------------------------------- Some files in this package are licensed under the 4-clause BSD license,
document. - the copyright on most of them belongs to The Regents of the University
- Module: libpcap of California. Since the license was retroactively changed in 1999 to
In the following statement, the phrase ``This material’’ refers to portions - remove the advertising clause, they are effectively under the 3-clause
of the system documentation. ---------------------------------------------------------------------------- license even if the text of the license in the files hasn’t been
updated. See the following document for more details:
This material is reproduced with permission from American National Copyright (C) 1993-2008 The Regents of the University of California.
Standards Committee X3, on Information Processing Systems. Computer and ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change>
Business Equipment Manufacturers Association (CBEMA), 311 First St., NW, Redistribution and use in source and binary forms, with or without
Suite 500, Washington, DC 20001-2178. The developmental work of modification, are permitted provided that the following conditions Other files under the 4-clause BSD license and whose copyright doesn’t

INSTALLATION
Programming Language C was completed by the X3J11 Technical Committee. are met: belong to the The Regents of the University of California are listed
below:
The views and conclusions contained in the software and documentation are 1. Redistributions of source code must retain the above copyright - aodv.h, Copyright (c) 2003 Bruce M. Simpson
those of the authors and should not be interpreted as representing official notice, this list of conditions and the following disclaimer. - atmuni31.h, Copyright (c) 1997 Yen Yen Lim and North Dakota State University
policies, either expressed or implied, of the Regents of the University 2. Redistributions in binary form must reproduce the above copyright - ieee802_11.h, Copyright (c) 2001 Fortress Technologies and Charlie Lenahan
of California. notice, this list of conditions and the following disclaimer in - print-802_11.c, Copyright (c) 2001 Fortress Technologies and Charlie Lenahan
the documentation and/or other materials provided with the - print-aodv.c, Copyright (c) 2003 Bruce M. Simpson
---------------------------------------------------------------------------- distribution. - print-ascii.c, Copyright (c) 1997, 1998 The NetBSD Foundation, Inc.
- 3. The names of the authors may not be used to endorse or promote - print-cnfp.c, Copyright (c) 1998 Michael Shalayeff
- Module: strace products derived from this software without specific prior - print-gre.c, Copyright (c) 2002 Jason L. Wright
- written permission. - print-mobile.c, Copyright (c) 1998 The NetBSD Foundation, Inc.
---------------------------------------------------------------------------- - print-sunatm.c, Copyright (c) 1997 Yen Yen Lim and North Dakota State
THIS SOFTWARE IS PROVIDED ``AS IS’’ AND WITHOUT ANY EXPRESS OR University

CONFIGURATION
Copyright (c) 1991, 1992 Paul Kranenburg <[email protected]> IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED - print-telnet.c, Copyright (c) 1997, 1998 The NetBSD Foundation, Inc.
Copyright (c) 1993 Branko Lankester <[email protected]> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. - print-timed.c, Copyright (c) 2000 Ben Smithurst
Copyright (c) 1993 Ulrich Pegelow <[email protected]> - missing/inet_aton.c, Copyright (c) 1995, 1996, 1997 Kungliga Tekniska
Copyright (c) 1995, 1996 Michael Elizabeth Chastain <[email protected]> ---------------------------------------------------------------------------- Högskolan (Royal Institute of Technology, Stockholm,
Copyright (c) 1993, 1994, 1995, 1996 Rick Sladkey <[email protected]> - Sweden).
Copyright (C) 1998-2001 Wichert Akkerman <[email protected]> - Module: tcpdump - missing/inet_ntop.c, Copyright (c) 1995, 1996, 1997 Kungliga Tekniska
Copyright (C) 2001-2017 The strace developers. - Högskolan (Royal Institute of Technology, Stockholm,
All rights reserved. ---------------------------------------------------------------------------- Sweden).
- missing/inet_pton.c, Copyright (c) 1995, 1996, 1997 Kungliga Tekniska
Redistribution and use in source and binary forms, with or without Licensed under the 3-clause BSD license: Högskolan (Royal Institute of Technology, Stockholm,
modification, are permitted provided that the following conditions Sweden).
are met: Redistribution and use in source and binary forms, with or without
1. Redistributions of source code must retain the above copyright modification, are permitted provided that the following conditions
notice, this list of conditions and the following disclaimer. are met:

OPERATION
2. Redistributions in binary form must reproduce the above copyright ----------------------------------------------------------------------------
notice, this list of conditions and the following disclaimer in the 1. Redistributions of source code must retain the above copyright -
documentation and/or other materials provided with the distribution. notice, this list of conditions and the following disclaimer. - Module: ssmping
3. The name of the author may not be used to endorse or promote products 2. Redistributions in binary form must reproduce the above copyright -
derived from this software without specific prior written permission. notice, this list of conditions and the following disclaimer in ----------------------------------------------------------------------------
the documentation and/or other materials provided with the
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS’’ AND ANY EXPRESS OR distribution. Copyright (C) 2005, 2006 Stig Venaas <[email protected]>
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 3. The names of the authors may not be used to endorse or promote
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. products derived from this software without specific prior Permission to use, copy, modify, and distribute this software for any
IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, written permission. purpose with or without fee is hereby granted, provided that the above
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT copyright notice and this permission notice appear in all copies.
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, THIS SOFTWARE IS PROVIDED ``AS IS’’ AND WITHOUT ANY EXPRESS OR

INFORMATION
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED

FURTHER
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

INDEX
48
 INSTALLATION
CONFIGURATION
www.adder.com

OPERATION
INFORMATION
FURTHER
INDEX
© 2022 Adder Technology Limited
All trademarks are acknowledged.
Documentation by: www.ctxd.com
Part No. MAN-XDIP-ADDER • Release 1.7
49
Index
A E M R U

INSTALLATION
Adapters Enable Remote Control 24 Manage Ports page Rack mount bracket 7 USB
video 9 receiver 23 Recovery mode 33 indicator 33
Admin menus 21 F transmitter 28 Remote Control 24 UTP 37
Advanced page Fast-Leave Matrix 3 Remote Logging Address 25,29
receiver 24 IGMP 35 Menu Remote Support 25,29 V
transmitter 29 File systems admin 21 Reset 20 VID
API 38 supported 26 Mounting 7 Reset button 4 indicator 33
Audio connections 12 FTP 37 REST API 3,38 Video format

CONFIGURATION
N Restore node 20 conversion 9,10
C G Navigation Video resolutions
Cable types 37 General Settings page of menus 14 S maximum 8
Category rating 37 receiver 21 Network switch Screening 37
Channel List 17 transmitter 27 specifications 12 Setup Channels page 27 W
Channels Node Severity Level 25,29 Wizard
switching 31 H restore 20 Shielding 37 configuration 14
Configuration wizard 14 Hotkeys 22 Snooping
Y

OPERATION
Connections channel switching 31 O IGMP 35
audio 12 configuring 32 Optional extras 6 Software Upgrade page YAML 38
computer 8 OSD Mouse Launch 22 receiver 26
console 11 I OSD Settings page 22 transmitter 30
link 12 IGMP 35 OSD Timeout 22 SoL 16
overview 7 Indicators 33 Start of Life 16
power 13 Interference P Static IP address 24
protection 37 PiMF 37

INFORMATION
Crosstalk 37 STP 37

FURTHER
Internet Group Management PoE 12 Supplied items 5
D Protocol 35 Power connection 13 Supported file systems 26
Disconnect Power over Ethernet 12 Switching channels 31
from channel 31 K Public REST API 38
DisplayPort 9 Keyboard navigation 14 PWR T
DVI 9 indicator 33 Transmitter node
L
Dynamic IP address 24 add 18
Link connection 12

INDEX
LNK
indicator 33

50