The transfer of configuration data when working with LANconfig can be handled by various protocols: HTTPS, SSH, HTTP or TFTP.
Widely available protocols are defined globally. In addition, it is possible to disable protocols for specific devices. However, it is not possible to re-enable a globally disabled protocol for an individual device.
Configuration of the global communication settings
The configuration of the communication protocols differentiates between the protocol strictly for testing the device and the protocols for other operations, such as firmware uploads, etc.:
LANconfig:
- HTTPS, SSH, HTTP, TFTPWhen this is selected, you enable the individual protocols for the operations firmware upload, configuration up/download, and script up/download. In these operations, LANconfig attempts to use these protocols in the order HTTPS, SSH, HTTP and TFTP. If the transfer fails when using one of the selected protocols, LANconfig automatically tries the next protocol.
- Prefer checks via TFTPThe device evaluation only transfers small amounts of data with the system information. As such, it makes sense to perform device checks in the LAN by TFTP protocol. When this option is activated, LANconfig first uses the TFTP protocol to check the device, regardless of the communication protocols set previously. If the check via TFTP fails, then LANconfig attempts the protocols HTTPS, SSH, and HTTP.
- Using public key authenticationIf you have selected the SSH protocol, you can alternatively perform the authentication via a private key. In this case, the authentication dialog for password entry is not invoked. Enter the path to your private key file in the fields, and, if necessary, the passphrase that you used to encrypt the file. Load the corresponding public key with LANconfig or WEBconfig onto each device.
Note: The global communication settings take precedence over the device-specific settings in order to prevent, for example, the central use of a protocol.