If a mainboard is not supported by the proxy, using 1:1 NAT may help.

The difference to the normal proxy mode is, that this option will route all requests from the customer's IP to the IPMI IP via NAT. This means that the HTTP/HTTPS requests are also forwarded directly to IPMI.
Normally a random port is used for KVM and HTTP/HTTPS connections are forwarded to IPMI via reverse proxy, which allows to set access rights via the ACL groups.

The use of this option is only recommended if you have problems with the normal proxy, it has the following technical disadvantages:

  • If a customer has multiple servers, he can only open one KVM session simultaneously
  • The customer can reach the IPMI webinterface even if access to IPMI is deactivated in the ACL group

How to activate 1:1 NAT (Module version 2.4.3 or higher)

The 1:1 NAT mode can be enabled or disabled for each ACL group individually:

  • Open the admin page of the module, click on "ACL Groups" at the navigation bar.
  • Click the "Proxy Settings" button on the affected ACL group.
  • Enable the "Enable 1:1 NAT" option and save the change.

How to activate 1:1 NAT (Module version below 2.4.3)

The feature can be activated via the customconfig.php file, which is located at /modules/servers/dedicated/

  • Navigate into the directory /modules/servers/dedicated/
  • Open the file customconfig.php, or create the file if it does not exist

  • Insert following line and save the file:

    $proxy_direct_traffic = 1;

  • If the file was newly created, you need to add a PHP tag at the beginning:

    <?php
$proxy_direct_traffic = 1;

You still need to enable the proxy feature in the ACL group.

  • No labels