How to check the connection to a KNXnet/IP router or interface

Owned by Wolfgang Granzer
Last updated: Feb 29, 2024 by Robert Schneider
4 min read

Our KNX interface uses KNXnet/IP tunneling to communicate to the KNX network. Therefore, any standard conform KNXnet/IP router or interface can be used.

KNXnet/IP routers and interfaces must not be monitored by the NETx Server! During the monitoring process, our server opens a KNX management connection (for more details see ). Some KNXnet/IP routers and interfaces will reboot and close all tunneling connections after closing a KNX management connection. Therefore, unwanted disconnects of the KNXnet/IP connection will occur.

Please use the GATEWAY item to monitor the state of a KNXnet/IP router or interface instead.

Within the Item Tree of the server, the GATEWAY item indicates the connection state to a KNXnet/IP router or interface. If it is true, the connection is working – if it is false there is a communication problem. The following figure shows an example where the connection to a KNXnet/IP router is successfully established.

In addition, the Status item provides an error code if the connection is not working:

Status code (decimal)

Status code (hex)

Description

Status code (decimal)

Status code (hex)

Description

33

0x21

The KNXnet/IP router or interface cannot find an active data connection with the specified ID. This may indicate that the KNXnet/IP router or interface restarted and lost the connection IDs. Possible reason for a restart may be too much traffic at the KNX bus, a hardware failure or problems with the power supply.

34

0x22

The requested connection type is not supported by the KNXnet/IP router or interface.

35

0x23

One or more requested connection options are not supported by the KNXnet/IP router or interface.

36

0x24

No KNXnet/IP tunneling connection is available. A KNXnet/IP router or interface only supports a limited amount of simultaneous connections. Old devices only one – newer devices (like our NETx KNX IP Router and Interface) up to eight. Please check whether any other client (e.g. ETS) is also connected to the router or interface.

37

0x25

No free KNX individual address available for the tunneling connection. Please check your ETS project whether all available tunneling connections are assigned to a KNX individual address. For older KNXnet/IP routers or interfaces, additional addresses may be activated by pressing the programming button for at least five seconds. Please check the datasheet of your device.

38

0x26

The KNXnet/IP router or interface detects an error concerning the data connection with the specified ID.

39

0x27

The KNX connection to the router or interface is not working. Please check the twisted pair side of your router or interface.

40

0x28

Security authentication error.

45

0x2D

No free tunneling address.

46

0x2E

Connection is already in use.

1000

 

Network problem. The server is not able to establish a UDP connection to router or interface. Check your firewall, network and all network switches and routers inbetween. Ensure that the respective UDP packets reach the target device and that the response is transported back to the server. Be cautious with stateful firewalls towards the server and make sure that incoming UDP packets are accepted.

1001

 

State request timeout.

1002

 

Invalid commissioning password. Please verify that the password used in the gateway definitions is the same as used in ETS.

1003

 

Invalid authentication code. Please verify that the code used in the gateway definitions is the same as used in ETS.

1004

 

The configured individual address differs from the chosen one.

1005

 

Session timeout.

1006

 

Invalid telegram received.

1007

 

Unknown telegram received.

1008

 

Connection lost.

1009

 

Invalid individual address.

1010

 

Session closed by foreign device.

1999

 

Unknown error. Please contact the NETx support team.

If the status is 1000, there is a network problem. To further analyze the problem, check your firewall, network and all network switches and routers. KNXnet/IP tunneling uses UDP/IP for communication, the default UDP port is 3671. Please ensure that a UDP communication with port 3671 is possible between the server and the KNXnet/IP router or interface.

To analyze the network, please do not use the "ping" command. Ping uses the ICMP protocol. This means that even if a ping is successful it does not indicate that a UDP/IP connection is possible. Even more, each standard network device will reply to ping requests – even if it is not a KNXnet/IP router or interface.

For a meaningful analyzes you can use the following tools:

  • Wireshark: A comprehensive, free network monitoring tool. Using Wireshark, you can sniff all incoming and outgoing network packets. Since 2016, Wireshark also includes a KNXnet/IP decoder.

  • nxaKNXnetIPTestTool.exe: this is a small console application which is included within the setup of the server. It can be used to test KNXnet/IP tunneling connections.

The nxaKNXnetIPTestTool.exe Tool is located within the following directory: <installation directory>\Tools\KNXnetIP

Usage: KNXnetIP <Dst IP Address> [Src IP Address]

To use the tool, open a Windows "cmd" shell and change to the directory mentioned above. Then invoke the command with the IP address of the KNXnet/IP router or interface as parameter that you would like to test. The second parameter is the local IP address which is optional.

To check the router of the IP address 192.168.1.36, the following command has to be entered:

Within the output of the command, the raw KNXnet/IP packets are shown. In addition, it is shown whether the connection was successful – if not the error code is shown, too.

Article applies to the following products:

  • NETx BMS Platform

  • NETx Multi Protocol Server

  • NETx BMS Server 2.0