sat > ip tuner

[gromgsxr]

is sat>ip meant to work in the docker image? as it does not find my triax tss400, i tried setting net to host to see if this would help but still not seeing the tuner. the windows version at least detects it but scanning for channels does not work either

[sub]

is sat>ip meant to work in the docker image? as it does not find my triax tss400, i tried setting net to host to see if this would help but still not seeing the tuner.

The SAT>IP discovery protocol uses a broadcast to the network to locate devices. If your docker networking mode gives you an ip address on the same subnet as your SAT>IP device, then it should find it. (I have in mind a small tweak in mind so that you can explicitly pass in the address of a SAT>IP server, to allow it to work even from a different subnet)

the windows version at least detects it but scanning for channels does not work either

If you can post the logs showing a scan, I'll take a look. Its probably something minor stopping it from working.

[gromgsxr]

The SAT>IP discovery protocol uses a broadcast to the network to locate devices. If your docker networking mode gives you an ip address on the same subnet as your SAT>IP device, then it should find it. (I have in mind a small tweak in mind so that you can explicitly pass in the address of a SAT>IP server, to allow it to work even from a different subnet)

i have attached the logs from the docker version it is on the same subnet as the tuner this was in host mode so docker should have access to all ports

i will start a post in the windows section as well

[gromgsxr]

i just tried the arm32v7 on an odroid hc1 using the same settings the arm32v7 docker version finds my tuners but the amd64 running on my dell server version fails to detect them both are running docker inside open media vault.

the arm32v7 & windows versions both fail to tune any channels

[sub]

i just tried the arm32v7 on an odroid hc1 using the same settings the arm32v7 docker version finds my tuners but the amd64 running on my dell server version fails to detect them both are running docker inside open media vault.

Have you grabbed the latest amd64 build, posted yesterday? I did do some SAT>IP related changes

the arm32v7 & windows versions both fail to tune any channels

Ok, I'll follow up in your Windows thread.

[gromgsxr]

is this "Unexpected error with HDHR discovery: System.Net.WebException: The operation has timed out." message in my log to do with the amd64 docker version not seeing my tuners?

[sub]

is this "Unexpected error with HDHR discovery: System.Net.WebException: The operation has timed out." message in my log to do with the amd64 docker version not seeing my tuners?

Not specifically related to that message. The same type of thing happens though, but it's not logged with SAT>IP. Basically it's sending a broadcast to discover devices, and not hearing back.

Whether it's discovered or not will vary depending on the style of networking the container is using. If it's allocated a ip address on the same subnet, and has access to other devices on the network then it should be discovered. If it's using an internal nat, then the device discovery wont work. I'm still trying to think what to do about this - I might need to add the ability to add SAT>IP device addresses on the docker command line, so that it doesn't need to do the discovery (since the protocol is only designed to work on the same network)

[gromgsxr]

Not specifically related to that message. The same type of thing happens though, but it's not logged with SAT>IP. Basically it's sending a broadcast to discover devices, and not hearing back.

Whether it's discovered or not will vary depending on the style of networking the container is using. If it's allocated a ip address on the same subnet, and has access to other devices on the network then it should be discovered. If it's using an internal nat, then the device discovery wont work. I'm still trying to think what to do about this - I might need to add the ability to add SAT>IP device addresses on the docker command line, so that it doesn't need to do the discovery (since the protocol is only designed to work on the same network)

ah i see well its using host mode so should have access to all the network discovery stuff