Sat>IP device not accessible

[Connor]

Dear,

I wanted to do my first steps with NPVR in order to compare it performance wise with TVHeadend.
To do so, I set up a Docker instance on my Synology NAS. The container is running well and is using the same net as the host.

Unfortunately, I do not have access to my Kathrein EXIP 414E (Sat>IP) device.
Due to the settings, it should be accessible via the host net - but it isn't.

So, what can I do - or how can I add what kind of information?
I tried to include the log files as attachment - but this is seemingly not allowed.

Thank you for your feedback and support,
best regards,

Connor

[sub]

So, what can I do - or how can I add what kind of information?
I tried to include the log files as attachment - but this is seemingly not allowed.

You need to attach the log files as a .zip

ie, click the 'log files' button on the Settings->About screen. This will give you a zip file. You can attach the zip as an attachment.,

[Connor]

Ah, OK.
In this case the Finder tricked on me, since my ZIP files are always directly unzipped.
Here you go...

[Connor]

Anything I can do to support my request any further?

[sub]

Sorry - I'm a bit swamped, so things full through the cracks if you get me at the wrong time.

I've just taken a look through the logs. There is no sign of SAT>IP device announcing itself when requested (via udp broadcast), so I can only assume something about the docker network setup is stopping that from happening.

There is a way to pass an SATIP_DEVICES environment variable with the server url, and it'll go directly to the SAT>IP device rather than relying on the udp broadcast for detection. From memory, with docker it's adding something like:
--env SATIP_DEVICES=http://169.168.1.15/octoserve/octonet.xml

The trick will be determining what the url is for you SAT>IP device, since they vary from device to device. The above is the url for my DigitalDevices 8 tuner Octopus.NET SAT>IP server. Hopefully it's web app might show you the url you need to use.

[Connor]

Got it - thank you for guiding me.
For reference - EXIP 414E uses http://<IP>/rootDescr as server URL.

One further question - my setup is not finding any channels, as the RSTP connection fails with

"Error in RSTP data thread: Connection timed out".

I guess this might be port related. Which port are you using (554/ 9983)? and how can I set the port to 9983 in general?

Thank you for supporting me here,

best regards,

Connor

[sub]

Got it - thank you for guiding me.
For reference - EXIP 414E uses http://<IP>/rootDescr as server URL.

One further question - my setup is not finding any channels, as the RSTP connection fails with

"Error in RSTP data thread: Connection timed out".

I guess this might be port related. Which port are you using (554/ 9983)? and how can I set the port to 9983 in general?

Thank you for supporting me here,

best regards,

Connor

Can you post the logs?

[sub]

I guess this might be port related. Which port are you using (554/ 9983)? and how can I set the port to 9983 in general?

Is that the port they're using for RTSP data, or the web admin? They're usually different ports.

At the moment it's hardcoded for 554, but I also haven't come a device using a different port. Does your http://<IP>/rootDescr contain any info that refers to a different port?

[Connor]

For sure - now that I know, how to do it ;-)

As a side note: The issue with RSTP ports in well known for me from the TVHeadend, which is only working on port 9983.

And by the way: I also realised that the ENV variable RSTP_PORT is not the right try.

[sub]

I can't see any way to detect the port, but I guess I could make 554 for the default, but let the user override it with SATIP_RTSP_PORT environment variable