OH3 NetUtil Warning in log

Setup, Configuration and Use Beginners
1

I’m moving on from in Docker to OH3 in Docker and taking it very slowly in order to ensure that there is a clean OH system once it is finished. I’ve just installed OH3 and ran the first time setup. OH runs but looking at the log there is the following warning which seems odd to me since it is ignoring the IP address of the machine that OH3 is running on. (The OH2 version was stopped before starting with OH3.)

2021-03-31 19:14:46.264 [WARN ] [org.openhab.core.net.NetUtil        ] - Found multiple local interfaces - ignoring 192.168.0.5

The entire log is:

2021-03-31 19:14:43.775 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'America/Chicago'.
2021-03-31 19:14:43.791 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to '29.558997463465616,-95.35042226314546'.
2021-03-31 19:14:43.793 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'en_US'.
2021-03-31 19:14:46.264 [WARN ] [org.openhab.core.net.NetUtil        ] - Found multiple local interfaces - ignoring 192.168.0.5
2021-03-31 19:14:48.479 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2021-03-31 19:14:49.588 [INFO ] [org.openhab.ui.internal.UIService   ] - Started UI on port 18080
2021-03-31 19:14:49.935 [INFO ] [ab.ui.habpanel.internal.HABPanelTile] - Started HABPanel at /habpanel
2021-03-31 19:14:50.118 [INFO ] [.network.internal.utils.NetworkUtils] - CIDR prefix is smaller than /24 on interface with address 172.17.0.1/16, truncating to /24, some addresses might be lost
2021-03-31 19:14:53.881 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.

During the initial start-up the following bindings were installed:
Astro
DSCAlarm
Lutron
MQTT
Network
Zwave

  • Platform information:
    • Hardware: Synology RS12212+
    • OS: DSM 6.2.4-25556
    • Docker
    • Java Runtime Environment: Java 11
    • openHAB version: 3.0.1
2

Containers have their own internal private subnet, usually starting with 173. Unless you give the container permission, it can’t even see the host’s IP address.

When you use --net=host in the docker run command, you are letting the container see the host’s network in addition to the docker network

The docker network interface is the default so OH users that one. You can change that in Settings Network in MainUI

3

Thank you. Does it make any difference which one I use? My main concern is the Aeotec z-stick which always seem to be a challenge on Synology.