wsdd icon indicating copy to clipboard operation
wsdd copied to clipboard

Doesn't respond without specifying "-4" and "-i"

Open paponius opened this issue 6 years ago • 3 comments

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

no -i no -4

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -n huhu -v -s -w WORKGROUP WARNING: no interface given, using all interfaces INFO: using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e INFO: joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 INFO: joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 INFO: joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 INFO: joined multicast group ('ff02::c', 3702, 22364, 160) on fe80::83e:e1e9:d627:a983%eth0 INFO: fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:123c3105-12d8-4ab4-89da-6a704d8961a7 UDP" - - INFO: fe80::5d27:ee50:5c54:3db%eth1:65296(eth1) - - "Resolve urn:uuid:120f9043-ac05-4e6a-aeca-fac8d58bb093 UDP" - -

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -n huhu -v -s -w WORKGROUP [sudo] password for admin: WARNING: no interface given, using all interfaces INFO: using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e INFO: joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 INFO: joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 INFO: joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 INFO: joined multicast group ('ff02::c', 3702, 22364, 160) on fe80::83e:e1e9:d627:a983%eth0 INFO: fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:9359d205-eea7-42d9-b084-97937d0f9cfa UDP" - -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -v 2019-06-10 02:20:59,795:wsdd WARNING(pid 17695): no interface given, using all interfaces 2019-06-10 02:20:59,795:wsdd INFO(pid 17695): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:20:59,808:wsdd INFO(pid 17695): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:20:59,874:wsdd INFO(pid 17695): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 2019-06-10 02:20:59,943:wsdd INFO(pid 17695): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 02:20:59,947:wsdd INFO(pid 17695): joined multicast group ('ff02::c', 3702, 22364, 160) on fe80::83e:e1e9:d627:a983%eth0 2019-06-10 02:21:10,621:wsdd INFO(pid 17695): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:feaa365e-71cb-4876-9638-ef78aefea373 UDP" - -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -v 2019-06-10 03:22:32,962:wsdd WARNING(pid 23565): no interface given, using all interfaces 2019-06-10 03:22:32,963:wsdd INFO(pid 23565): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 03:22:32,977:wsdd INFO(pid 23565): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 03:22:33,061:wsdd INFO(pid 23565): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 2019-06-10 03:22:33,111:wsdd INFO(pid 23565): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 03:22:33,115:wsdd INFO(pid 23565): joined multicast group ('ff02::c', 3702, 22364, 160) on fe80::83e:e1e9:d627:a983%eth0 2019-06-10 03:22:40,026:wsdd INFO(pid 23565): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:e1a29ed7-6346-442e-a213-414c806c3528 UDP" - - 2019-06-10 03:23:04,700:wsdd INFO(pid 23565): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:e7f03eac-953a-4203-be34-596739f595d9 UDP" - -

-i eth1

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -i eth1 -n huhu -v -w WORKGROUP 2019-06-10 01:56:29,087:wsdd INFO(pid 15289): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 01:56:29,099:wsdd INFO(pid 15289): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 01:56:29,180:wsdd INFO(pid 15289): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 01:56:44,450:wsdd INFO(pid 15289): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:ea5430dc-8f81-4375-9a6f-372a74a55355 UDP" - -

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -i eth1 -v 2019-06-10 02:16:45,590:wsdd INFO(pid 17268): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:16:45,602:wsdd INFO(pid 17268): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:16:45,682:wsdd INFO(pid 17268): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 02:16:49,373:wsdd INFO(pid 17268): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:5e488cbe-5324-4273-b268-a06601bd830c UDP" - - 2019-06-10 02:17:00,176:wsdd INFO(pid 17268): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:fa2e1279-60fb-464f-ab47-c84ad6e6937d UDP" - -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth1 -v 2019-06-10 03:01:36,405:wsdd INFO(pid 21587): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 03:01:36,470:wsdd INFO(pid 21587): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 03:01:46,574:wsdd INFO(pid 21587): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 03:01:46,579:wsdd INFO(pid 21587): 192.168.8.103:53385(eth1) - - "Probe urn:uuid:1dc6b942-c9c3-4e3d-9d0e-8c7454d12adf UDP" - - 2019-06-10 03:01:46,640:wsdd INFO(pid 21587): fe80::5d27:ee50:5c54:3db%eth1:65296(eth1) - - "Resolve urn:uuid:8997a8fd-451c-496c-b2c3-dba07eba7145 UDP" - -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth1 -v 2019-06-10 03:14:43,779:wsdd INFO(pid 22823): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 03:14:43,792:wsdd INFO(pid 22823): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 03:14:43,926:wsdd INFO(pid 22823): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 03:14:55,296:wsdd INFO(pid 22823): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:3b53c12f-eb3d-49aa-ac0d-270abf9d659c UDP" - - 2019-06-10 03:15:29,065:wsdd INFO(pid 22823): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:1350dc38-d2bd-48ae-975a-b697c80938e2 UDP" - - 2019-06-10 03:16:28,492:wsdd INFO(pid 22823): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:b0137695-cdc4-4783-93fa-d6c4ecc3f44a UDP" - -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth1 -v 2019-06-10 03:16:58,829:wsdd INFO(pid 23039): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 03:16:58,849:wsdd INFO(pid 23039): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 03:16:58,896:wsdd INFO(pid 23039): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 03:17:02,980:wsdd INFO(pid 23039): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:1ffcf024-97c0-402a-b624-5b24a8f40f4b UDP" - -

log 2

-4

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -4 -v -w WORKGROUP 2019-06-10 02:10:40,599:wsdd WARNING(pid 16637): no interface given, using all interfaces 2019-06-10 02:10:40,600:wsdd INFO(pid 16637): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:10:40,614:wsdd INFO(pid 16637): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:10:40,696:wsdd INFO(pid 16637): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 2019-06-10 02:11:01,225:wsdd INFO(pid 16637): 192.168.8.103:53385(eth0) - - "Probe urn:uuid:e3313fa9-48a2-4f93-bf3d-47456493815b UDP" - - 2019-06-10 02:11:02,609:wsdd INFO(pid 16637): 192.168.8.103:65295(eth0) - - "Resolve urn:uuid:c40c4b6b-7800-402e-b8d9-aeb6bfcb668e UDP" - - 2019-06-10 02:11:38,748:wsdd INFO(pid 16637): 192.168.8.103:53385(eth0) - - "Probe urn:uuid:946871aa-e14b-4eee-aef3-8399fc4bbf40 UDP" - - 2019-06-10 02:11:41,275:wsdd INFO(pid 16637): 192.168.8.103:65295(eth0) - - "Resolve urn:uuid:caad32b7-aadb-4816-89f1-a563cbb643a1 UDP" - -

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -n Huhu -4 -v -w WORKGROUP 2019-06-10 02:13:17,009:wsdd WARNING(pid 16894): no interface given, using all interfaces 2019-06-10 02:13:17,010:wsdd INFO(pid 16894): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:13:17,026:wsdd INFO(pid 16894): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:13:17,094:wsdd INFO(pid 16894): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 2019-06-10 02:13:20,665:wsdd INFO(pid 16894): 192.168.8.103:53385(eth0) - - "Probe urn:uuid:3b87cab4-f803-4caf-a94e-6b16996ae9e2 UDP" - - 2019-06-10 02:13:21,856:wsdd INFO(pid 16894): 192.168.8.103:65295(eth0) - - "Resolve urn:uuid:b7183da1-74ba-40c0-af25-4e4ff4a97212 UDP" - -

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -4 -v 2019-06-10 02:17:17,127:wsdd WARNING(pid 17328): no interface given, using all interfaces 2019-06-10 02:17:17,128:wsdd INFO(pid 17328): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:17:17,140:wsdd INFO(pid 17328): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:17:17,217:wsdd INFO(pid 17328): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 2019-06-10 02:17:22,539:wsdd INFO(pid 17328): 192.168.8.103:53385(eth0) - - "Probe urn:uuid:a55bb073-d9c4-4256-8eff-83795a0e16e3 UDP" - - 2019-06-10 02:17:25,524:wsdd INFO(pid 17328): 192.168.8.103:65295(eth0) - - "Resolve urn:uuid:cb241500-da80-4e78-9587-a86a0735d306 UDP" - -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -4 -v 2019-06-10 03:08:50,298:wsdd WARNING(pid 22265): no interface given, using all interfaces 2019-06-10 03:08:50,299:wsdd INFO(pid 22265): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 03:08:50,311:wsdd INFO(pid 22265): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 03:08:50,352:wsdd INFO(pid 22265): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 2019-06-10 03:08:58,761:wsdd INFO(pid 22265): 192.168.8.103:53385(eth0) - - "Probe urn:uuid:49a8c5c0-d99e-4f89-9fce-4b29388f8b78 UDP" - - 2019-06-10 03:08:59,244:wsdd INFO(pid 22265): 192.168.8.103:65295(eth0) - - "Resolve urn:uuid:2771ac45-d3ec-4456-a120-68efcbef283c UDP" - -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -4 -v 2019-06-10 03:20:50,225:wsdd WARNING(pid 23404): no interface given, using all interfaces 2019-06-10 03:20:50,226:wsdd INFO(pid 23404): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 03:20:50,243:wsdd INFO(pid 23404): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 03:20:50,376:wsdd INFO(pid 23404): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 2019-06-10 03:20:59,799:wsdd INFO(pid 23404): 192.168.8.103:53385(eth0) - - "Probe urn:uuid:3ca0e68a-55e5-4ca0-b05d-367ad1680fc5 UDP" - - 2019-06-10 03:21:01,345:wsdd INFO(pid 23404): 192.168.8.103:65295(eth0) - - "Resolve urn:uuid:de1f91d1-fdd4-4cf2-81bf-e84ca7f12eeb UDP" - - 2019-06-10 03:21:02,425:wsdd INFO(pid 23404): 192.168.8.103:65295(eth0) - - "Resolve urn:uuid:b7d08dea-1d27-4afe-8859-d64dd5db098e UDP" - - (refresh again) 2019-06-10 03:21:34,300:wsdd INFO(pid 23404): 192.168.8.103:53385(eth0) - - "Probe urn:uuid:5c84c3cf-f5c7-4107-85bf-6dfef899f863 UDP" - - 2019-06-10 03:21:35,550:wsdd INFO(pid 23404): 192.168.8.103:65295(eth0) - - "Resolve urn:uuid:54085f36-1865-4fbe-938b-290708e26833 UDP" - -

log 3

-i eth0

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth0 -v 2019-06-10 04:33:58,274:wsdd INFO(pid 1197): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 04:33:58,291:wsdd INFO(pid 1197): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0 2019-06-10 04:33:58,334:wsdd INFO(pid 1197): joined multicast group ('ff02::c', 3702, 22364, 160) on fe80::83e:e1e9:d627:a983%eth0

-i eth0 and -6

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth0 -6 -v 2019-06-10 04:15:32,981:wsdd INFO(pid 31584): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 04:15:32,995:wsdd INFO(pid 31584): joined multicast group ('ff02::c', 3702, 22364, 160) on fe80::83e:e1e9:d627:a983%eth0

-i eth0 and -4

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth0 -4 -v 2019-06-10 04:18:33,437:wsdd INFO(pid 31889): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 04:18:33,449:wsdd INFO(pid 31889): joined multicast group ('239.255.255.250', 3702) on 10.0.5.239%eth0

log 4

-i eth1 and -4

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -i eth1 -n huhu -4 -v -w WORKGROUP 2019-06-10 01:57:40,986:wsdd INFO(pid 15403): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 01:57:41,000:wsdd INFO(pid 15403): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 01:57:48,480:wsdd INFO(pid 15403): 192.168.8.103:53385(eth1) - - "Probe urn:uuid:6205e1b7-19d6-4533-852d-7b6c733437a8 UDP" - - 2019-06-10 01:57:48,537:wsdd INFO(pid 15403): 192.168.8.103:65295(eth1) - - "Resolve urn:uuid:da022ce2-c84d-4757-be97-af892d4eb7f0 UDP" - - 2019-06-10 01:57:48,552:wsdd INFO(pid 15403): 192.168.8.103 - - "POST /2cb964ad-e5d4-558a-a30d-f4952aef207e HTTP/1.1" 200 -

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -i eth1 -n Huhu -4 -v -w WORKGROUP 2019-06-10 02:14:13,113:wsdd INFO(pid 16997): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:14:13,125:wsdd INFO(pid 16997): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:14:17,873:wsdd INFO(pid 16997): 192.168.8.103:53385(eth1) - - "Probe urn:uuid:b68421f9-1076-40d2-816f-213ff0bcd04a UDP" - - 2019-06-10 02:14:19,031:wsdd INFO(pid 16997): 192.168.8.103:65295(eth1) - - "Resolve urn:uuid:2f006081-8a1f-433b-9436-f846e58358a1 UDP" - - 2019-06-10 02:14:19,063:wsdd INFO(pid 16997): 192.168.8.103 - - "POST /2cb964ad-e5d4-558a-a30d-f4952aef207e HTTP/1.1" 200 -

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -i eth1 -4 -v -w WORKGROUP 2019-06-10 02:15:39,727:wsdd INFO(pid 17156): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:15:39,739:wsdd INFO(pid 17156): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:15:46,790:wsdd INFO(pid 17156): 192.168.8.103:53385(eth1) - - "Probe urn:uuid:bc09f2bf-ddf6-4050-808e-cb988f4e03bc UDP" - - 2019-06-10 02:15:49,393:wsdd INFO(pid 17156): 192.168.8.103:65295(eth1) - - "Resolve urn:uuid:f3e40ada-c393-446b-89c3-a780f177c244 UDP" - - 2019-06-10 02:15:49,404:wsdd INFO(pid 17156): 192.168.8.103 - - "POST /2cb964ad-e5d4-558a-a30d-f4952aef207e HTTP/1.1" 200 -

admin@ubuntu_1804:/etc/systemd$ sudo /usr/bin/wsdd -i eth1 -4 -v 2019-06-10 02:16:25,350:wsdd INFO(pid 17218): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:16:25,363:wsdd INFO(pid 17218): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:16:29,536:wsdd INFO(pid 17218): 192.168.8.103:53385(eth1) - - "Probe urn:uuid:d5d44030-2f82-439f-9212-565f3bca47ec UDP" - - 2019-06-10 02:16:31,914:wsdd INFO(pid 17218): 192.168.8.103:65295(eth1) - - "Resolve urn:uuid:26b936da-dde0-4bf5-a6eb-b2b51bca45f0 UDP" - - 2019-06-10 02:16:31,925:wsdd INFO(pid 17218): 192.168.8.103 - - "POST /2cb964ad-e5d4-558a-a30d-f4952aef207e HTTP/1.1" 200 -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth1 -4 -v 2019-06-10 02:19:21,575:wsdd INFO(pid 17528): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:19:21,589:wsdd INFO(pid 17528): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 02:19:27,198:wsdd INFO(pid 17528): 192.168.8.103:53385(eth1) - - "Probe urn:uuid:005a76cd-dd0c-455c-a82b-9ef7fcc0b001 UDP" - - 2019-06-10 02:19:27,876:wsdd INFO(pid 17528): 192.168.8.103:65295(eth1) - - "Resolve urn:uuid:78e9e7ea-4462-461f-addf-bcb927a55716 UDP" - - 2019-06-10 02:19:27,887:wsdd INFO(pid 17528): 192.168.8.103 - - "POST /2cb964ad-e5d4-558a-a30d-f4952aef207e HTTP/1.1" 200 -

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth1 -4 -v 2019-06-10 03:16:43,448:wsdd INFO(pid 23025): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 03:16:43,461:wsdd INFO(pid 23025): joined multicast group ('239.255.255.250', 3702) on 192.168.8.104%eth1 2019-06-10 03:16:47,154:wsdd INFO(pid 23025): 192.168.8.103:53385(eth1) - - "Probe urn:uuid:a88cf1b9-0bd2-483b-8b9b-634020d3ddfc UDP" - - 2019-06-10 03:16:47,534:wsdd INFO(pid 23025): 192.168.8.103:65295(eth1) - - "Resolve urn:uuid:871db107-b238-474d-8e54-e4891b0f628b UDP" - - 2019-06-10 03:16:47,546:wsdd INFO(pid 23025): 192.168.8.103 - - "POST /2cb964ad-e5d4-558a-a30d-f4952aef207e HTTP/1.1" 200 -

more

-i eth1 and -6

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -i eth1 -6 -v 2019-06-10 02:25:15,890:wsdd INFO(pid 18109): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 02:25:15,902:wsdd INFO(pid 18109): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 02:25:26,555:wsdd INFO(pid 18109): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:145fa8cf-d50e-46b7-a5b4-2a27a9dab3b6 UDP" - -

-6

admin@ubuntu_1804:/etc/systemd$ /usr/bin/wsdd -6 -v 2019-06-10 03:08:08,818:wsdd WARNING(pid 22204): no interface given, using all interfaces 2019-06-10 03:08:08,830:wsdd INFO(pid 22204): using pre-defined UUID 2cb964ad-e5d4-558a-a30d-f4952aef207e 2019-06-10 03:08:08,866:wsdd INFO(pid 22204): joined multicast group ('ff02::c', 3702, 22364, 158) on fe80::7b6b:82a0:1475:6160%eth1 2019-06-10 03:08:08,895:wsdd INFO(pid 22204): joined multicast group ('ff02::c', 3702, 22364, 160) on fe80::83e:e1e9:d627:a983%eth0 2019-06-10 03:08:26,442:wsdd INFO(pid 22204): fe80::5d27:ee50:5c54:3db%eth1:53386(eth1) - - "Probe urn:uuid:ded1c713-3fae-4818-93f5-a401937a4571 UDP" - -

paponius avatar Jun 10 '19 02:06 paponius

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 -i option as you already did. This applies especially to environments where the traffic of the NAT'ed interface actually goes to the same physical network as the real interface.

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.

christgau avatar Jun 29 '19 18:06 christgau

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 Interestingly, Ubuntu LTS 18.04 does not seem to have this problem nor does my VM that I did release upgrades to take it up to 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 2020-01-12 22:44:11,815:wsdd INFO(pid 1180): using pre-defined UUID 5b89ab76-c687-5583-950f-2df89872764b 2020-01-12 22:44:11,823:wsdd INFO(pid 1180): joined multicast group ('239.255.255.250', 3702) on 192.168.10.2%ens160 2020-01-12 22:44:11,830:wsdd INFO(pid 1180): joined multicast group ('ff02::c', 3702, 22364, 2) on fe80::20c:29ff:fea7:1def%ens160 2020-01-12 22:44:15,869:wsdd INFO(pid 1180): fe80::6d1a:2512:762:4e4f:54188(ens160) - - "Probe urn:uuid:a344bf0a-ce9d-4437-8dca-c0158fafb2eb UDP" - - 2020-01-12 22:44:15,934:wsdd INFO(pid 1180): fe80::6d1a:2512:762:4e4f:54190(ens160) - - "Resolve urn:uuid:3d7aa9b6-ca30-47f0-a2c8-e37909ea6648 UDP" - -

blastagator avatar Jan 12 '20 22:01 blastagator

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.

christgau avatar Jan 13 '20 16:01 christgau