Sonos connection to devices lost after some time after adding docker container(s) to the server

Hi all,

since a couple of weeks I experience problems with my sonos system. I do not know if the problems are related with a recent sonos software update - or with my setup.

I use Ubuntu 22.04.2 LTS x86_64 (5.15.0-67-generic) as server operating system with the following java runtime:

openjdk 11.0.10 2021-01-19 LTS
OpenJDK Runtime Environment Zulu11.45+27-CA (build 11.0.10+9-LTS)
OpenJDK 64-Bit Server VM Zulu11.45+27-CA (build 11.0.10+9-LTS, mixed mode)

OpenHAB was installed from the official repository and is up-to-date: Version 3.4.2 (Build)

After a restart the sonos devices are detected and remain online for a couple of hours. But after some time all my sonos devices report offline.

2023-03-14 17:42:37.692 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Sonos player RINCON_347E5C37646001400 is not available in local network
2023-03-14 17:43:37.704 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Sonos player RINCON_347E5C37646001400 has been found in local network

Devices use the following software version:

2023-03-14 18:10:07.751 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'SoftwareVersion':'71.1-38240' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C37659001400'
2023-03-14 18:10:07.752 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'DisplaySoftwareVersion':'15.1.1' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C37659001400'

It is strange that after a new start with cache clean only some of the players loose connection; but connect again after some time - but after aprox. half a day all devices report offline.

I’m collecting trace logs now to potentially create a bugreport - but would know if there are ideas what else could be the problem or what info I should collect to help with trouble shooting (the trace logs will be quite big - so if I can things narrow down that would help). I can also install wireshark to monitor the network traffic if this is helpful - but I would need to know what filters make sense to get useful information.

The sonos native apps do not have problems to see the devices and do not report any problems.

Thanks for any advice :-).

with kind regards,
Patrik


Update - After 3 Hours all Sonos devices remain offline:

This is where the last time I saw kind of communication:

2023-03-14 18:35:01.826 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Sonos player RINCON_347E5C3E35B401400 is not available in local network
2023-03-14 18:35:10.992 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Sonos player RINCON_7828CA76219E01400 is not available in local network
2023-03-14 18:35:11.822 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Sonos player RINCON_48A6B824D4D801400 is not available in local network
2023-03-14 18:35:12.030 [DEBUG] [s.internal.handler.ZonePlayerHandler] - RINCON_347E5C37646001400: Subscription to service ZoneGroupTopology failed
2023-03-14 18:35:21.002 [DEBUG] [s.internal.handler.ZonePlayerHandler] - RINCON_347E5C3E379601400: Subscription to service RenderingControl failed
2023-03-14 18:35:21.003 [DEBUG] [s.internal.handler.ZonePlayerHandler] - RINCON_347E5C37646001400: Subscription to service RenderingControl failed
2023-03-14 18:35:31.000 [DEBUG] [s.internal.handler.ZonePlayerHandler] - RINCON_347E5C37646001400: Subscription to service DeviceProperties failed
2023-03-14 18:35:41.011 [DEBUG] [s.internal.handler.ZonePlayerHandler] - RINCON_7828CAD279FE01400: Subscription to service GroupManagement failed
2023-03-14 18:35:41.028 [DEBUG] [s.internal.handler.ZonePlayerHandler] - RINCON_7828CAD279FE01400: Subscription to service RenderingControl failed
2023-03-14 18:35:41.032 [DEBUG] [s.internal.handler.ZonePlayerHandler] - RINCON_347E5C37646001400: Subscription to service ContentDirectory failed
2023-03-14 18:35:47.757 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'ChannelFreq':'2462' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.758 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'Configuration':'1' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.758 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'EthLink':'true' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.758 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'HTBondedZoneCommitState':'0' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.758 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'ZoneName':'Büro' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'ChannelMapSet':'RINCON_347E5C37659001400:LF,LF;RINCON_347E5C3E379601400:RF,RF' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'SecureRegState':'3' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'BehindWifiExtender':'0' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'Invisible':'true' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'AirPlayEnabled':'false' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'RoomCalibrationState':'4' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'WirelessMode':'0' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'Orientation':'0' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'WirelessLeafOnly':'false' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'IsZoneBridge':'false' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'SupportsAudioClip':'true' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.759 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'SettingsReplicationState':'RINCON_347E5C37646001400,126,RINCON_FFFFFFFFFFFF99999,0,RINCON_347E5C37646001400,0,RINCON_347E5C37646001400,0,RINCON_347E5C3E35B401400,3702,RINCON_347E5CFEB09E01400,9,RINCON_347E5C37646001400,1018,RINCON_FFFFFFFFFFFF99999,0,RINCON_347E5C37646001400,8,RINCON_347E5C3E379601400,0,RINCON_7828CAD2861A01400,231,RINCON_7828CAD2861A01400,2821,RINCON_347E5C3E35B401400,6,RINCON_7828CAD2861A01400,21,RINCON_347E5C37646001400,0,RINCON_7828CAD2861A01400,132,RINCON_48A6B8EEAF2C01400,1447' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.760 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'WifiEnabled':'true' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.760 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'SupportsAudioIn':'false' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.760 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'IsIdle':'true' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.760 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'LastChangedPlayState':'PLAYING,UNPLAYABLE,MEMBER,' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:47.760 [TRACE] [s.internal.handler.ZonePlayerHandler] - Received pair 'Icon':'x-rincon-roomicon:office' (service 'DeviceProperties') for thing 'sonos:SYMFONISK:RINCON_347E5C3E379601400'
2023-03-14 18:35:48.760 [DEBUG] [s.internal.handler.ZonePlayerHandler] - RINCON_7828CAD279FE01400: Subscription to service ContentDirectory failed
2023-03-14 18:35:51.202 [DEBUG] [overy.ZonePlayerDiscoveryParticipant] - Discovered a Sonos 'sonos:SYMFONISK' thing with UDN 'RINCON_347E5C37646001400'
2023-03-14 18:35:51.202 [INFO ] [s.internal.handler.ZonePlayerHandler] - UPnP device RINCON_347E5C37646001400 is absent (thing sonos:SYMFONISK:RINCON_347E5C37646001400)
2023-03-14 18:35:51.819 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:35:51.825 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:35:59.009 [INFO ] [s.internal.handler.ZonePlayerHandler] - UPnP device RINCON_347E5CFEAE0A01400 is present (thing sonos:SYMFONISK:RINCON_347E5CFEAE0A01400)
2023-03-14 18:35:59.009 [DEBUG] [overy.ZonePlayerDiscoveryParticipant] - Discovered a Sonos 'sonos:SYMFONISK' thing with UDN 'RINCON_347E5CFEAE0A01400'
2023-03-14 18:35:59.537 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:35:59.874 [DEBUG] [overy.ZonePlayerDiscoveryParticipant] - Created a DiscoveryResult for device '192.168.0.95 - SYMFONISK Bookshelf' with UDN 'RINCON_347E5CFEAE0A01400'
2023-03-14 18:36:00.991 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:36:01.821 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:36:01.828 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:36:09.541 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Sonos player RINCON_347E5CFEAE0A01400 is not available in local network
2023-03-14 18:36:09.542 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:36:10.993 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Sonos player RINCON_7828CAD279FE01400 is not available in local network
2023-03-14 18:36:11.825 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:36:11.831 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:36:11.890 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:36:20.970 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:36:20.971 [DEBUG] [s.internal.handler.ZonePlayerHandler] - UPnP device RINCON_347E5C37646001400 not yet registered
2023-03-14 18:36:21.826 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Sonos player RINCON_347E5C3E379601400 is not available in local network
2023-03-14 18:37:01.821 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:01.828 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:11.354 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:11.825 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:11.831 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:19.544 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:20.972 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:20.972 [DEBUG] [s.internal.handler.ZonePlayerHandler] - UPnP device RINCON_347E5C37646001400 not yet registered
2023-03-14 18:37:21.828 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:21.834 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:37:21.893 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:11.826 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:11.831 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:20.973 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:20.973 [DEBUG] [s.internal.handler.ZonePlayerHandler] - UPnP device RINCON_347E5C37646001400 not yet registered
2023-03-14 18:38:21.355 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:21.827 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:21.833 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:29.549 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:31.832 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:31.838 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:38:31.896 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:39:20.974 [DEBUG] [s.internal.handler.ZonePlayerHandler] - Polling job
2023-03-14 18:39:20.975 [DEBUG] [s.internal.handler.ZonePlayerHandler] - UPnP device RINCON_347E5C37646001400 not yet registered

After this the binding is polling and somehow recognizes the player - but claims that they are not registered … (loglevel ist set to trace, but after the last “real” communication only those debug messages repeat that the player is not registered).

I did some more investigation on this - and the problem is related to my setup, as a downgrade of OH3 to a previous version did not resolve the problems.

However - I recently started to use docker containers to host additional services on my OH3 server (OH is not running in docker, but on the host os itself). Which changed the network configuration of the server significantly:

Most likely I face the same as reported in Isse #13077: [sonos] Multiple docker networks interfere with binding · Issue #13077 · openhab/openhab-addons · GitHub

I’ll try to learn more about network communication and upnp to see if this is something that should be handled by local configuration - or the binding itself. Any advice is appreciated of course :slight_smile: .

with kind regards,
Patrik

I gave an answer here: [sonos] Multiple docker networks interfere with binding · Issue #13077 · openhab/openhab-addons · GitHub

1 Like

Thanks! :slight_smile: - with the proposed workarraound it is working stable now; I’ve updated the issue with the information. I think this should be treated as a bug - or at least be mentioned in the binding docu. Let’s see if people that are deeper involved in docker, and/or sonos binding code have an opinion on this.

(changed title of the discussion to better reflect the topic/issue)

Unfortunately after upgrade of my docker stack to OH 4.0.4 SONOS stopped working again - I did some investigation and updated the issue accordingly. Here the same information for reference:

Relevant code in jupnp transport

// An implementation can honor these if it wants (the default does)
public static final String SYSTEM_PROPERTY_NET_IFACES = "org.jupnp.network.useInterfaces";
public static final String SYSTEM_PROPERTY_NET_ADDRESSES = "org.jupnp.network.useAddresses";

Relevant Karaf configuration:

Pid:            org.jupnp
BundleLocation: ?
Properties:
   asyncThreadPoolSize = 30
   felix.fileinstall.filename = file:/openhab/userdata/etc/org.jupnp.cfg
   multicastResponsePort = 0
   service.pid = org.jupnp
   threadPoolSize = 15
openhab> config:edit --type json --force org.jupnp
openhab> config:property-list
   asyncThreadPoolSize = 30
   multicastResponsePort = 0
   threadPoolSize = 15
openhab> config:property-append org.jupnp.network.useInterfaces "eno1"
openhab> config:property-append org.jupnp.network.useAddresses "192.168.0.65"
openhab> config:update
openhab> config:property-list --pid org.jupnp                                                                                                                                                          
   asyncThreadPoolSize = 30
   multicastResponsePort = 0
   org.jupnp.network.useAddresses = 192.168.0.65
   org.jupnp.network.useInterfaces = eno1
   threadPoolSize = 15

:arrow_right: Expected trace message

log.trace("Skipping unwanted network interface (-D {} ): {}", SYSTEM_PROPERTY_NET_IFACES, iface.getName());

Actual result:

userdata/logs/upnp.log:
  100: 2023-11-16 08:45:53.780 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Discovered usable network interface address: 172.22.0.1
  104: 2023-11-16 08:45:53.780 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Discovered usable network interface address: 172.21.0.1
  108: 2023-11-16 08:45:53.781 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Discovered usable network interface address: 172.19.0.1
  112: 2023-11-16 08:45:53.782 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Discovered usable network interface address: 172.20.0.1
  116: 2023-11-16 08:45:53.782 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Discovered usable network interface address: 192.168.6.98
  120: 2023-11-16 08:45:53.783 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Discovered usable network interface address: 192.168.0.65

Update
It seems that SONOS indeed uses a different factory:

Update:

I’ve checked a wrong version of the binding source code (embarrassing) :frowning: … the current binding properly uses the core infrastructure. Below the info I added to the git issue (a config that seems to work for me):


I did some more digging and in theory the solution @lolodomo referenced should work - but maybe I did a mistake in the syntax of the compose file … anyhow - I have now a working configuration in case @arins would like to x-check if this also works for you.

The SONOS binding is properly integrated with the current OH core upnp infrastructure - but the scope of the properties make the difference. I do not know why the EXTRA_JAVA_OPTS=-Dorg.jupnp.network.useInterfaces="eno1" did not work (I suspect that the networks must be listed without the "…). But I will not follow up on this atm (time budget used and the system seems to work …).

What I did is to set the interface in `userdata/etc/system.properties’:

org.jupnp.network.useInterfaces=eno1

Until now the communication looks stable and the logs do make sense:

userdata/logs/upnp.log:
   5: 2023-11-17 18:37:37.109 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth84ef8a1
   8: 2023-11-17 18:37:37.110 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth0496b9d
  11: 2023-11-17 18:37:37.110 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth99a640a
  14: 2023-11-17 18:37:37.111 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth422e0b5
  17: 2023-11-17 18:37:37.111 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth1ff1007
  20: 2023-11-17 18:37:37.112 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth1528ef9
  23: 2023-11-17 18:37:37.112 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth0ea4cf2
  26: 2023-11-17 18:37:37.113 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth24b2901
  29: 2023-11-17 18:37:37.114 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): vethd0f5998
  32: 2023-11-17 18:37:37.115 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth93bf6ff
  35: 2023-11-17 18:37:37.115 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth21f0d06
  38: 2023-11-17 18:37:37.116 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): veth3b67029
  41: 2023-11-17 18:37:37.117 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): br-d19ae4339d2f
  44: 2023-11-17 18:37:37.119 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): br-8db4ae73724f
  47: 2023-11-17 18:37:37.119 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): br-b8da1ab4b871
  56: 2023-11-17 18:37:37.121 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): docker_gwbridge
  59: 2023-11-17 18:37:37.122 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Skipping unwanted network interface (-D org.jupnp.network.useInterfaces ): eno1.4

2023-11-17 18:37:37.129 [TRACE] [sport.impl.NetworkAddressFactoryImpl] - Discovered usable network interface address: 192.168.0.65
2023-11-17 18:37:37.131 [DEBUG] [org.jupnp.transport.Router          ] - Init multicast receiver on interface: eno1
2023-11-17 18:37:37.133 [DEBUG] [org.jupnp.transport.Router          ] - Starting multicast receiver on interface: eno1
2023-11-17 18:37:37.143 [DEBUG] [org.jupnp.transport.Router          ] - Init stream server on address: /192.168.0.65
2023-11-17 18:37:37.144 [DEBUG] [ansport.impl.ServletStreamServerImpl] - Setting executor service on servlet container adapter
2023-11-17 18:37:37.144 [DEBUG] [ansport.impl.ServletStreamServerImpl] - Adding connector: /192.168.0.65:-1
2023-11-17 18:37:37.148 [INFO ] [i.HttpServiceServletContainerAdapter] - Registering UPnP callback servlet as /upnpcallback
2023-11-17 18:37:37.158 [DEBUG] [org.jupnp.transport.Router          ] - Init datagram I/O on address: /192.168.0.65

If someone else can confirm that this works we can update the documentation for the docker use case (as this also affects other bindings probably the README of the docker image itself will be the right place).

It is also the question if the EXTRA_JAVA_OPTS would be the better approach (but I’ll stay with the config file for the moment) - but if someone can confirm the other approach we might add both options to the docu with including the info that the parameter must not use "

with kind regards,
Patrik

1 Like