Virtual NIC, init.d and network interfaces

Hi guys,
I am trying to add some virtual NIC for tvheadend as described in the link below, but I cannot find any network interface or tvheadend in init.d.

Are these network settings somewhere else located in osmc?


This may help:

Thanks Tom.

Thanks Tom, I have to take it easy and try out what explained in that forum.
The second step after that will be:

“open /etc/init.d/tvheadend, find the line reading ARGS=”-f" and append something like --satip_xml within the quotes. save the file and restart Tvheadend."

But there is no tvheadend file in init.d
Is this file located elsewhere in this osmc implementation?


Have you tried installing TVHeadend from the OSMC store? It will probably be easier to setup.

/etc/init.d/tvheadend - has probably been replaced with systemd unit file in:


Thanks Tom.

@lost Just tried your instructions on a Debian VM, and /etc/init.d/tvheadend exists here.

“dpkg -i libssl1.0.0_1.0.1t-1+deb8u6_i386.deb”

If you installed this version of libssl, this may well be the problem as the vero4k uses a different cpu architect. I think its already included with osmc, so you shouldn’t have need to install it; but if you do you want this:

Thanks Tom.

@lost Have you seen that there is a how-to-topic for the AVM DVB-C at [HowTo] Configure Tvheadend 4.2 and the Sat>IP Server AVM FRITZ!WLAN Repeater DVB-C on OSMC ?

I think this can be adapted for the AVM 6490 with 4 tuners, so you need 4 additional ipv4, in TVHeadend its DVB-C4 device, etc.

Hm, something else seems not okay also. I have a Fritzbox 6490 dvb-c from Vodafone/ Kabel D.
The FW is 6.69 (or 6.65, I can’t see it right now) and is pushed by the provider, not user upgradable.
Deer is no DVB-C menu on it, nor satip or iptv. That might be also an issue, all postings about this hack are showing a Fritzbox menu with dvb-c menus.

The provider 6490 boxes normally do not have DVB-C released for the customers; only the free AVM branded boxes on the market.
Here the same with my AVM 6490 from Unitymedia NRW.

Not even think about re-branding the box with an AVM firmware; the internet is full of reports and threads where this ended in a brick. Also, the provider would recognize it at once.