+1 239 999 4122
+1 239 999 4122
Free Download

Knowledge Base

Back to support overview

The configuration of the FreeBSD can happen in different stages.

TeamViewer delivers the binary files as well as a recipe to create the package. The FreeBSD platform expects that the admin builds the package for his systems on his own. The following steps are not required if somebody just wants to get started.

📌Note: The acceptance of the EULA is not a “configuration” step. This is a mandatory step that has to be performed for every new installation as described in the Delivery and Usage Flow. The system itself is preventing the acceptance of the EULA during package installation.

Stage A – Packaging

Every customer can build his own package with the default configuration they want to have:

  1. Unpack the dist files package (not the ports package) and changes the teamviewer-iot-agent.conf located at ./etc/teamviewer-iot-agent/.This configuration file is logically the same as the file used for OEM packages on Linux. In this article, we will not describe each setting, as they are described in the file itself.
  2. After the configuration file has been changed, the whole unpacked dist folder needs to be packaged again using .tar.gz.
  3. A change in the configuration file require the customer to rerun the creation of the checksum: For that, the customer should unpack the ports file and run
setenv TV_PORT_MASTER_SITES 
sudo --preserve-env=TV_PORT_MASTER_SITES make makesum
sudo --preserve-env=TV_PORT_MASTER_SITES make package

Result: The package has the custom configuration included and can be installed on the target system.

Stage B – After the installation

It is mandatory to accept the EULA (see info box above).

The FreeBSD package will be shipped with agent.conf located at /etc/teamviewer-iot-agent/.

This configuration file is logically the same as the file used for OEM packages on Linux. In this article, we will not describe each setting, as they are described within the file. This file can be changed even if the agent is already running. A restart of the agent is required, so the changes are applied to the agent.