---
title: Things to Check if the MTC Is Not Working
slug: kron-pam-installation-guides-v3/things-to-check-if-the-mtc-is-not-working
createdAt: 2026-11-20T15:23:13.314Z
---

**1)** Check that Secure Boot is disabled on both the Kron PAM Server and the Multi Tenant Connector; if it is enabled, WireGuard might not work:

| **Linux CLI** | **\[root\@connector\~]#** mokutil --sb-state |
| ------------- | -------------------------------------------- |

**2)** Check the WireGuard configuration file on the Kron PAM Server and the Multi Tenant Connector:

| **Linux CLI** | **\[root\@pam\~]#** cat /etc/wireguard/wg-vpn-&#x7B;port-number}.conf                                                                                                                                                                                                                                                                                                                                      |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Example**   | **\[root\@pam\~]#** cat /etc/wireguard/wg-vpn-10001.conf<br />\[Interface]<br />PrivateKey = AAA231425CfCy55zsfG/37XkIZmngeV8az+XXXXXX=<br />Address = **192.168.0.2/32**<br />Endpoint = $&#x7B;VPN\_NODE\_IP}:$&#x7B;TUNNEL\_PORT}<br />ListenPort = 10001<br />\[Peer]<br />PublicKey = AAAyno14GRH7aadq6cBzATMg8bVB3Ac5Ry3KuXXXXXX=<br />AllowedIPs = **192.168.0.1/32**<br />PersistentKeepalive = 25 |

| **Linux CLI** | **\[root\@connector\~]#** cat /etc/wireguard/wg-vpn-&#x7B;port-number}.conf                                                                                                                                                                                                                                                                                                               |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Example**   | **\[root\@connector\~]#** cat /etc/wireguard/wg-vpn-10001.conf<br />\[Interface]<br />PrivateKey = BBBlD/N5r2ff1pfIxu2d5aYk3cppDeDiXZjtBYYYYYY=<br />Address = **192.168.0.1/32**<br />ListenPort = 10001<br />\[Peer]<br />PublicKey = BBByno14GRH7aadq6cBzATMg8bVB3Ac5Ry3KuYYYYYY=<br />AllowedIPs = **192.168.0.2/32**<br />Endpoint = 10.10.10.10:10001<br />PersistentKeepalive = 25 |

Ping the Kron PAM Server's WireGuard IP address and the Multi Tenant Connector's WireGuard IP address on both environments (you should see that messages are received/sent).

| **Linux CLI** | **\[root\@pam\~]#** ping \{Multi Tenant Connector's WireGuard IP}<br />**\[root\@connector\~]#** ping \{Kron PAM Server's WireGuard IP} |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Example**   | **\[root\@pam\~]#** ping 192.168.0.1<br />**\[root\@connector\~]#** ping 192.168.0.2                                                    |

**2.1) (MTC Inbound)** If the **latest handshake** field is empty in the **wg show wg-vpn-\{Tunnel Port}** output on the Kron PAM Server, restart the WireGuard interface of the node on the Kron PAM Server (see Section 8.4):

| **Linux CLI** | **\[root\@pam\~]#** wg-quick down wg-vpn-\{Tunnel Port}<br />**\[root\@pam\~]#** wg-quick up wg-vpn-\{Tunnel Port} |
| ------------- | ------------------------------------------------------------------------------------------------------------------ |

**3)** Check the iptables rules on the Multi Tenant Connector machine:

| **Linux CLI** | **\[root\@connector\~]#** iptables -t nat -nvL |
| ------------- | ---------------------------------------------- |

**4)** Check the status of pam-connector.service on the Multi Tenant Connector machine:

| **Linux CLI** | **\[root\@connector\~]#** sudo systemctl status pam-connector.service |
| ------------- | --------------------------------------------------------------------- |

**5)** Check the port allowance at the server level that is defined in the firewalld service, and stop the firewalld service if it is not needed:

| **Linux CLI** | **\[root\@connector\~]#** sudo firewall-cmd --list-ports<br />**\[root\@connector\~]#** sudo systemctl stop firewalld |
| ------------- | --------------------------------------------------------------------------------------------------------------------- |

**6)** Check the heartbeat messages on the Tenant Connector page of the Kron PAM Web GUI:

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/1xvP2XexeFwHCGoRMK8Jm_image.png "Tenant Connector Screen")

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/cr_beBIGc5--zFduRPnJb_image.png "Heartbeat Chart on the Kron PAM Web GUI")

**7)** Check the IP routing configuration on the Multi Tenant Connector. The result should be 1; if it is 0, enable IP routing by setting it to 1:

| **Linux CLI** | **\[root\@connector\~]#** sysctl net.ipv4.ip\_forward<br />**\[root\@connector\~]#** sysctl -w net.ipv4.ip\_forward=1 |
| ------------- | --------------------------------------------------------------------------------------------------------------------- |

**8)** Check the SELinux security mode on the Multi Tenant Connector. The result should be permissive; if it is enforcing, select the permissive security mode:

| **Linux CLI** | **\[root\@connector\~]#** getenforce<br />**\[root\@connector\~]#** setenforce 0 |
| ------------- | -------------------------------------------------------------------------------- |

**9)** Check **connector.log** under **/pam/gui/logs** on the Kron PAM Server during the Multi Tenant Connector installation (after pressing the **SAVE** button on the GUI):

| **Linux CLI** | **\[root\@pam\~]#** tail -1000f /pam/gui/logs/connector.log |
| ------------- | ----------------------------------------------------------- |

**10)** Check catalina.out and localhost\_access\_log.&#x7B;YEAR-MONTH-DAY}.txt under **/pam/gui/logs** on the Kron PAM Server during the session opened on the device assigned to the Multi Tenant Connector:

| **Linux CLI** | **\[root\@pam\~]#** tail -1000f /pam/gui/logs/catalina.out<br />**\[root\@pam\~]#** tail -1000f /pam/gui/logs/localhost\_access\_log.&#x7B;YEAR-MONTH-DAY}.txt |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |

**11)&#x20;**<u>**(Through the Multi Tenant Connector or Direct Access Check)**</u> If the Kron PAM Server can somehow access the remote devices directly (for instance, in test environments, both the Kron PAM Server and the Multi Tenant Connector can be in the same network), make sure whether the remote devices are accessed directly or through the Multi Tenant Connector by using tcpdump (to install: **sudo dnf install tcpdump**):

| **Linux CLI** | **\[root\@connector\~]#** tcpdump -i any host \{MTC's WireGuard IP} and port \{Target Device's Virtual Port assigned by Kron PAM Server} -vv |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Example**   | **\[root\@connector\~]#** tcpdump -i any host 192.168.0.1 and port 40000 -vv                                                                 |

If tcpdump doesn't capture any message during a **successful session**, the target device is accessed <u>**directly**</u> by the Kron PAM Server; whereas, if tcpdump captures lots of messages, the target device is accessed through the <u>**Multi Tenant Connector**</u>.

**12)&#x20;**<u>**(WireGuard Communication Check) LASTLY, please ask the customer to check their firewall at the network level.**</u> You can understand whether the network-level firewall blocks the secure tunnel messaging by executing the **sudo wg show** command and checking its result (if the transfer line is 0, the network-level firewall blocks the messages through the WireGuard port):

| **Linux CLI** | **\[root\@connector\~]#** sudo wg show<br />interface: wg-vpn-10001<br />listening port: 10001<br />peer: AAAyno14GRH7aadq6cBzATMg8bVB3Ac5Ry3KuXXXXXX=<br />endpoint: 10.10.10.10:10001<br />allowed ips: 192.168.0.2/32<br /><font color="#EF4444">**transfer\: 0 B received, 0 B sent**</font><br />persistent keepalive: every 25 seconds |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

To make sure whether the network-level firewall blocks the secure tunnel messaging, use netcat (to install: **sudo dnf install nc**) to send UDP packets and tcpdump to verify their reception, on both sides: 1) from the Multi Tenant Connector to the Kron PAM Server and 2) from the Kron PAM Server to the Multi Tenant Connector. <u>**Please do not rely on messages**</u> such as "UDP packet sent successfully" displayed by netcat; the only reliable way to verify UDP communication is to confirm packet transmission and reception using tcpdump on both ends.

<u>**Side 1**</u> (from the Multi Tenant Connector to the Kron PAM Server):

| **Linux CLI** | **\[root\@pam\~]#** tcpdump -i any port \{WireGuard UDP Port}<br />**\[root\@connector\~]#** nc -u -vz \{public IP address of Kron PAM Server} \{WireGuard UDP Port} |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Example**   | **\[root\@pam\~]#** tcpdump -i any port 10000<br />**\[root\@connector\~]#** nc -u -vz 1.1.1.1 10000                                                                 |

<u>**Side 2**</u> (from the Kron PAM Server to the Multi Tenant Connector):

| **Linux CLI** | **\[root\@connector\~]#** tcpdump -i any port \{WireGuard UDP Port}<br />**\[root\@pam\~]#** nc -u -vz \{public IP address of Multi Tenant Connector} \{WireGuard UDP Port} |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Example**   | **\[root\@connector\~]#** tcpdump -i any port 10000<br />**\[root\@pam\~]#** nc -u -vz 2.2.2.2 10000                                                                        |

