KNXnet/IP | ETS
The EIBPORT has an integrated KNXnet/IP server. This server enables KNXnet/IP communication for system coupling using KNXnet/IP routing and provides an interface for the ETS commissioning software (KNXnet/IP tunnelling).
KNXnet/IP tunneling
KNXnet/IP tunnelling is used to establish a connection between ETS and EIBPORT, to program KNX devices or to monitor KNX data traffic (bus monitor). KNXnet/IP tunnelling is a point-to-point connection and is based on "unicast" (communication types / routing schemes). To establish a "tunnelling" connection from the ETS to the EIBPORT, please proceed as described in chapter Using EIBPORT as ETS commissioning interface.
PORT (UDP) | 3671 |
KNXnet/IP routing
KNXnet/IP routing is used by so-called KNX IP routers to couple different lines and areas via the network. For this, a multipoint connection based on multicast is used (communication types / routing schemes).
Please note that, in more complex network structures, multicast is not automatically forwarded via switches and routers! Ensure that the involved devices can communicate via multicast prior to enabling them.
MULTICAST ADDRESS (standard) | 224.0.23.12 |
PORT | 3671 |
Preparations in EIBPORT / physical addressing
To enable the KNXnet/IP routing protocol, the EIBPORT's physical address must be at least defined as a line- or area coupler (at least one 0 in the physical address). For information on setting the physical address, see chapter Physical address.
You can then enable "Routing" using the option "System" > "KNXnet/IP" > "Enable: KNXnet/IP to EIB“and "Enable: "EIB to KNXnet/IP" for both directions.

Enabling KNXnet/IP routing