---
title: "Pool’nX KNX-IP settings: ETS tunneling, routing and address tables"
description: Set the individual addresses of the Pool’nX ETS tunneling connections, multicast routing and filter tables, or import the ETS filter table in HTML.
canonical: https://wiki.can-nx.com/en/guides/pool-local-knxip/
language: en
product: Pool’nX
audience:
  - administrateur
  - installateur
context: "Pool’nX local configuration site: KNX-IP and Address Tables pages"
---

# Pool’nX KNX-IP settings: ETS tunneling, routing and address tables

Context: Pool’nX local configuration site: KNX-IP and Address Tables pages

The local configuration site of the Pool’nX sets its KNX-IP part: individual addresses of the tunneling connections, multicast routing, acknowledgement tables and routing tables, which you can fill from an ETS export.

Intended for the KNX integrator who connects ETS or another KNXnet/IP client to the gateway, or who integrates it into a KNX IP network. To open the site, follow [signing in to the local configuration site](https://wiki.can-nx.com/en/guides/pool-local-config/).

## Before you start

- You are signed in to the local configuration site of the gateway.
- Plan free individual addresses on the KNX line and, for routing, the multicast address used by the other routers.

## Set tunneling and routing

1. In the menu, open **KNX-IP**. The **KNX-IP Settings** page shows the **Connection Settings** card.
2. **Port** shows the KNXnet/IP port of the gateway, **3671**, read-only.
3. In **Individual address**, fill in the individual addresses of the tunneling connections, for example **1.1.250** (example). Add a row with **+ Add individual address**, up to 16 addresses; remove one with **Remove**.
4. To connect the gateway to other KNX IP routers, tick **Routing** and fill in the **Multicast address**. The standard KNX multicast address is 224.0.23.12.
5. Click **Save**. **KNX-IP settings saved** confirms the save.

Each simultaneous tunneling connection, from ETS or from a visualization, uses one individual address. Choose free addresses on the KNX line.

The **Bus Voltage Monitoring** card on the same page is set with its **Interval (minutes)** and its **KNX Address**, then its own **Save** button.

## Connect ETS in tunneling mode

1. In ETS, add a KNXnet/IP connection to the local IP address of the gateway, port **3671**.
2. Choose tunneling mode and test the connection.
3. Open the ETS group monitor to check that the bus telegrams arrive.

ETS reaches the gateway at its local IP address: the computer running ETS must be able to reach this address on the network.

## Fill in the acknowledgement tables

1. Open **Adresses Tables**, then the **Acknowledge tables:** section.
2. In **Group addresses ACK** and **Physical addresses ACK**, add with **+ Add row** the addresses for which the gateway acknowledges telegrams on the KNX bus. Each table accepts up to 20 rows.
3. Click **Save**. **Tables saved successfully** confirms the save.

A row accepts an address or a pattern:

| Pattern | Group addresses | Physical addresses |
| --- | --- | --- |
| A single address | **1/2/3** | **1.2.3** |
| Wildcard on one level | **\*/2/4** | **\*.2.4** |
| Ranges | **1/2-7/5-9** | **1.2-7.5-9** |

## Filter routing between IP and KNX

The routing tables only appear if **Routing** is ticked on the **KNX-IP** page.

1. On the **Address Tables** page, open the **Group address forward** section.
2. Fill in **Group Address forward IP to KNX** and **Group Address forward KNX to IP**. Tick **Broadcast (0/0/0)** to also forward address 0/0/0 in the direction concerned.
3. In the **Physical address forward** section, fill in **Physical Address forward IP to KNX** and **Physical Address forward KNX to IP** in the same way. The **Physical address forward — Default** box sets the default forwarding of physical addresses.
4. Click **Save**.

## Import the ETS filter table

1. In ETS 5 or 6, export the filter table in HTML format.
2. On the **Address Tables** page, open **Import ETS file** and drop the .html file.
3. The **Replace routing tables?** window shows **This will replace the current GAfwdIP and GAfwdKNX routing tables with the addresses from the imported file.** Click **Replace**.
4. The message gives the number of address groups imported into the routing tables. Both group tables, from IP to the bus and from the bus to IP, receive the same addresses.
5. Click **Save** to save the imported tables.

## Check the result

- Reload **KNX-IP** and **Address Tables**: the addresses entered are kept.
- The ETS tunneling connection succeeds and its group monitor shows the telegrams.
- With routing, send a value from the IP network to a filtered address and check that it is received on the bus in [the group monitor of the gateway](https://wiki.can-nx.com/en/guides/pool-local-monitoring/).

## Troubleshooting

| Message or symptom | Cause and action |
| --- | --- |
| Tunneling connection refused | All the individual addresses are in use. Add an address in **Individual address**, then save. |
| **Group address forward** section missing from **Address Tables** | **Routing** is not ticked. Tick it on the **KNX-IP** page and save. |
| **No group addresses found in this file** | The file is not an HTML export of an ETS filter table. Export it again from ETS. |
| **+ Add row** button missing | The table already has 20 rows. Group addresses together with a pattern. |
| **Failed to save** or **Failed to save tables** | The save did not succeed. Reload the page and save again. |

For other situations, see [Pool’nX troubleshooting](https://wiki.can-nx.com/en/guides/pool-help/). If the problem persists, write to support@can-nx.com with the gateway name and the page concerned.