Frequently asked questions (FAQ)

Why does bus monitoring not work?

This is by design. Due to the limitations of the N148, you cannot have a bus monitoring client in addition to a standard client. If you were to switch EIBnetmux to bus monitoring mode, all your clients would receive the monitored packets and they'd be on their own to deal with them. No matter if they expect such behaviour or not.

So, by default, EIBnetmux does not support bus monitor connection requests by EIBnet/IP clients (such as ETS), as this may create severe problems for other clients.

However, you may activate it by adding the command line parameter "--enable-busmonitor" when you run configure. Then, EIBnetmux allows clients to request a bus monitor connection, as long as no other EIBnet/IP clients are active. If a bus monitor connection has been established, all other clients will be blocked. EIBnetmux clients are not taken into account for this functionality. There is no guarantee whatsoever on what happens to them if you turn a bus monitor on (or off).

Why does searching not find EIBnetmux?

Make sure your Linux kernel supports IP multicasting (CONFIG_IP_MULTICAST=y, mrouter is not required). Also, the client performing the search and the EIBnetmux server must be in the same IP subnet (no router in between).

How do I write my own client software to connect to EIBnetmux?

Currently, there are two client libraries. One for C developers, one for PHP (a Python library is planned and will be available with one of the next releases). You can find their documentations here:

Sample applications can be downloaded from here.

You can also communicate directly with EIBnetmux, if you so desire. The protocol is documented here.