Not Finding Devices

[BrettB]

2022-12-12 14:55:08.155 [VERBOSE][65] About to attempt HDHR discovery via UDP
2022-12-12 14:55:08.173 [VERBOSE][65] ...skipping non-Ethernet network device
2022-12-12 14:55:08.173 [VERBOSE][65] ...skipping non-Ethernet network device
2022-12-12 14:55:08.173 [VERBOSE][65] ...skipping non-Ethernet network device
2022-12-12 14:55:08.173 [VERBOSE][65] ...sending on device: System.Net.NetworkInformation.SystemUnicastIPAddressInformation
2022-12-12 14:55:08.173 [VERBOSE][65] ...skipping non-Ethernet network device

I might need to give you a new build with a tweak to that logging, so we can see the address it sent to. We can see it tried to send the UDP discovery though, skipping a few non-Ethernet network devices, but sending to one.

(sorry - busy next couple of hours)

Sub: The DCR uses USB network connection between the host and the device. I wonder if it might be showing up for you in Linux as a "non-Ethernet network device" and therefore being skipped. Maybe adjust that verbose logging message to also include the device name for the skipped device?

[mvallevand]

That is why I wanted to see the SD (Silicon Dust) output in Wireshark.

Martin

[sub]

I've attached a build with slightly more better logging around for these lines.

While it's a USB device, it represents itself to the system as a USB network adapter.

[mvallevand]

That is what I found interesting his laptop is listening on

2022-12-12 14:22:00.688 [DEBUG][11] address: 192.168.1.188

and the device responds on the same subnet C:\Program Files\Silicondust\HDHomeRun>hdhomerun_config.exe discover
hdhomerun device 20200EC0 found at 192.168.1.155

so you should be sending out discovery broadcasts to 192.168.1.255 as a minimum.

Martin

[jcole998]

Verbose logs for latest NShared.dll.

[mvallevand]

What type of Ethernet card do you have in the laptop for 192.168.1.188 It isn't detecting it.

Martin

[jcole998]

Attached is a snapshot of devices on this laptop.

[mvallevand]

On a hunch I unplugged my network card and turned on wifi and NextPVR "skipped" my wifi device and there was no UDP discovery.

@JohnC if you plug in a network cable and use it instead of wifi NextPVR might be able to detect your device and then on the Settings General Page turn off the scan on startup which could disable it when you are wifi only.

Code:

2022-12-14 18:43:56.377    [VERBOSE][6]    About to attempt HDHR discovery via UDP
2022-12-14 18:43:56.418    [VERBOSE][6]    ...sending on device: Realtek PCIe GbE Family Controller [169.254.205.253]
2022-12-14 18:43:56.419    [VERBOSE][6]    ...sending on device: Realtek PCIe 2.5GbE Family Controller [172.16.3.3]  < static wired NIC no cable.
2022-12-14 18:43:56.827    [VERBOSE][6]    ...skipping non-Ethernet network device
2022-12-14 18:43:56.827    [VERBOSE][6]    ...skipping non-Ethernet network device
2022-12-14 18:43:56.827    [VERBOSE][6]    ...skipping non-Ethernet network device
2022-12-14 18:43:56.827    [VERBOSE][6]    ...sending on device: Bluetooth Device (Personal Area Network) #2 [169.254.246.43]
2022-12-14 18:43:56.827    [VERBOSE][6]    ...skipping non-Ethernet network device

Martin

[jcole998]

(Long delay for this reply. Holidays intervened. My apologies.)

Good hunch. Unfortunately, the laptop is wifi-only with no socket for an ethernet cable. Maybe sub could add the ability to sense wifi networks(like HDHR? Maybe an option to NOT try discovery at app/service startup and just use a manually filled CAPTURE_SOURCE database table?)

JohnC

[sub]

Maybe an option to NOT try discovery at app/service startup and just use a manually filled CAPTURE_SOURCE database table?)

FYI, setting <ScanDevicesAtStartup>false</ScanDevicesAtStartup> in config.xml will stop it from scanning devices at startup.