Solved - Network scanning fails
Added by Yann Ormanns about 6 years ago
Hi everyone,
I am using tvheadend 4.2.6-62 on my Kodi HTPC (LibreELEC), and now I want to switch the setup to a 24/7 system. This system runs on Gentoo, and I simply do not manage tvheadend to scan the network successfully.
I use a Fritz!Box 6490 with Fritz!OS 7 as a Sat>IP streaming server - so I pass the argument "--satip_xml http://10.0.0.1:49000/satipdesc.xml" to tvheadend.
Aside my HTPC, I have tested a few versions:
- 4.2.7-17 on Ubuntu
- 4.3-1216 on Gentoo
- 4.3-1517 on Gentoo
Everyone of them is unable to get some data in while scanning the network, as the following log lines from the newest build show:
2018-11-02 17:56:07.851 [ INFO]:subscription: 0074: "scan" subscribing to mux "402MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #1 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription" 2018-11-02 17:56:07.851 [ INFO]:mpegts: 610MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #2 (10.0.0.1@UDP) 2018-11-02 17:56:07.851 [ INFO]:subscription: 0075: "scan" subscribing to mux "610MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #2 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription" 2018-11-02 17:56:07.851 [ INFO]:mpegts: 434MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #3 (10.0.0.1@UDP) 2018-11-02 17:56:07.851 [ INFO]:subscription: 0076: "scan" subscribing to mux "434MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #3 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription" 2018-11-02 17:56:07.851 [ INFO]:mpegts: 362MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #4 (10.0.0.1@UDP) 2018-11-02 17:56:07.851 [ INFO]:subscription: 0077: "scan" subscribing to mux "362MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #4 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription" 2018-11-02 17:56:12.850 [ INFO]:mpegts: 362MHz in DVB-C Netzwerk - scan no data, failed 2018-11-02 17:56:12.850 [ INFO]:subscription: 0077: "scan" unsubscribing 2018-11-02 17:56:12.851 [ INFO]:mpegts: 434MHz in DVB-C Netzwerk - scan no data, failed 2018-11-02 17:56:12.851 [ INFO]:subscription: 0076: "scan" unsubscribing 2018-11-02 17:56:12.851 [ INFO]:mpegts: 610MHz in DVB-C Netzwerk - scan no data, failed 2018-11-02 17:56:12.851 [ INFO]:subscription: 0075: "scan" unsubscribing 2018-11-02 17:56:12.851 [ INFO]:mpegts: 402MHz in DVB-C Netzwerk - scan no data, failed 2018-11-02 17:56:12.851 [ INFO]:subscription: 0074: "scan" unsubscribing
My config under the newest build (the tuners have a slightly different config, because I tested the impact of the "specinv" parameter):
{ "tunercfgu": "Auto", "tcp_mode": false, "fast_switch": true, "fullmux_ok": false, "sigscale": 240, "pids_max": 32, "pids_len": 127, "pids_deladd": false, "fe": true, "piloton": false, "pids21": true, "skip_ts": 0, "disableworkarounds": false, "device_uuid": "663d5d6c-f9f8-4bb4-84d4-444E6D2A2DDF", "frontends": { "DVB-C #1": { "delsys": 0, "transport_mode": 0, "udp_rtp_port": 0, "tdelay": 50, "play2": true, "grace_period": 0, "teardown_delay": false, "pass_weight": 1, "specinv": 1, "enabled": true, "priority": 0, "spriority": 0, "displayname": "SAT>IP DVB-C Tuner", "ota_epg": false, "initscan": false, "idlescan": false, "free_weight": 0, "remove_scrambled": false, "networks": [ "3d276401e06bc0c924cf3e94b581833b" ], "linked": "", "type": "DVB-C", "uuid": "783c66242e42be1959296f358a7668f8" }, "DVB-C #2": { "delsys": 0, "transport_mode": 0, "udp_rtp_port": 0, "tdelay": 50, "play2": true, "grace_period": 0, "teardown_delay": false, "pass_weight": 1, "specinv": 1, "tunerbindaddr": "", "enabled": true, "priority": 0, "spriority": 0, "displayname": "SAT>IP DVB-C Tuner", "ota_epg": false, "initscan": false, "idlescan": false, "free_weight": 0, "remove_scrambled": false, "networks": [ "3d276401e06bc0c924cf3e94b581833b" ], "linked": "", "type": "DVB-C", "uuid": "aca1f336b31c6552d43eb555ea1ca6b7" }, "DVB-C #3": { "delsys": 0, "transport_mode": 0, "udp_rtp_port": 0, "tdelay": 50, "play2": true, "grace_period": 0, "teardown_delay": false, "pass_weight": 1, "specinv": 2, "enabled": true, "priority": 0, "spriority": 0, "displayname": "SAT>IP DVB-C Tuner", "ota_epg": false, "initscan": false, "idlescan": false, "free_weight": 0, "remove_scrambled": false, "networks": [ "3d276401e06bc0c924cf3e94b581833b" ], "linked": "", "type": "DVB-C", "uuid": "4ac81c649fd42d421cbabed680f64c0b" }, "DVB-C #4": { "delsys": 0, "transport_mode": 0, "udp_rtp_port": 0, "tdelay": 50, "play2": true, "grace_period": 0, "teardown_delay": false, "pass_weight": 1, "specinv": 2, "enabled": true, "priority": 0, "spriority": 0, "displayname": "SAT>IP DVB-C Tuner", "ota_epg": false, "initscan": false, "idlescan": false, "free_weight": 0, "remove_scrambled": false, "networks": [ "3d276401e06bc0c924cf3e94b581833b" ], "linked": "", "type": "DVB-C", "uuid": "356e1cbe1d430d3bb6fcecdbcbac5fce" } } }
What can I do to locate the cause for this problem? If any information is missing, please let me know.
Kind regards,
Yann
Replies (26)
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
I finally got it working. It seems as one iptables rule was responsible for the problems - but I cannot figure out, which one. Although I allowed all traffic between my FritzBox and the PC, it seems that some traffic was blocked. Afterwards, I logged all blocked traffic and derived new firewall rules from that.
Thank you for your effort, Al Bundy!
Kind regards,
Yann
- « Previous
- 1
- 2
- Next »