Media5 Mediatrix 4104, Reference Manual

Page: 66 / 466

Chapter 3 - Web Interface – Management Configuration File Download
44 Mediatrix 4104
Configuration Download Procedure
The following steps explain how to download configuration files from the web interface.

To download configuration files:
1. Set the configuration file server host and port as defined in “Configuration File Server Settings” on
page 39 .
2. Place the configuration files to download on the computer hosting the TFTP or HTTP server.
These files must be in a directory under the TFTP root path.
3. If not already done, set the transport protocol and configuration file path as described in “Setting up
the Configuration File Download” on page 40 .
4. Initiate the configuration file download by setting the System Command drop-down menu of the
System – Admin Web Page to updateConfiguration .
The Mediatrix 4104 immediately downloads the configuration files. See “System Management” on
page 31 for more details on the system commands.
5. Click Submit .
Automatic Configuration Update
You can configure the Mediatrix 4104 to automatically update its configuration. This update can be done:

Every time the Mediatrix 4104 restarts.

At a specific time interval you can define.
NAT Variations
NAT treatment of UDP varies among implementations. The four treatments are:
• Full Cone: All requests from the same internal IP address and port are mapped to the same
external IP address and port. Furthermore, any external host can send a packet to the internal
host by sending a packet to the mapped external address.
• Restricted Cone: All requests from the same internal IP address and port are mapped to the
same external IP address and port. Unlike a full cone NAT, an external host (with IP address
X) can send a packet to the internal host only if the internal host had previously sent a packet
to IP address X.
• Port Restricted Cone: Similar to a restricted cone NAT, but the restriction includes port
numbers. Specifically, an external host can send a packet, with source IP address X and
source port P, to the internal host only if the internal host had previously sent a packet to IP
address X and port P.
• Symmetric: All requests from the same internal IP address and port, to a specific destination
IP address and port, are mapped to the same external IP address and port. If the same host
sends a packet with the same source address and port, but to a different destination, a
different mapping is used. Furthermore, only the external host that receives a packet can send
a UDP packet back to the internal host.
For more details on NAT treatments, refer to RFC 3489.
Note:
The configuration download via TFTP can only traverse NATs of types “Full Cone” or “Restricted
Cone”. If the NAT you are using is of type “Port Restricted Cone” or “Symmetric”, the file transfer will not
work.
Caution:
When downloading via HTTP, the configuration file server’s port must be 80. You can see the
actual port assigned in the Status section of the Configuration File page.
If you are using a DHCP server and it did not provide the proper port, reconfigure it with the proper port or
use a static configuration. See
“Configuration File Server Settings” on page 39 for more details.