Chad, stupid question, but, is the time set right in the receiver after you did the firmware update?
Chad, stupid question, but, is the time set right in the receiver after you did the firmware update?
I see samba is running on port 139.
I set timers with my external USB drive as default, but the timers no longer works after updating the firmware to the latest version when trying to record using timers to the external USB, but it will record manually. I can read and play everything I previously recorded from that drive with the media player, just doesn't work with the timers. But the timers works fine recording to the internal USB drive. Any ideas? I haven't tried the front USB port...
Not really sure, as I don't do much timer recording, but I've been updating the firmware every time a new one is available, so it must have been 1213. The last shows I recorded with timers was in October...What was the last know software version that would timer record for you? I'm pretty sure it was working just fine for me using 1152 firmware version. Can't get it to schedule record a thing using 1213 or 1248 software.
Hi Fred. Yeah that does work.
That is so.That's cool, so you can copy recordings off the box over the network then? If so that is a pretty useful feature.
The streaming is supported and installed. The streaming works via the remote application in Android and iOS - application is called VIVANT remote. But because it did not work flawlessly, we do not offer it as supported option.Hi Fred. Yeah that does work. I found the samba config will paste below. Basically no password read write share which shares out /mnt where all your external drives mount. Its samba version 2.2.12 which was released in 2004. Appears that most config files as well as the database are located in /home/stb. Some logs are in /tmp. Pretty straight forward layout. From the logs I see that DNLA isnt starting due to missing files or config which is why I dont see the box broadcast DNLA even though there is a DNLA setting in the firmware. I also pulled out of the init files that the busybox/development environment is:
# This file auto create by makefile
echo "Compile file system used arm-hisiv200-linux-"
If you search for arm-hisiv200-linux you get this site (and probably others) which are maybe some clues on how the OS was built for this box: http://sourceforge.net/projects/ath.arris/files/HMC3000/
I think thats the build environment where you could probably build/compile your own apps for the box to run. I only looked quickly.
Here is the samba config (the one for wireless) there is another config for if you are using the LAN adapter instead which just runs smbd on the Lan interface instead:
[global]
interfaces = wlan0
workgroup = MYGROUP
server string = Samba
netbios name = myarm
guest account= root
security = share
[share]
path =/mnt
writeable = yes
guest ok= yes
browseable= yes
Well Ive found no info on any support for streaming just a framework there where the capabilities were started just never hooked up on the back end under the hood to anything. I dont know much about the dvb process that seems to run on the box. When watching PBS East HD on 125west the dvb process takes 30% cpu on average and 30% of the ram. I think this is a great improvement in the latest version. The GUI on the box seems a lot more responsive. I noticed the kernel is newer too. As this box is polished except for the lower cpu and ram specs to me its been the holy grail of features for satellite viewing. NTP/time update, promising dvr features, channel edits from the gui, ACM/Music choice support, sensitive tuner able to tune the lowest symbol rates down to 973 symbols and lower (the NPR feeds on 99west) on my non ppl LNBF, extensive features. I am really enjoying this box. Id like to see this firmware on a box with twice (or more) the power and triple+ the ram with the exact same amazing tuner in the future.
Just a dump of an hour digging deeper into the unit.
Please watchI was wondering if there is a way to stream channels from this box or control it via the network. I did an nmap on the unit and found the following tcp ports open:
nmap 10.20.150.214
Starting Nmap 6.40 ( http://nmap.org ) at 2015-12-01 20:47 EST
Nmap scan report for 10.20.150.214
Host is up (0.048s latency).
Not shown: 991 closed ports
PORT STATE SERVICE
23/tcp open telnet
80/tcp open http
139/tcp open netbios-ssn
554/tcp open rtsp
3000/tcp open ppp
49152/tcp open unknown
49153/tcp open unknown
49154/tcp open unknown
49155/tcp open unknown
I then telnet'd to the box and as explained earlier in this thread there is a whole busybox shell/environment. Looks like there is an rstp port running on port 554? the dvr process is the process running on port 80 (and others). Tried connecting to port 80 at the ip of my satbox but chrome just spins. Is there a special URL I need to feed to VLC to stream. I see samba is running on port 139. Can you connect to this box like a windows share? Ill play more but any tips would be great.
The streaming is supported and installed. The streaming works via the remote application in Android and iOS - application is called VIVANT remote. But because it did not work flawlessly, we do not offer it as supported option.