connected_if: Machine is not on the network.

[kroese]

When I create a bridge interface between a host (20.20.20.1) and a virtual machine (20.20.20.21), and listen with wsdd2 on that interface, it starts correctly:

starting.
ifname dockerbridge, ifindex 2
hostname 58581c09ba9a, netbios name 58581c09ba9a, workgroup WORKGROUP
wsdd-mcast-v4 udp port 3702 239.255.255.250 20.20.20.1 @ dockerbridge
wsdd-http-v4 tcp port 3702 - 20.20.20.1 @ dockerbridge
llmnr-mcast-v4 udp port 5355 224.0.0.252 20.20.20.1 @ dockerbridge
llmnr-tcp-v4 tcp port 5355 - 20.20.20.1 @ dockerbridge
netlink_recv: address addition/change/deletion detected.
restarting service.
ifname dockerbridge, ifindex 1927
hostname 58581c09ba9a, netbios name 58581c09ba9a, workgroup WORKGROUP
wsdd-mcast-v4 udp port 3702 239.255.255.250 20.20.20.1 @ dockerbridge
wsdd-http-v4 tcp port 3702 - 20.20.20.1 @ dockerbridge
llmnr-mcast-v4 udp port 5355 224.0.0.252 20.20.20.1 @ dockerbridge
llmnr-tcp-v4 tcp port 5355 - 20.20.20.1 @ dockerbridge

The when I try to discover the network inside the Windows VM I can see the incoming queries in the wsdd2 log:

llmnr: connected_if: 20.20.20.21: Machine is not on the network
wsd_recv: wsd_recv_action: connected_if: Machine is not on the network
wsd_recv: wsd_recv_action: connected_if: Machine is not on the network
wsd_recv: wsd_recv_action: connected_if: Machine is not on the network
wsd_recv: wsd_recv_action: connected_if: Machine is not on the network
wsd_recv: wsd_recv_action: connected_if: Machine is not on the network
wsd_recv: wsd_recv_action: connected_if: Machine is not on the network

But wsdd2 fails to send a reply back, everytime it reports Machine is not on the network.

What can be the cause of this? Clearly it is getting the request packets so why cannot send the reply back?

When using wsdd (the Python version of this tool) it works without any problem. So it seems like this a bug in wsdd2.