- Intended For:
- Customer Admin/IT
- Prerequisite Skills:
- Working with xml files
- Estimated Time to Complete:
- 10 minutes
- Applies to Software/Firmware Version(s):
The 4.0.7 firmware supports updated features that can be implemented using the 4RE configuration xml file or the domaintoConfigv1.xsl file for Evidence Library.
This article will describe the new 4RE feature, the corresponding xml nodes (i.e.
<Language>0</Language>), the acceptable values, and where to place them in the configuration file.
The 4RE configuration xml file can be found in a deployed configuration. Manually deploy a configuration to a USB flash drive.
The domaintoConfigv1.xsl file is located in
“Program Files\WatchGuard Video\Hosted
and you will need to open Notepad as an administrator to modify it.
Always make a backup of the configuration file before modifying!
A key feature in the 4RE 4.0.7 firmware is support for cellular uploads. Below is an example of the
<NetworkConfiguration> tag with the newly added entries. Note that these tags can be placed anywhere within the
<SecondaryBackendServer> elements should only contain IP addresses for the primary and secondary backend servers. The
<SecondaryBackendServer> is typically a public IP address that can be reached when the 4RE is connected via LTE.
Backend Server Domain Name
If the server is defined by a domain name, then the
<SecondaryBackendServerDomainName> element should be used for the primary and secondary servers respectively.
If there is no configuration for the primary server but either the secondary backend server IP address or domain name or both is defined, the 4RE will consider that an invalid configuration file and will not work.
If both an IP address and a domain name are defined for a backend server, the system will first try to resolve the domain name using the specified DNS servers. It will not assume that the IP address configured will resolve to the same IP address as the DNS uses for the domain name.
<DnsServer2> elements are used to specify up to two different DNS servers; there is no correlation to using DNS server 1 to resolve the primary domain name and DNS server 2 to resolve the secondary domain name. The two servers provide up to two ways to resolve the domain names.
<PortForwarding> element is intended to be used when the LTE path is provided using an LTE dongle on the MDC laptop. In this case, the 4RE uses destination natting commands to route the packets intended for the backend server to the MDC. The MDC will be running a port proxy script that then forwards the packets received from the 4RE to the backend server.
Encrypt Backend Server
<EncryptBackendServer> element, if set to true, will configure the SPS to first encrypt and then route packets received from the 4RE to the primary backend server. The
<EncryptSecondaryBackendServer> element does the same thing only for the secondary server path. These tags take a true or false value. The 4RE configures the stunnel configuration file on the Smart Power Switch (SPS) using other values in the configuration file.