ListenActiveScanUnicast() Invalid argument: setsockopt in logs for SddpDiscoveryService

[yndtrud]

Platform information:

• openHAB version: 4.3.7 / 5.0.1
• Java Runtime Environment OH4x: zulu17.60.17-ca-jdk17.0.16-win_x64
• Java Runtime Environment OH5x: Temurin OpenJDK21U-jdk_x64_windows_hotspot_21.0.8_9
• Hardware: ASUSPN41/IntelPentiumSilverN6000@2100/8GB_DDR4-2666/256GB_SSD-WD-GREEN
• OS: Windows Server 2022 Std Latest

2025-08-29 13:53:34.179 [INFO ] [org.openhab.core.Activator          ] - Starting openHAB 5.0.1 (Release Build)
2025-08-29 13:53:34.558 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Etc/GMT-3'.
2025-08-29 13:53:34.558 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'en_US'.
2025-08-29 13:53:38.089 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'lab_network_en.items'
2025-08-29 13:53:38.662 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'network_home_v1.things'
2025-08-29 13:53:41.020 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2025-08-29 13:53:42.752 [WARN ] [.discovery.sddp.SddpDiscoveryService] - listenActiveScanUnicast() error 'Invalid argument: setsockopt'

[lolodomo]

Please enable this log
log:set DEBUG org.openhab.core.config.discovery.sddp.SddpDiscoveryService
This will add an interesting log just before the error.

[lolodomo]

I assume it is this line that triggers the exception:

openhab-core/bundles/org.openhab.core.config.discovery.sddp/src/main/java/org/openhab/core/config/discovery/sddp/SddpDiscoveryService.java

Line 282 in 478a7de

socket.setOption(StandardSocketOptions.IP_MULTICAST_IF, networkInterface);

[yndtrud]

log:set DEBUG org.openhab.core.config.discovery.sddp.SddpDiscoveryService

Log file:

openhab.zip

[yndtrud]

socket.setOption(StandardSocketOptions.IP_MULTICAST_IF

https://bugs.openjdk.org/browse/JDK-8272476

[lolodomo]

The concerned part:

2025-08-30 11:54:42.906 [DEBUG] [.discovery.sddp.SddpDiscoveryService] - listenActiveScanUnicast() starting on '192.168.13.90:50198' on interface 'Microsoft Hyper-V Network Adapter'
2025-08-30 11:54:42.906 [WARN ] [.discovery.sddp.SddpDiscoveryService] - listenActiveScanUnicast() error 'Invalid argument: setsockopt'

I am just asking myself if the problem is the interface itself. I am not familiar with that interface, is it fine to use it for Internet Protocol multicast datagrams ?

Here is the documentation of setOption:
https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/net/DatagramSocket.html#setOption(java.net.SocketOption,java.lang.Object)
The error that is logged is the result of the catching of IOException. Here is what says the doc for this exception: "if an I/O error occurs, or if the socket is closed."

[lolodomo]

socket.setOption(StandardSocketOptions.IP_MULTICAST_IF

https://bugs.openjdk.org/browse/JDK-8272476

I see your message after publishing my last message.
I did not read the full Java bug but apparently it is not a bug in openHAB if I correctly understand. And maybe your workaround would be to enable IP v6 on that interface ?

[yndtrud]

The concerned part:

2025-08-30 11:54:42.906 [DEBUG] [.discovery.sddp.SddpDiscoveryService] - listenActiveScanUnicast() starting on '192.168.13.90:50198' on interface 'Microsoft Hyper-V Network Adapter'
2025-08-30 11:54:42.906 [WARN ] [.discovery.sddp.SddpDiscoveryService] - listenActiveScanUnicast() error 'Invalid argument: setsockopt'

I am just asking myself if the problem is the interface itself. I am not familiar with that interface, is it fine to use it for Internet Protocol multicast datagrams ?

Here is the documentation of https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/net/DatagramSocket.html#setOption(java.net.SocketOption,java.lang.Object) The error that is logged is the result of the catching of IOException. Here is what says the doc for this exception: "if an I/O error occurs, or if the socket is closed."

Does not depend on the interface. In this case, it is a Microsoft Hyper-V virtual machine.
But the problem is also on the hardware. On any Windows with any hardware interface.

Does not depend on this options

Throws an exception (;og) if ip v6 is disabled on the interface (system)

Log with enabled ipv6 on network inteface (disabled/ebaled in OH - no effect)

ipv6.zip

[lolodomo]

Your very last log seems to be about your other problem with no USB, not the one with ListenActiveScanUnicast.

Unfortunately I will not be able to help more myself, all this stuff with socket and network configuration is a little over my own skills.

But we can ping @andrewfg as he created this code, maybe it will be clearer for him.

[andrewfg]

Two things..

1. Regarding the USB issue: This is a separate issue and there is a fix Fix USB discovery on Windows in case there is no USB port #4996 in process
2. Regarding the SDDP issue: This protocol runs via UDP multicast on IPv4 (only). I did not read your logs but it seems that you are seeing the errors related to IPv6? Is that correct? If so, the issue would not be solved by disabling IPv6 but rather by enabling IPv4 => did you try that?

[yndtrud]

Two things..

1. Regarding the USB issue: This is a separate issue and there is a fix Fix USB discovery on Windows in case there is no USB port #4996 in process
2. Regarding the SDDP issue: This protocol runs via UDP multicast on IPv4 (only). I did not read your logs but it seems that you are seeing the errors related to IPv6? Is that correct? If so, the issue would not be solved by disabling IPv6 but rather by enabling IPv4 => did you try that?

How to reproduce error in log:

[WARN ] [.discovery.sddp.SddpDiscoveryService] - listenActiveScanUnicast() error 'Invalid argument: setsockopt'

OS: Windows
OpehHAB Settings->Network Settings -> Use IP v6: off
Windows system Network Interface used as primary in OpenHAB: Intenet Protocol Version 6 (TCP/IP): off

You wrote: If so, the issue would not be solved by disabling IPv6. No, enabling IPv6 on the network interface (windows not openhab) will solve the problem.
What you mean: enabling IPv4 => did you try that?. IPv4 always enabled.

[andrewfg]

You wrote: If so, the issue would not be solved by disabling IPv6. No, enabling IPv6 on the network interface (windows not openhab) will solve the problem.

@yndtrud Sorry but I don't understand; can you please explain further?

[yndtrud]

You wrote: If so, the issue would not be solved by disabling IPv6. No, enabling IPv6 on the network interface (windows not openhab) will solve the problem.

@yndtrud Sorry but I don't understand; can you please explain further?

Of course I can!

If in the Windows operating system (I don't know about Linux) the network adapter (that is primary for the OpenHAB) has IPv6 protocol disabled in the adapter settings, then we get an error in the logs about Invalid argument: setsockopt'.

This command always fail if IPv6 protocol disabled on network adapter

// comand
socket.setOption(StandardSocketOptions.IP_MULTICAST_IF, networkInterface) 
// After this command, the code is not executed because the exception is handled and listenActiveScanUnicast exits.

// log
[WARN ] [.discovery.sddp.SddpDiscoveryService] - listenActiveScanUnicast() error 'Invalid argument: setsockopt'

My network adapter settings. No IPv6 as can see.

Ethernet adapter vEthernet (OpenHAB VM Wired Port):

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
   Physical Address. . . . . . . . . : D4-5D-64-EF-92-21
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.13.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.13.10
   DNS Servers . . . . . . . . . . . : 192.168.13.5
                                       192.168.13.10
   NetBIOS over Tcpip. . . . . . . . : Enabled

[andrewfg]

Hmm. It is very odd that DISabling IPv6 would cause an error on the SDDP protocol since that uses exclusively IPv4. However let me think about it. Do you confirm that there is no error when you ENable IPv6 ?

[yndtrud]

Hmm. It is very odd that DISabling IPv6 would cause an error on the SDDP protocol since that uses exclusively IPv4. However let me think about it. Do you confirm that there is no error when you ENable IPv6 ?

Yes.

P.S. Maybe this -> https://bugs.openjdk.org/browse/JDK-8272476