Doesn't respond without specifying "-4" and "-i" #15
Comments
|
Sorry for being unresponsive. Real life can be tough 😉. In general, it is a bad idea to let wsdd bind to all interfaces if one of them is affected by NAT. NAT breaks wsdd's functionality because the IP address of the host as seen by wsdd is contained in the emitted messages but the message content is (in almost all cases) not modified by the firewall/paket filter. Thus, you may have to bind to the real interface with the Concerning the IPv4/6 issue: The replies to the IPv6 probes appear to be missing. Otherwise you would observe the resolve message via IPv6 more often. Or the probe replies (ProbeMatch messages) are not received by the Windows host. You wrote that IPv6 is not really turned on. I'm not sure what that means on a QNAP device, but if it is really disabled than wsdd should not have detected an IPv6 address anyway. |
wsdd now uses the lower case version of the hostname for domains and (as before this commit) the upper case version for workgroup environments in its default behavior. The added -p option preserves the case information of the provided or detected hostname. closes christgau#16 see also christgau#15
|
This seems like two issues in one. I can speak to the "-4" portion. My network is ipv4 only and for some reason if I don't specify the -4, wsdd does not work correctly. When I refresh the network browser on my PC, I see the packets hit wsdd but the machine doesn't show up. If I start it with the '-4' flag, everything works fine. Environment: Ubuntu 19.10 Log of activity without the '-4' flag: 2020-01-12 22:44:11,814:wsdd WARNING(pid 1180): no interface given, using all interfaces |
|
Looks like the final and essential HTTP request is not performed. Based on the log, it should be done via IPv6, but since your network may not support it, you can into trouble. I had similar problems with FreeBSD and IPv6. Windows sporadically refused to do the HTTP request, although IT works fine in other situations. As stated in the readme, using IPv4 was a workaround.
When I refresh the network browser on my PC, I see the packets hit wsdd
Do you mean you can see network packets in tools like tcpdump or wireshark?
Do you see an attempt to establish a TCP connection, i.e. SYN packets coming to the machine wsdd is running on?
Please also ensure your Firewall allows IP 6 traffic for wsdd. If you do not have configured your network for IPv6 you should stick to IPv4 for wsdd as well as you already did.
|
Specifying both -i eth1 and -4 works fine,
just with a minor issue, the name and domain name are ALL CAPS.
NETBIOS is all ALL CAPS only, but WSD is not.
(log 4)
Following tests don't show the machine running wsdd, "Ubuntu", on a machine trying to see the first one, "Win10".
Without specifying "-4", (with or without -i eth1), "Probe" is received on IP6 (once on IP4), sometimes "Resolve" from IP6 follows on next line, (I didn't allow IP6 on eth1 adapter but the settings on QNAP seems dodgy on this anyway), no "POST" follows
(log 1)
Specifying "-4", but without specifying "-i eth1"
"Resolve" always follows "Probe", no "POST". Both Resolve and Probe reports IP address used by eth1, (192.168.8.103:65295(eth0)), while eth0 is on 10.0.5.239
(log 2)
Specifying -i eth0 will pass no "Probe" which is expected as NAT (to which eth0 is plugged) will not translate a broadcast,
but log in above case shows eth0
(log 3)
Before each "Probe" line in logs below, I issued a refresh on Win10 (File Explorer > Network > refresh button)
Only log section with both -4 and -i eth1 specified, showed Ubuntu on Win10's Network tab in File Explorer
The "Ubuntu" is LXC (chroot, ...) running on QNAP NAS (so-called Linux Station feature)
Ubuntu was assigned two network "cards". The NAS decided how to use them, but it works and I didn't bother to try changing it.
eth0, is "plugged-in" to Virtual Switch with NAT and DHCP servers, but has higher metric (should not be used as a gateway)
eth1 is connected to PHY - real Network Adapter
I didn't turn on IP6 on neither PHY, nor the Virtual Switch. It's a choice in the NAS Settings. I can turn it on for test if needed.
Win10 is Windows Pro 10 1809
log 1
log 2
log 3
log 4
more
The text was updated successfully, but these errors were encountered: