wsdd: wsdd 0.6.3 no longer functional on FreeBSD

FreeBSD port maintainers recently upgraded from 0.6.2 to 0.6.3 and PR 252742 and now the daemon no longer functions (meaning: Network Neighbourhood no longer shows the machine where wsdd is running).

It will take me some time to figure out why (I’ll end up using git bisect to figure out what commit broke things), and I probably won’t have time to do the analysis until this weekend.

I at least wanted to report it first.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 18 (8 by maintainers)

Commits related to this issue

fix(src): Use dedicated sockets for sending to multicast and unicast. Fixes #80 — committed to christgau/wsdd by christgau 3 years ago

Most upvoted comments

@christgau resolved this error with timeout of 5.0 seconds. Thanks.

Izorkin on Jan 27, 2021

@Izorkin based on the log, you are using wsdd now in the discovery mode (client) while the original error was related to the normal (host) operation mode. So this is completely unrelated. In addition, the timeout is not really a fault of wsdd and it is not an error per se. Two possibilities:

The other side (the wsd host in that case) does not respond quick enough
Your firewall setup prevents establishing a connection to the other side, maybe because the OUTPUT chain is too restrictive.

For the first point, you might check if the default timeout of 2.0 seconds could be increased and a higher values resolves the issue: https://github.com/christgau/wsdd/blob/ee8783ce71a408a3d9923b5d67659f7ce2712166/src/wsdd.py#L672

If this really turns out to be a problem, please open a new issue or a PR, if you have a patch.

For the second point, please check your firewall rules, but a discussion of the ruleset might be out of scope… at least for this issue.

christgau on Jan 27, 2021