Bug #5101
EyeTV Netstream 4C
0%
Description
tvheadend will not detect my EyeTV Netstream 4C
Firmware Version: 1.1.0-390r1
what can i do?
i found this thread https://tvheadend.org/boards/5/topics/16084
but a reset of the device will not work
Files
History
Updated by Chris master over 6 years ago
saen acro wrote:
https://www.geniatech.eu/faq/eyetv-netstream-4c-does-not-support-upnp-or-dlna/
ok thanks, so i will be sent it back
Updated by saen acro over 6 years ago
Factory reset device and see if there will be change.
geniatech forum is useless for any information
Updated by Chris master over 6 years ago
saen acro wrote:
Factory reset device and see if there will be change.
geniatech forum is useless for any information
if i rest with the restbutton on the backside it will change nothing.
same firmware, only my ip will be set back to DHCP
Updated by da h4xX0rz1sT over 6 years ago
I once had the Netstream 4Sat for testing (not the cable version) and it was recognized without any issues. You don't need UPnP to run a SAT>IP server.
Do you have the latest firmware installed? If you launch their app on the network, it will automatically ask you whether you want to upgrade if there is a new firmware.
Unfortunately, AFAIK there is no way to manually add a tuner to TVh, except maybe placing some hacked configuration file. Are you sure your network setup is correct? Can you connect with the app on your local network? Did you try any other software besides TVh, e.g. DVBViewer?
Updated by Chris master over 6 years ago
da h4xX0rz1sT wrote:
I once had the Netstream 4Sat for testing (not the cable version) and it was recognized without any issues. You don't need UPnP to run a SAT>IP server.
Do you have the latest firmware installed? If you launch their app on the network, it will automatically ask you whether you want to upgrade if there is a new firmware.
Unfortunately, AFAIK there is no way to manually add a tuner to TVh, except maybe placing some hacked configuration file. Are you sure your network setup is correct? Can you connect with the app on your local network? Did you try any other software besides TVh, e.g. DVBViewer?
the cable version had only this firmware. With the app it works fine but i cant see it without hack in tvheadend.
i send this tuner back to amazon. at the moment i have a raspberry with 2 technotrend cable tuners. This raspberry make a sat ip server with tvheadend and so i connect to my big tvheadend server. cable is optional for me
Updated by da h4xX0rz1sT over 6 years ago
Sad, 4Sat worked fine here with TVh. But their app is a piece of crap, support sucks, and their device is insecure with an open telnet, so you're right, better get rid of it
Updated by Marti McFly over 6 years ago
- File nok_tvheadend.log nok_tvheadend.log added
- File nok_netstream.log nok_netstream.log added
Hej da h4xX0rz1sT,
I bought the netstream 4c, too. It is the same firmware Chris master used to run.
Through ssh I've got the service announcement (ssdp) enabled and the device is shown in tvheadend.
But badly TVH only shows status BAD. The device returns 503 Service Unavailable. Please find my logs attached.
Viewing television from Eyetv and DVBViewer is absolutely no problem.
A test in VLC has shown that it returned a stream by http...
http://192.168.178.94/?freq=450&msys=dvbc&sr=6900&specinv=0&mtype=256qam&pids=0,110,120,100,130
But didn't by rtsp...
rtsp://192.168.178.94:554/?freq=450&msys=dvbc&sr=6900&specinv=0&mtype=256qam&pids=0,110,120,100,130
Furthermore the http request didn't like when "&specinv=0" was missing and didn't like when "&fe=1" was added.
I might add an ok-log if you wish?
If you need, we could do a TV-Session (TeamViewer), too?
Marti
Updated by Marti McFly over 6 years ago
- File description.xml description.xml added
The Sat>Ip description is served under...
Updated by Marti McFly over 6 years ago
The Sat>Ip / HTTP Control is done with port 80. Only the description is served with port 81.
Updated by saen acro over 6 years ago
M F wrote:
The Sat>Ip / HTTP Control is done with port 80. Only the description is served with port 81.
why not test for open ports
sudo nmap -n -PN -sT -sU -p- netstream_4c_IP
then
sudo nmap -PN -p port_number -sN netstream_4c_IP
to see open ports service identification
Updated by Marti McFly over 6 years ago
Hey saen acro,
i know the open ports of the device. I'm able to login and show them....
[netstream-4c]$ netstat -lapn
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:554 0.0.0.0:* LISTEN 898/Tombea
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 898/Tombea
tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 898/Tombea
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1607/dropbear
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 1593/telnetd
tcp 0 300 192.168.178.94:22 192.168.178.201:49214 ESTABLISHED 3821/dropbear
tcp 0 0 192.168.178.94:22 192.168.178.87:49914 ESTABLISHED 2634/dropbear
netstat: /proc/net/tcp6: No such file or directory
udp 0 0 0.0.0.0:59415 0.0.0.0:* 898/Tombea
udp 0 0 0.0.0.0:63565 0.0.0.0:* 898/Tombea
udp 0 0 239.255.255.250:1900 0.0.0.0:* 898/Tombea
udp 0 0 192.168.178.94:1900 0.0.0.0:* 898/Tombea
netstat: /proc/net/udp6: No such file or directory
raw 0 0 0.0.0.0:2 0.0.0.0:* 2 898/Tombea
raw 0 0 0.0.0.0:2 0.0.0.0:* 2 898/Tombea
raw 0 0 0.0.0.0:255 0.0.0.0:* 255 898/Tombea
raw 0 0 0.0.0.0:255 0.0.0.0:* 255 898/Tombea
netstat: /proc/net/raw6: No such file or directory
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node PID/Program name Path
unix 5 [ ] DGRAM 1094 784/syslogd /dev/log
unix 2 [ ] DGRAM 40272 898/Tombea
unix 2 [ ] DGRAM 1948 1572/udhcpc
unix 2 [ ] DGRAM 1311 905/ifplugd
My only problem is, that tvheadend isn't able to open the stream. VLC/EyeTV/DVBiewer is able to open any stream.
It appears that netstream 4c needs to be controlled by the http connection. rtsp is used for transport of the strream only. Within the http stream it seems not to be allowed to address any certain tuner (not allowed parameter: ?...&fe=1). It has to be up to the box which tuner it's using. And for any reason there has to be a parameter called "?...&specinv=0". Without that, nothing will happen except the 503 Errorcode.
The Sat>Ip desciption is distruputed/discovered by "http://192.168.178.94:81/description.xml". The http control connection is done by the port 80. The stream is send by the port 554.
Please check the attached logs for details.
Reference:
http://www.satip.info/sites/satip/files/resource/satip_specification_version_1_2_2.pdf
Marti
Updated by saen acro over 6 years ago
Not sure this app Tombea do, but there is no manual
http://urup.net/?p=42
[ARCLinux]$ Tombea --help Elgato DVB>IP Server 1.1.0-402r1, Feb 19 2015, 17:49:21 Compiled for ViXS ARC700 platform, XCode Version 4A5546 Copyright (C) 2013-2014 Elgato Systems GmbH, Germany
there is written something RTSP streaming
http://ipfelgruen.de/forum/hardware/peripherie/tv-karten-tuner-und-empfänger/2267-netstream-4c-expertmode
open source contents
https://opensource.geniatech.eu/Netstream4X/1.1.0.402r1/
Updated by Marti McFly over 6 years ago
Tombea is the so called firmware. It provides all the services. I've got the Tombea out of the "open source contents", have put it into /persistent and ran it. The box is represented with Firmware "IP Server 1.1.0-402r1" from then.
EyeTV, VLC, DVBViewer work great, but tv does not.
The expert mode seems to have a different PIN and UI, than the earlier Netstreams had. Honestly I don't know what it is for.
The forum is talking about emulating the SAT>IP protocol for dvb-c. I've got that option enabled. But then then box is announced as sat receiver. Because of wrong frequencies all Sat>Ip calls are rejected then with 403: Forbidden.
Do you have the Netstream 4C or Netstream 4Sat?
Marti
Updated by Marti McFly over 6 years ago
Looking at the software I guess, that you have the 4C?
Btw. Where have you got your firmware image from? And does Sat>Ip work with your box?
Updated by Marti McFly over 6 years ago
References:
https://www.synology-forum.de/showthread.html?37898-tvstreamrecord-Aufzeichnen-von-HTTP-Streams/page81&p=623304&viewfull=1#post623304
https://forum.dvblogic.com/viewtopic.php?f=57&t=30188&p=112862#p112560
https://www.dvbviewer.tv/forum/topic/57391-elgato-eyetv-netstream-4c-dvb-c/#entry446116
http://www.hifi-forum.de/viewthread-258-2876.html
http://ipfelgruen.de/forum/hardware/peripherie/tv-karten-tuner-und-empfänger/2267-netstream-4c-expertmode/
Updated by Marti McFly over 6 years ago
Marti McFly wrote:
References:
https://www.synology-forum.de/showthread.html?37898-tvstreamrecord-Aufzeichnen-von-HTTP-Streams/page81&p=623304&viewfull=1#post623304
https://forum.dvblogic.com/viewtopic.php?f=57&t=30188&p=112862#p112560
https://www.dvbviewer.tv/forum/topic/57391-elgato-eyetv-netstream-4c-dvb-c/#entry446116
http://www.hifi-forum.de/viewthread-258-2876.html
http://ipfelgruen.de/forum/hardware/peripherie/tv-karten-tuner-und-empfänger/2267-netstream-4c-expertmode/
Updated by saen acro over 6 years ago
Marti McFly wrote:
Tombea is the so called firmware. It provides all the services.
Marti
Firmware is ALL software ex. copy of your hard disc with installed operating system.
Tombea is streamer, it is a program nothing more but it is not Open Source.
If cross-compile SatIP-AXE, SATPI or MiniSatIP
and replace Tombea, it will work with same success.
Updated by Marti McFly over 6 years ago
- File 5a51180164b56_EyeTV4C.thumb.jpg.fbf5d2472cc99b4214f127619e760f24.jpg 5a51180164b56_EyeTV4C.thumb.jpg.fbf5d2472cc99b4214f127619e760f24.jpg added
Of corse your right with the definition of Firmware. I wouldn't name Tombea firmware myself. I'm sceptical if anything else, except Tombea, is replaced among the firmware releases.
What I tried to say is, that Geniatech use to call it firmware in eyetv... https://eyetvforum.com/index.php?/topic/2067-no-firmware-update/&tab=comments#comment-3413
Have you crosscompiled SatIP-AXE, SATPI or MiniSatIP for the Netstream 4c without success, is this what you try to say?
Updated by saen acro over 6 years ago
Inside opensource archive there is file arc_gcc_rel4.4.tar.gz
with include cross-compile environment.
But am not good in cross-compilations
if some one is good lets write and help with "alternative firmware" based on SatIP-AXE, SATPI or MiniSatIP whi not TVHeadend directly.
As I see both usb ports are 100% working, but not loaded in kernel and in software used. /DVR or NVR maby/
Also transcoding option is interesting /there is a lot of ready profiles/
Updated by Marti McFly over 6 years ago
Would you like to answere my questions? - Those sentences ending with questionsmarks (?) ...
Do you have the Netstream 4C or Netstream 4Sat?
Where have you got your firmware image from? And does Sat>Ip work with your box?
It feels more like TVHeadend expects things in a certain way, even it's not made that way.
Updated by Chris master over 6 years ago
the best solution is to sell this shit netstream Box
Buy HD Homerun this works perfekt with tvheadend
Updated by saen acro over 6 years ago
Chris master wrote:
the best solution is to sell this shit netstream Box
Buy HD Homerun this works perfekt with tvheadend
quad PCI tuner cost less and work 1000 times better
Updated by saen acro over 6 years ago
There is a working team on Platform used in this Netsteram device
https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain
maby some one will agree to build clean linux with dvb support + network,
and some streaming software
Updated by Marti McFly over 6 years ago
Well, HD Homerun wouldn't be supported without an issue from which someone decided to implement sat>Ip in tvheadend.
As you can see DVBViewer, VLC, Eytv is able to view everything from the netstream. And the Standard tells about more then one way of doing Sat>Ip.
So I guess things are more like the DVBViewer developer tells on his forum: You can't relay on dedicated tuners. And you have to be open to do http for control and rtsp for stream.
Now ssdp works. Netstream is shown in TVH. Streaming works for VLC. The URL is known. Now it's time to find a way to make it work in tvheadend.
Maybe it's possible to return to a constructive and solution orientated conversation?
Updated by Chris master over 6 years ago
a quad PCI Card is a good solution, but i use tvheadend in a virtual machine so cant use a pci card.
i use SiliconDust HDHomeRun EXPAND 4-Tuner DVB-C and this works very fine with tvheadend. i dont need firmware cracks or somethin else
Updated by Chris master over 6 years ago
Marti McFly wrote:
Related:
https://tvheadend.org/boards/5/topics/19900?r=26279#message-26279
https://tvheadend.org/boards/5/topics/16084
you can rest the firmware in EyeTV Netstream 4C and tvheadend show this tuner in the list but you can not watch channels.
its better to use a device that is supportet from tvheadend without any factory resets
Updated by saen acro over 6 years ago
Chris master wrote:
a quad PCI Card is a good solution, but i use tvheadend in a virtual machine so cant use a pci card.
i use SiliconDust HDHomeRun EXPAND 4-Tuner DVB-C and this works very fine with tvheadend. i dont need firmware cracks or somethin else
This cost more then pc quad tuner and simple mobo 512mb ram and 8gb usb disk and laptop PSU
I personaly use my very old OCTAGON SF1028P with stream from 2 tuners
p.s.
SatIP-AXE is based exactly on firmware hack.
Marti Martz McFly
Why not make playlist and add it to TVH?
I hope your operator dont change parameters daily.
Updated by Marti McFly over 6 years ago
Guys, this issue isn't about buying another stuff or finding better alternatives. It's about making the Netstream 4C work.
I've done the buying decision for good reasons! Hardware-Transcoding, 4 tuners, small power conusmption and small price are good reasons for that device. The support seriously tries to help me with that box. I'm not going to change my view on this.
From my developers view I just think that tvheadend has to learn to handle this sort of satip protocol. As you can read in above references, even TVs (Panasonic) are able to work with this device.
@saen: I thought about playlist. This would work, but adds a lot of overhead. Indeed my provider changes its frequencies quiet often.
Marti
Updated by Marti McFly over 6 years ago
I found the post about the tuner selection in the DVBViewer forum...
That's the problem. fe=1 (frontend = 1) selects the first tuner in the RS device list. According to your svchardware.xml it's a DVB-C tuner (Astrometa), so DVB-T2 can't work. The client should omit the fe parameter and leave the tuner selection to the server. See Sat>IP specifications 1.2.2, appendix A1.1
...
TVH should not set the fe= parameter at all.
If a user really needs to define a exact tuner. They could offer a special expert setting. Whether a user could set the tuner number. But it should be clear that ist should not be set unless the user knows exactly what he is doing and why.
...
It should be configurable for special purpose, but it should not be the default. That's clearly a bad idea. The default should be no frontend assignment as stated in the Sat>IP specifications (see my post above).
...
#4016 is just a questionable work-around. It must be considered that the RS handles request -> tuner assignnments dynamically. If you have two DVB-T tuners and the first one is occupied by a recording or another streaming client, the RS will automatically use the second one. This feature is spoiled by using the fe parameter unnecessarily. And it spoils similar features in other Sat>IP servers as well. If the RS has started a DVB-T recording, it will reject TVH as client, because it stubbornly insists on a particular tuner that is occupied.
https://www.dvbviewer.tv/forum/topic/58808-cannot-connect-to-rs-using-satip/?tab=comments#comment-452147
https://tvheadend.org/issues/4016
Updated by Marti McFly over 6 years ago
From the specification...
http://www.satip.info/sites/satip/files/resource/satip_specification_version_1_2_2.pdf
Binding to a particular frontend
SAT>IP servers mostly provide several frontends. A client should generally let the server automatically select a frontend. It does this by notincluding the “fe” parameter in its requests.Clients can however provide an option in the settings menu for specifying a fixed frontend in their requests. This allows a client to get access to a dedicated frontend resource. In a controlled network environment it thus becomes possible to associate guaranteed tuning resources (servers and frontends) to each and every client.
Updated by Marti McFly over 6 years ago
Now everything makes sense for me. Geniatech Netstream 4C implemented the Sat>Ip spec right. Sat>Ip wants special parameters for DVB-S/S2/C/C2. Like specinv has to be passed for DVB-C.
Appentix D
Spectrum inversion
specinv
Spectrum inversion.
Set to “0” (spectrum inversion off) or “1” (spectrum inversion on)
DVB-C only
specinv=0
Example DVB-C Query:
rtsp://192.168.128.5/?freq=623.25&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,50,201,301
Example DVB-C2 Query
rtsp://192.168.128.5/?freq=793.982&bw=8&msys=dvbc2&c2tft=0&ds=0&plp=0&pids=0,16,100,308,25
Updated by saen acro over 6 years ago
Is device support this M3U playlist in rtmp and multicast as in examples from spec.
Multicast example is nice and easy to implement in Tvheadend
Updated by Marti McFly over 6 years ago
M3U could be an answere. But M3U is optional and the netstream does not mention m3u in its description.xml.
To which part of the spec do you refer with multicast...?
Updated by saen acro over 6 years ago
Marti McFly wrote:
M3U could be an answere. But M3U is optional and the netstream does not mention m3u in its description.xml.
To which part of the spec do you refer with multicast...?
http://www.satip.info/sites/satip/files/resource/satip_specification_version_1_2_2.pdf
see nearly at the end
Updated by Marti McFly over 6 years ago
- File adaptersettings.png adaptersettings.png added
With very small changes I made the Netstream 4c work with tvheadend. I'm impressed so far!
As I mentioned, the sat>ip specification recommends letting the sat>ip device select the frontend. In consequence, the Netstream 4c does not support the frontend/tuner selection and reports errorno 505 in case tvh tries to pass the frontend parameter.
I'd appreciate a checkbox in the tvh-adapter configuration, which could be named like "Disable fe (frontend) selection" or "FE supported". This should disable the "fe="-parameter in rtsp protocol.
The „fe=“-parameter is used to adress the frontend/tuner. Since tvh won't adress more then 4 tuners anyway, I don't think it's going to be a problem to remove the parameter. Except you'll use up all 4 tuners by another device. But even then tvh just won't be able to use the occupied tuners and reports a simple message.
Next missing thing is the "specinv=0" parameter for dvb-c devices. This has to be passed by tvheadend to dvb-c devices. Without this, the Netstream 4C does not accept the connection.
Practically spoken:
For proof of concept I changed two rows in tvh sourcecode. Please find it in my fork on github. To make it run just compile the master as you're used to.
https://github.com/mpietruschka/tvheadend
Since the Netstream 4C does not do service announcement by itself, you've got two options to make TVHeadend recognize it.
1. Pass the sat>ip description to tvheadend manually
--satip_xml http://IPADDRESSOFNETSTREAM:81/description.xml
2. Enable sat>ip service announcement on the Netstream 4C.
Connect to the Netstream 4C
#> ssh [email protected]
password: service
Kill the streaming deamon, give it 30 seconds to finish and run it with ssdp (Simple Service Discovery Protocol) turned on. Please keep in mind, that the official IOS and Android apps won't find it with this option turned on.
#> killall Tombea
#> Tombea -i 1 --no-alternate-discovery
Once after you've made tvheadend find the device, it remembers the netstream 4Cs IP and you won't have to enable ssdp again.
Please find the tuner options in the attached screenshots.
Have fun!
Reference
http://urup.net/?tag=netstream-4c
Updated by Marti McFly over 6 years ago
because it got truncated...
ssh root [at] ipadressofnetstream4c
Updated by Marti McFly over 6 years ago
fixed with this pull requests
https://github.com/tvheadend/tvheadend/pull/1139
https://github.com/tvheadend/tvheadend/pull/1137
Updated by Marti McFly about 3 years ago
Lately I've googled this topic and figured out, that someone has explained how to upgrade to 402r1 on the Geniatec-Forum.
You can extract the .dmg-file with 7-zip or open it directly on MacOs.