Tunneling – General information
9
TUNNELING – GENERAL INFORMATION
Since version 0x110B / 0x118B of AVM500-ES firmware, multiple tunneling communications can be built, depending on the
network architecture. This chapter will illustrate the more common cases that you can face when using an AVM500-ES.
9.1 Ex. 1: Communication between AVY16-ES100 and Serial Port
In this example, we want to build a tunneling between an AVY16-ES100, and AVM500-ES physical serial port. This can be
used to remote control Yamaha AD8HR that is not fed with AVKit.
9.1.1
AVY16-ES100 is plugged on port B
Remember that port B is the port that owns the physical serial port. In this example, the whole configuration will be made in
AVM500-ES Port B control page. What we want to do here is to redirect the Serial port stream to the AVY16-ES100 in LS9,
and the AVY16-ES100 stream back to the Serial port.
Let’s see how to handle the control page:
-
The “Incoming Tunneling Data” is the data from the remote device, i.e. AVY16-ES100 in our example. It goes in port
B (because AVY16-ES100 is plugged on port B). We want this stream goes to AVM500-ES Serial port. That’s why
we choose “Serial Port” in “Egress Port for Tunneling” combo box.
-
The “Incoming Port Data” is the “internal” AVM500-ES data coming from any Port from A to E, or from Serial Port. If it
is coming from another port, the configuration is made in the corresponding port (we will see an example just after).
In our case, this data is coming from Serial Port. That’s why we can see in “Serial Port Configuration” box that the
physical Serial port is redirected to “Port B”. We want to send this stream to the AVY16-ES100, that why we choose
“LS9-1” in “Tunneling Destination” combo box.
-
Of course, to finish this configuration, we must go to AVY16-ES100 control page, and configure a Unicast up to
AVM500-ES Port B.
AVM500-ES User’s Manual v2.1
AuviTran 2010
40
Summary of Contents for AVM500-ES
Page 1: ...AVM500 ES User s Manual 1 ...
