Not Finding Devices
|
2022-12-07, 08:34 PM
(This post was last modified: 2022-12-07, 08:36 PM by mvallevand.)
For know just turn Windows Defender Firewall off and too see if it is blocking access. NextPVR should be doing the same UDP discovery as the Silicon Dust app your screen shot didn't cover the most important part of the rules.
Martin
2022-12-08, 08:29 PM
As suggested, I turned off Windows Defender Firewall entirely for both public and private networks and then restarted the computer. Still no devices on rescan, So...
As my last gasp at trying what I can to fix this, I carefully made sure only one NextPVR service is running, On the Win11 laptop I tried V4 on both ports, 8866 and 8867. Worked as expected. V6 finds no devices on either port. I then carefully compared firewall status between the laptop and my Win10 desktop where V6 works on port 8867. Anything that looked related to NextPVR or HDHomeRun showed the same settings with regard to public/private networks. Finally, I copied the desktop V6 config.xml and npvr.db3 into the laptop NPVR-data folder and started V6. Devices were displayed as expected but were shown as unavailable. Attached log files were zipped up at this point. That's all I can do. I'd like to move to V6 and access streaming capabilities but V6 still uses TCP connections which are not reliable on my desktop. I was hoping a new, speedier laptop may be the answer but V6 won't run. I dread the day when cableland will finally break V4, a most reliable PVR. Thanks for your help. JohnC
2022-12-08, 08:34 PM
Sub will need to answer why UDP discovery is not working I think DeviceHostWindows only uses tcp but maybe there is something else.
Martin
2022-12-11, 02:42 AM
It's hard to tell what is happening.
In theory it should be able to be discovered by HDHomeRun discovery broadcast logic. This UDP, so your devices need be on the same subnet etc. To give us more detail, you'd probably need to try capturing the first 15 seconds of network activity while NextPVR is starting, using the free WireShark utility. Ideally, we should see NextPVR sent a UDP broadcast on port 65001, and we can check what responses it gets back from the network.
2022-12-11, 02:33 PM
I've had some success using Wireshark.
Martin suggested the following test: C:\Program Files\Silicondust\HDHomeRun>hdhomerun_config.exe discover. This retuned the correct IP address of my triple tuner device. Can I use this command to try and narrow down what transactions to look for when V6 tries it? Does V4 use the same discovery logic as V6 regarding ports and protocols? JohnC
2022-12-11, 02:45 PM
Yes you can use this filter
udp.port == 65001 and you should see it going out to your subnet with responses coming back. Martin
2022-12-11, 07:41 PM
Attached is the Wireshark output for the HDHomeRun discovery command: hdhomerun_config.exe discover.
I can do more... JohnC
2022-12-11, 08:12 PM
(This post was last modified: 2022-12-11, 08:15 PM by mvallevand.)
What about NextPVR when you click rescan devices? I don't think the pcap is as good as just knowing it is sending and receiving
NextPVR logs too. Martin |
|
|
