SAT>IP on ethernet conflicts with WiFi internet

Help and Support
1

Hello, I’m hoping someone can help with my OSMC set up on a Raspberry Pi 4. I have a SAT>IP box (Telestar Digibit Twin) connected directly to the ethernet port on the Pi. The Pi is also connected to my home WiFi.

The problem is:
If /etc/connman.conf contains PreferredTechnologies=ethernet,wifi

  • TVHeadend finds the Digibit box and I can watch live TV in Kodi
  • but the Pi has no internet

If /etc/connman.conf contains PreferredTechnologies=wifi,ethernet

  • the Pi has internet
  • but TVHeadend cannot see the Digibit box

In both configurations the Pi connects to the WiFi just fine (I can ssh into it from my laptop). But I would really like it to be able to reach the internet, eg to keep the time correct and to be able to install add-ons in Kodi.

Is there any way to get both the Pi internet connection (over WiFi) and the SAT>IP box (over ethernet) working at the same time?

2

Hi, that’s an interesting but complex situation since the Telestart Digibit Twin is a DHCP enabled device as well afaIcs. Adhoc it might help to give the OSMC ethernet if a fix IP and the Telestar if as well; there is a web interface of the Telestar you can reach, if you connect a PC to it (believing the manual).

I think we first need to see logs in both cases to get an idea what exactly happens in this environment:

The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue (here wait a minute when you see the mediacenter GUI)

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

image
image960×539 41.4 KB

4

Hi, thanks for your help. If I’ve done this right the logs are

Ethernet preferred (satellite TV works, no internet)
https://paste.osmc.tv/anojorewul

Wifi preferred (internet works, no satellite TV)
https://paste.osmc.tv/ijalaweruv

5

Wifi prefered is the right way to go. In the logs I can see that there is always a zeroconf ip configuration, so there is no dhcp on the ethernet port means the Telestar router is a pure dhcp client.

I suggest to try the Thethering method to get into contact with your Telestar device:

  • in MyOSMC ENABLE the wired adapter
  • the Wireless settings seems to be correct since you state you can even reach the internet when using wifi prefered
  • Now, in Thethering activate “Wifi to Ethernet” and enable this function

image
image1917×1069 112 KB

This makes the OSMC device a DHCP server on the ethernet port with the network range 192.168.0.0/24. Your Telestar device should get now ipv4 192.168.0.2 and the OSMC device will get 192.168.0.1 on the ethernet port.
From here the SAT>IP server should be visible (in theory).

Addition: For tests I connected a Vero4k+ directly to the ethernet port of a VeroV and configured the VeroV as described above. After booting the Vero4k+, I could ping it from the VeroV using 192.168.0.2 and even ssh to it.

Here, I did not change /etc/connman.conf and the content is

 more /etc/connman.conf
[General]
PreferredTechnologies=ethernet,wifi
SingleConnectedTechnology=false
AllowHostnameUpdates=false
TetheringTechnologies=ethernet,wifi
PersistentTetheringMode=true
NetworkInterfaceBlacklist=vmnet,vboxnet,virbr,ifb,docker,veth
1 Like
6

Thanks Jim,
With “WiFi to Ethernet” tethering enabled:

  • OSMC can reach the internet
  • Telestar device is not found (no adapters showing in tvheadend)
  • but I can ping 192.168.0.2 from OSMC

This is the same for either setting of PreferredTechnologies.
Log is here: https://paste.osmc.tv/okibigapol

7

Which IP did you configure in TVHeadend?

1 Like
8

I didn’t configure any IP. Previously TVHeadend just automatically found the Telestar.
Is there somewhere in the interface I can enter the IP?

9

It’s working! fzinken’s comment got me searching in the right direction.

I edited /lib/systemd/system/tvheadend.service, adding this to the ExecStart line:
--satip_xml http://192.168.0.2:38400/description.xml

Then after a reboot I have working satellite TV and also working internet for OSMC.

Many thanks to JimKnopf and fzinken, I really appreciate your help.

1 Like
10

Use a systemd drop in so that the execstart line isn’t overwritten by updates

Sam

1 Like