HDHR Port query

[Ranbato]

I'm trying to set up another Docker container (Pi-Hole) and I am getting a port conflict where it can't find my HDHR devices.  So for I haven't been able to discover the port that is conflicting; probably because I am missing the obvious.  Once I shut down the other container everything works.
In any case, this is the section of the log I think applies.  Can you tell me what port it is trying to use for the discovery?

Code:

[17] {"current": "5.0.0.191007","available": "5.0.0.191007"}
[17] Got request [172.17.0.1]: /services/service
[17] method=setting.devices
[17] parameters:
[17] method: setting.devices
[17] format: json
[17] sid: 4750a6e6-fc9c-4886-9a4e-2f14974e4044
[17] client_ip: 172.17.0.1
  [17] user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36  
  [17] setting.devices  2019-10-13 21:47:42  Renewing session: 4750a6e6-fc9c-4886-9a4e-2f14974e4044
  [17] CaptureSource.LoadAll()
  [17] [{ "id": "23",  "name": "HDHomeRun 10438FD4-0",   "channelCount": 88,   "sourceType": "HDHR", "present": false}  ,
  {  "id": "24",  "name": "HDHomeRun 10438FD4-1",   "channelCount": 88,   "sourceType": "HDHR", "present": false}  ,
  {  "id": "21",  "name": "HDHomeRun 1036D72E-0",   "channelCount": 88,   "sourceType": "HDHR", "present": false}  ,
  {  "id": "22",  "name": "HDHomeRun 1036D72E-1",   "channelCount": 88,   "sourceType": "HDHR", "present": false}  ,
  {  "id": "20",  "name": "IPTV Device",   "channelCount": 0, "sourceType": "IPTV", "present": true}   ]...snip... 
  [17] Got request [172.17.0.1]: /services/service
  [17] method=setting.devices
  [17] parameters:
  [17] format: json
  [17] sid: 4750a6e6-fc9c-4886-9a4e-2f14974e4044
  [17] client_ip: 172.17.0.1
  [17] user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36  
  [17] setting.devices  2019-10-13 21:47:44  Renewing session: 4750a6e6-fc9c-4886-9a4e-2f14974e4044 System.Net.Sockets.SocketException (98): Address already in use at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)   at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.UdpClient..ctor(Int32 port, AddressFamily family)  at NShared.Utility.SATIPHelper.StartDiscovery() 
  [17] CaptureSource.LoadAll()  
  [17] [  { "DeviceID": "1036D72E",  "LocalIP": "192.168.1.13",  "Legacy": 1, "BaseURL": "http://192.168.1.13", "DiscoverURL": "http://192.168.1.13/discover.json" },
          { "DeviceID": "10438FD4",  "LocalIP": "192.168.1.37",  "BaseURL": "http://192.168.1.37", "DiscoverURL": "http://192.168.1.37/discover.json", "LineupURL": "http://192.168.1.37/lineup.json"  }  ]  
  [17] Found HDHomeRun: 1036D72E (2 tuners) 
  [17] Found HDHomeRun: 10438FD4 (2 tuners)
  [17] HDHR Discover [17] Local Devices: <devices>  </devices>

The Pi-hole container uses the following:
      - 443/tcp
      - 53/tcp
      - 53/udp
      - 67/udp
      - 80/tcp

[mvallevand]

Are you sure it is Pi-hole. Sat>IP uses UPnP discovery, maybe you added a UPnP server?

Martin

[Ranbato]

This is the instructions I am following, so I am pretty sure. Haven't had time to see what i may have gotten wrong yet.
http://tonylawrence.com/posts/unix/synol...ogy-ports/

[mvallevand]

I was probably confusing the error on Sat>IP discovery with HDHR discovery. Do you have the two docker lines needed for the legacy HDHR in your config and if so is the HOST IP correct?

Martin

[Ranbato]

Haven't had a chance to follow up on this, too busy at work getting ready for Black Friday.

Plus, when I fiddle with DNS and DHCP it always takes forever to fix all the things I break 

[Ranbato]

Found the root issue :  I forgot I had remapped ssh from 22 to 8022 and of course it always had issues when I was connected to it trying to diagnose what was going wrong 

There still seems to be some funny business with detecting legacy HDHR devices if their IP changes, but I reset everything completely and I set my HDHRs to static IPs in my DHCP server so I shouldn't encounter that issue again.

Sub should probably look into the detection code on startup because I don't think that issue is completely fixed.

[sub]

Found the root issue :  I forgot I had remapped ssh from 22 to 8022 and of course it always had issues when I was connected to it trying to diagnose what was going wrong 

Good find.

There still seems to be some funny business with detecting legacy HDHR devices if their IP changes, but I reset everything completely and I set my HDHRs to static IPs in my DHCP server so I shouldn't encounter that issue again.

Sub should probably look into the detection code on startup because I don't think that issue is completely fixed.

It currently only detects changed IP addresses when you start the software. It wont detect IP address changes that happen while it's already running. (ie, would slow down live tv starts etc if I did it every time NextPVR used the device)