1,574
edits
Changes
Jump to navigation
Jump to search
Line 43:
Line 43: − + Line 77:
Line 77: + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
Signal-event reboot - the rpm now does systemctl enable wsdd
Signal-event reboot - the rpm now does systemctl enable wsdd
===Usage===
====Usage====
[root@sme10 ~]# config show wsdd
[root@sme10 ~]# config show wsdd
[[Category:Security]]
[[Category:Security]]
[[Category: Administration:Certificates]]
[[Category: Administration:Certificates]]
====Example Usage====
handle traffic on eth0 only, but only with IPv6 addresses
wsdd -i eth0 -6
or
wsdd --interface eth0 --ipv6only
===Known Issues===
====Security====
wsdd does not implement any security feature, e.g. by using TLS for the http service. This is because wsdd's intended usage is within private, i.e. home, LANs. The Hello message contains the hosts transport address, i.e. the IP address which speeds up discovery (avoids Resolve message).
In order to increase the security, use the capabilities of the init system or consider the -u and -c options.
====Using only IPv6 on FreeBSD====
If wsdd is running on FreeBSD using IPv6 only, the host running wsdd may not be reliably discovered. The reason appears to be that Windows is not always able to connect to the HTTP service for unknown reasons. As a workaround, run wsdd with IPv4 only.
====Usage with NATs====
Do not use wssd on interfaces that are affected by NAT. According to the standard, the ResolveMatch messages emitted by wsdd, contain the IP address ("transport address" in standard parlance) of the interface(s) the application has been bound to into. When such messages are retrieved by a client (Windows hosts, e.g.) they are unlikely to be able to connect to the provided address which has been subject to NAT. To avoid this issue, use the -i/--interface option to bind wsdd to interfaces not affected by NAT.
====Tunnel/Bridge Interface====
If tunnel/bridge interfaces like those created by OpenVPN or Docker exist, they may interfere with wsdd if executed without providing an interface that it should bind to (so it binds to all). In such cases, the wsdd hosts appears after wsdd has been started but it disappears when an update of the Network view in Windows Explorer is forced, either by refreshing the view or by a reboot of the Windows machine. To solve this issue, the interface that is connected to the network on which the host should be announced needs to be specified with the -i/--interface option. This prevents the usage of the tunnel/bridge interfaces.
Background: Tunnel/bridge interfaces may cause Resolve requests from Windows hosts to be delivered to wsdd multiple times,´i.e. duplicates of such request are created. If wsdd receives such a request first from a tunnel/bridge it uses the transport address (IP address) of that interface and sends the response via unicast. Further duplicates are not processed due to the duplicate message detection which is based on message UUIDs. The Windows host which receives the response appears to detect a mismatch between the transport address in the ResolveMatch message (which is the tunnel/bridge address) and the IP of the sending host/interface (LAN IP, e.g.). Subsequently, the wsdd host is ignored by Windows.