Bug #6141
WSL2: Manually adding SAT>IP Server
0%
Description
Hello!
So, long story short:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.18.35.98 netmask 255.255.240.0 broadcast 172.18.47.255
...snip...
This is the default interface of my WSL2 Debian instance. However, my real network runs in 192.168.8.x
. Hence, WSL2 can not detect my SAT>IP server automatically.
How do I tell TVHeadend about it's location? I could not find anything related to manually adding the tuner in the docs or other related documents or the config menu.
Thank you in advance!
Kind regards,
Ingwie
History
Updated by Walter av almost 3 years ago
The following topic "tvheadend: satip-client discovery not working(workaround)":
https://github.com/openwrt/packages/issues/16500
Might give you a few seperate solutions to let Tvheadend send it broadcast on a specific interface to detect tuners. Note that most current fix/workaround is OpenWrt specific but at the bottem of the first topic the arguments following arguments --bindaddr $LANIP
or satip device specific --satip_xml http://satipserveripfritzbox:49000/satipdesc.xml
will help detect a tuner.
However I think you may also need to tweak the WSL router to let forward packets in the right direction or better create a L2 bridge if possible?
[[https://develmonk.com/2021/06/05/easiest-wsl2-bridge-network-without-hyper-v-virtual-network-manager/]]
Updated by Flole Systems almost 3 years ago
- Status changed from New to Invalid
This is the bug tracker, questions should go into the forum (or read the documentation).