Project

General

Profile

Bug #3449

Two TVheadend instances -- SAT>IP autodiscovery broken

Added by Alex L. almost 9 years ago. Updated almost 9 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
SAT>IP
Target version:
-
Start date:
2015-12-29
Due date:
% Done:

0%

Estimated time:
Found in version:
4.1-1246~gdc4e037
Affected Versions:

Description

Hi folks!

My setup is as follows:
- TVheadend on a Rasperry Pi; Jessie; 4.1-1246~gdc4e037
- TVheadend on a Ubuntu; 15.10; 4.1-1246~gdc4e037
- Both are connected via a switch using IPv4; no IPv6 active at all

I want the TVH on my Pi to automatically add the other TVH instance.
Using the upnc trace subsystem, i figured out that the Pi receives the packets from the Ubuntu instance.
The Pi does receive the packet containing the configuration URL http://XXX.XXX.XXX.XXX:9981/satip_server/desc.xml, but it seems that it does not process the packet properly.
No satip server is added to the list of DVB inputs.

If i start the TVH on my Pi using the --satip_xml parameter, everthing works like a charme. The Pi finds the other TVH instances and adds it to its DVB inputs.
This looks like a bug to me, but further debugging needs to be done to narrow the issue down.
Can you pls give me any advice what the next steps are?

Cheers,
flip

History

#1

Updated by Jaroslav Kysela almost 9 years ago

Do you allow the HTTP (WEB) access on the SAT>IP server for the SAT>IP client ? The '--trace httpc' might give you a reason why the desc.xml is not fetched correctly.

#2

Updated by Alex L. almost 9 years ago

I started TVH using '--trace httpc,upnp,udp,satip -d -S', but there is no output from httpc at all.
The last thing about satip i see in the output is '2015-12-29 12:27:19.855 [ TRACE] upnp: unicast - received data from 192.168.178.xxx:27655 [size=337]'. This is the response from the second TVH instance.
In addition to that, i can manually download the desc.xml file from the TVH on my Ubuntu machine using wget. Therefore, i suppose this is not fw-related.

#3

Updated by Alex L. almost 9 years ago

If i specify the --satip_server parameter, the http client works correctly. I see a lot of debug output telling me that it can successfully talk to my satip server.

#4

Updated by Jaroslav Kysela almost 9 years ago

No idea, testing two instances on same machine and the upnp discovery works here. It seems related to your network settings.

The satip_discovery_service_received() fcn in satip.c should be called when UDP packet is received and satip_discoveries list should be updated there.

#5

Updated by Alex L. almost 9 years ago

Oh my good. I'm so sorry!
Both TVH instances use the same uuid because i copied the config from one machine to the other....
Therefore, the second TVH wasn't add. :(
I deleted the uuid from the config. That forced the tvh to generate a new one. Voilá. It works! :)

#6

Updated by Jaroslav Kysela almost 9 years ago

  • Status changed from New to Invalid

Also available in: Atom PDF