DSM-G600, DNS-3xx and NSA-220 Hack Forum

Hello,

  This is my first post and sorry for my poor english
  I just get my DNS 323 (just before christmass
  I just installed it (fun_plug is ok) and now my first soft to install is Twonky,
  I'm going to download it, but surprise the Twonky 5.0 is now released, yes that's cool I can get the latest version, good news
  But problem, I didn't find the link to download it for my DNS 323

  Is there someone who can help me to find the correct link? I have the same problem than "Diskotekno"
  Or do you think that the DNS 323 is no more supported
  This would be a big deception as bought it to use Twonky

Please help me
Pascal

Sorry I dont have a direct download but have uploaded a zipped copy of my 4.4.9 DNS 323 install if you want to try to my blueyonder / virgin media web hosting

http://net2005.myby.co.uk/twonkymedia/t … -4.4.9.zip

Ahodgey

Thanks to ahodgey and Diskotekno

I downloaded th 4.4.9, just installed it and it works with no difficulty
It is very easy,
Thank you again and Merry Christmass

TiPasFou

Cheers for the 4.4.9 software upload!

one question, does this work on a dns-343?
I disabled UPnP AV server, enabled telnet, and ran the nassetup.exe, and it said everything installed correctly and that the server was started...
but, no twonkymedia process is running, I can't connect to http://192.168.1.1:9000/configpage/index.html , and trying to run the script manually throws the error below

root@NAS:~# /mnt/HD_a2/starttwonky.sh
route: SIOCADDRT: File exists
root@NAS:~# /mnt/HD_a2/starttwonky.sh: /mnt/HD_a2/twonky/twonkymedia: No such file or directory

root@NAS:~# ls /mnt/HD_a2/twonky/
cgi-bin                       twonkymedia-default.ini
plugins                       twonkymediaserver
resources                     twonkyvision-mediaserver.ini
twonkymedia

as you can see, the file exists, and ps returns nothing

root@NAS:~# ps | grep twonky
18015 root     grep twonky

a netstat also shows no services running on port 9000, so the server definitely isn't running...just not sure why.

root@NAS:~# netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:9091            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:http            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:54129           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:51413           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:telnet          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN
udp        0      0 NAS:137                 0.0.0.0:*
udp        0      0 0.0.0.0:137             0.0.0.0:*
udp        0      0 NAS:138                 0.0.0.0:*
udp        0      0 0.0.0.0:138             0.0.0.0:*
udp        0      0 ALL-SYSTEMS.MCAST.NET:13579 0.0.0.0:*                       
udp        0      0 0.0.0.0:5353            0.0.0.0:*
udp        0      0 NAS:1900                0.0.0.0:*
udp        0      0 0.0.0.0:1900            0.0.0.0:*
udp        0      0 NAS:1906                0.0.0.0:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node Path

anyone able to offer any assistance?

DNS-313 cpu is:

Processor       : FA526id(wb) rev 1 (v4l)
BogoMIPS        : 230.19
Features        : swp half
CPU implementer : 0×66
CPU architecture: 4
CPU variant     : 0×0
CPU part        : 0×526
CPU revision    : 1

While DNS-323 cpu is an ARM926EJ-Sid. I don't think you'll run the ARM binaries on the DNS-313

However the DNS-343 *does* have an ARM processor (the same as the DNS-323), but I don't know if the system installed is the same. Check that your system binaries type and the twonkymedia's binaries look the same:

# file /bin/busybox
/bin/busybox: ELF 32-bit LSB executable, ARM, version 1, dynamically linked (uses shared libs), stripped
# file /mnt/HD_a2/twonky/twonkymedia
/mnt/HD_a2/twonky/twonkymedia: ELF 32-bit LSB executable, ARM, version 1, dynamically linked (uses shared libs), stripped

And that all required libraries are installed:

# ldd /mnt/HD_a2/twonky/twonkymedia
ldd: can't open cache '/ffp/etc/ld.so.cache'
        libpthread.so.0 => /lib/libpthread.so.0 (0x4000d000)
        libc.so.0 => /lib/libc.so.0 (0x40028000)
        ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x40000000)

Hope this helps.

root@NAS:/# file /bin/busybox
/bin/busybox: ELF 32-bit LSB executable, ARM, version 1, for GNU/Linux 2.4.3, dynamically linked (uses shared libs), stripped
root@NAS:/# file /mnt/HD_a2/twonky/twonkymedia
/mnt/HD_a2/twonky/twonkymedia: ELF 32-bit LSB executable, ARM, version 1, dynamically linked (uses shared libs), stripped

the only thing I can see here is the "for GNU/Linux 2.4.3", not sure if that would prevent it (twonky) from running...

root@NAS:/# ldd /mnt/HD_a2/twonky/twonkymedia
ldd: can't open cache '/ffp/etc/ld.so.cache'
checking sub-depends for '/lib/libpthread.so.0'
        libc.so.6 => /lib/libc.so.6 (0x4001e000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
checking sub-depends for '/ffp/lib/libc.so.0'
        libpthread.so.0 => /lib/libpthread.so.0 (0x00000000)
        libc.so.0 => /ffp/lib/libc.so.0 (0x00000000)
        /ffp/lib/ld-uClibc.so.0 => /ffp/lib/ld-uClibc.so.0 (0x00000000)

and here I'm fairly lost...can't see any glaring errors, but I'm not sure =/

http://www.twonkyforum.com/viewtopic.ph … 996#p22996

leka wrote:

Hi all,

I had the same issue on my DNS-313 device.

This is what I did to solve it:

1) unzip twonkymedia-dns323-4.4.11-20090108.zip (4.4.11)
2) RUN nassetup.exe
3) replace these 2 binaries with the ones included in twonkymedia-armel-glibc-2.2.5-4.4.11-20090108.zip:

(can be downloaded here: http://www.twonkyforum.com/unsupported/4.4.11/ (Linux ARM little endian glibc 2.2.5)

twonkymedia
twonkymediaserver

4) start Twonky via:

/mnt/HD_a2/starttwonky.sh


Have fun!! 

Cheers

Leka

did it all work for your Largo? Assuming it would have, as you have the same device as the person who supplied the fix - a dns313

for me, on the 343, replacing those binaries fixed the initial error, now twonky starts...well, appears to.

root@NAS:/mnt/HD_a2# ./starttwonky.sh
    route: SIOCADDRT: File exists
    root@NAS:/mnt/HD_a2# TwonkyMedia Version 4.4.11
    LOG_SYSTEM: reading ini file: "/mnt/HD_a2/twonky/twonkyvision-mediaserver.ini".

That's what happens when starttwonky.sh is run.

After that, whenever I try to access 192.168.1.1:9000, it loads a blank page (or reports page cannot be found), and the putty session returns

TwonkyMedia Version 4.4.11
    LOG_SYSTEM: reading ini file: "/mnt/HD_a2/twonky/twonkyvision-mediaserver.ini".

every time I try to access twonky via the webbrowser.
Any thoughts?

cheers,
- Klaus