Stream to a remote iTunes

Viewing 10 posts - 1 through 10 (of 13 total)
  • Author
    Posts
  • #1826
    Iris
    Participant

    I’ve had a request from my son who’s away at University – he’s asked me to see if I can set-up our home music server so he can access it from iTunes like he did when he was at home.

    He’s running XP and I’ve installed iTunes at work for purposes of testing the set-up. Up until now I’ve had no reason to use iTunes or access our music server remotely for that matter so I must admit this is rather new to me. Anyways, I know that I want to use a SSH tunnel for security reasons and that whatever add’l software I need to use has to run on my NAS. I have the ability to configure whatever ports at home and at work and I’m hoping this won’t be an issue for him after I get things working on my end.

    I’ve tried adapting a few “how to’s” to my set-up but no success. And, I haven’t been able to find anything via Google on how to stream from a NAS to a machine running XP. Lot’s for Mac’s!

    My signature contains the details of my set-up at home. I just either need a friendly push in the right direction or some hand holding to get this running. I also realize that I may be out of luck or because of what I’ve read I might be over doing it and that’s why I can’t get it to work.

    So, please help if you can.

    Iris πŸ˜•

    #12952
    rpedde
    Participant

    @Iris wrote:

    I’ve tried adapting a few “how to’s” to my set-up but no success. And, I haven’t been able to find anything via Google on how to stream from a NAS to a machine running XP. Lot’s for Mac’s!

    Most of the ssh tunneling stuff is applicable, just using different applications.

    Still the general idea is that you ssh into your home network and set it up such that connections to port 3689 on the ‘road-warrior’ pc are tunneled through the ssh connection to port 3689 on the daap server.

    With a unix or osx machine as the road-warrior, you do that with:

    ssh [email protected] -L 3689:internal.mt-daapd.ip:3689

    You’ve seen that on the faqs before.

    You can do the same thing with putty. Download putty and there is a section for tunnels. Set you local 3689 to connect to 3689 on the mt-daapd server.

    ssh in, and you should be able (from the road-warrior machine) to do http://localhost:3689 and be in the admin web pages.

    If so, then that’s half the battle.

    Next up, you’ll need to install rendezvous proxy (http://ileech.sourceforge.net/index.php?content=RendezvousProxy-Download), and set it up to advertise _daap._tcp on 3689 for 127.0.0.1.

    It should show up iTunes, and you should be in business.

    Of course, the next problem is upstream bandwidth…

    — Ron

    #12953
    Iris
    Participant

    Thanks Ron.

    I have both PuTTy and Rendezvous Proxy – I had the proxy at work configured wrong for one and I’ll fix that tomorrow. And, I have PuTTy but didn’t even think of using that 😳 – so use to using it just for Telnet.

    My upload is 916 Kb/s so I think that should be okay – only testing will tell.

    I read about opening up port 22 for SSH on my home router – is that still valid? If so, then I imagine the same would need to be done at work?

    Anyways, I’m anxious to try this out tomorrow.

    Iris πŸ™‚

    #12954
    rpedde
    Participant

    @Iris wrote:

    Thanks Ron.

    I have both PuTTy and Rendezvous Proxy – I had the proxy at work configured wrong for one and I’ll fix that tomorrow. And, I have PuTTy but didn’t even think of using that 😳 – so use to using it just for Telnet.

    My upload is 916 Kb/s so I think that should be okay – only testing will tell.

    I read about opening up port 22 for SSH on my home router – is that still valid? If so, then I imagine the same would need to be done at work?

    Anyways, I’m anxious to try this out tomorrow.

    Iris πŸ™‚

    wrt port 22, that’s correct. The way I have it working (at home) is my router I have configured to port forward from port 22 on the router itself to port 22 on my mt-daapd server. On that machine, I also register an address with dyndns, so I have a “myhouse.dyndns.org” or whatever that I can ssh to, and that connects to the front side of my router, which forwards to the linux machine that runs my mt-daapd server.

    If I ssh with -L 3689:localhost:3689, that connects 3689 on my work machine to 3689 on the mt-daapd machine (which is localhost, from the perspective of the machine running the ssh server). If that makes sense.

    Oh.. that’s a good point too… you have to have a ssh server in there somewhere as well to connect into. Didn’t think about that. If you are running mt-daapd on a mac or linux box, that’s a good candidate.

    — Ron

    #12955
    Iris
    Participant

    Well, of course nothing goes smoothly.

    As far as I could tell I had neither Dropbear or OpenSSH installed on the NAS. No problem, however, it seems that trying to install add’l packages never goes smoothly. For instance, ipkg install OpenSSH yields:

    # ipkg install openssh
    Installing openssh (4.7p1-1) to root...
    Downloading http://ftp.osuosl.org/pub/nslu2/feeds/optware/mss/cross/unstable/ope nssh_4.7p1-1_mipsel.ipk
    Configuring openssh

    Generating RSA Key...
    /opt/bin/ssh-keygen: error while loading shared libraries: cannot open shared object file: cannot load shared object file: No such file or directory
    Generating RSA Key...
    /opt/bin/ssh-keygen: error while loading shared libraries: cannot open shared object file: cannot load shared object file: No such file or directory
    Generating DSA Key...
    /opt/bin/ssh-keygen: error while loading shared libraries: cannot open shared object file: cannot load shared object file: No such file or directory
    mkdir: Cannot create directory `/root': Operation not permitted
    Fixing permissions on the /tmp directory...
    killall: sshd: no process killed
    /opt/sbin/sshd: error while loading shared libraries: cannot open shared object file: cannot load shared object file: No such file or directory
    postinst script returned status 127
    ERROR: openssh.postinst returned 127

    That’s the problem sometimes with following a “How To” verbatim. One may get whatever their working on to run without fully understanding what’s happening then one get these errors and your hooped!

    I guess I’ll be reading… reading…

    Iris πŸ™„

    #12956
    Iris
    Participant

    Someone save me from having to create another user id on another forum in order get some assistance for this slightly off-topic request.

    I’ve searched and read probably 30 different articles and nothing specific has mentioned how to diagnose the errors I’m getting above. So, considering this is the only forum that I belong to that probably has more members using linux and that what I’m trying to do is related to acessing FF I hope I can get help.

    I googled:

    error while loading shared libraries: cannot open shared object file: cannot load shared object file

    To see if I could find any solutions but there either nonsense or don’t help. OpenSSH is up-to-date accroding to ipkg install openssh it’s just that it doesn’t finish the configuration. ALL the files that it says it can’t open or find are there. I’m stumped. I even tried different sources for the package and got the same error. Is this perhaps related to a user privelege or something. I’m just telneting into my MSS w/o a p/w and executing the commands – seem thing I’ve done to install FF, etc.

    Iris

    #12957
    fizze
    Participant

    You sure that you run that all as root?
    tried to reboot the slug?

    Did you run ipkg update / ipkg upgrade?

    Tried to run ipkg with more verbosive error messages?

    I guess you lack some deps, or some deps are not met with the proper version.

    Strangely enough though, I never had any problems at all running ipkg install openssh on a fresh unsling slug.
    πŸ™„

    #12958
    Denis
    Participant

    Hi

    Today I ported my compression patch to svn-1676 (nightly build)

    you can grab the complete files here:

    http://denisy.dyndns.org/out-daap.c
    http://denisy.dyndns.org/out-daap.h

    here some log output:

    2007-10-19 01:08:45 (28605100): Using compression: /databases
    2007-10-19 01:08:45 (28605100): Uncompressed size: 10042599
    2007-10-19 01:08:51 (28605100): size after gzip: 1196535 with level: 6
    2007-10-19 01:08:51 (28605100): Compression ratio: 0.119146

    With the patch you only need to enable compress in the configfile!

    Denis

    PS: made this patch under FreeBSD, I hope it works
    for other OSs as well.

    #12959
    Iris
    Participant

    @fizze wrote:

    You sure that you run that all as root?
    tried to reboot the slug?

    Did you run ipkg update / ipkg upgrade?

    Tried to run ipkg with more verbosive error messages?

    I guess you lack some deps, or some deps are not met with the proper version.

    Strangely enough though, I never had any problems at all running ipkg install openssh on a fresh unsling slug.
    πŸ™„

    Yes Yes and Yes

    The only thing that I gleaned from the verbose message is that the files contained no MD5SUms. I even tried installing an older version.

    #12960
    rpedde
    Participant

    @Iris wrote:

    @fizze wrote:

    You sure that you run that all as root?
    tried to reboot the slug?

    Did you run ipkg update / ipkg upgrade?

    Tried to run ipkg with more verbosive error messages?

    I guess you lack some deps, or some deps are not met with the proper version.

    Strangely enough though, I never had any problems at all running ipkg install openssh on a fresh unsling slug.
    πŸ™„

    Yes Yes and Yes

    The only thing that I gleaned from the verbose message is that the files contained no MD5SUms. I even tried installing an older version.

    I’m assuming this is an mss. The mss’ are kind of funky because there apparently isn’t a fully compatible build system. The libraries and stuff from unslung are incompatible with the files on the mss. Not sure why, but it makes it really hard to work on the mss. Too bad, because it would be my first choice as a nas if it weren’t for that situation.

    You can try setting your LD_LIBRARY_PATH to /opt/lib and your path to put /opt/bin and /opt/sbin/ first:


    # export LD_LIBRARY_PATH=/opt/lib
    # export PATH=/opt/bin:/opt/sbin:$PATH
    # ipkg install openssh

    That might do it.

Viewing 10 posts - 1 through 10 (of 13 total)
  • The forum ‘General Discussion’ is closed to new topics and replies.