Recent Changes - Search:

Research


edit SideBar


WindowsiTunesSetup

RemoteDaapAccess

Keywords: SSH Tunneling, iTunes, mt-daapd, RendezvousProxy, PUTTY

copied from http://f5.grp.yahoofs.com/v1/EKw9QioMSh2AKkeq6uOSH4SEZJoM32iBJuBKM86DFpCUu0cdJxutM8PjvZ2V8FQWZb_9TKfjZxXKZacnFn2H7aa7hADv/RemoteDaapAccess/RemoteDaapAccess.htm

Goal: The aim here is to show you how to gain secure remote access to your MP3 collection stored on your NSLU. That means finally being able to listen to your favourite music at work without your admin getting upset about the 10Gigs of MP3's sitting on your hard drive (I'm not promising that he won't get upset about your bandwidth consumption)! This will be achieve by Port Forwarding across a SSH Tunnel. Although this guide is for Windows based OS it could easily be adapted for Apple Mac or Linux users, the principle remains the same.

Prerequisites:

  • Installation of Unslung (I'm currently using 3.18) - done
  • Successful installation of OpenSSH, See OpenSSH package install - done
  • Successful installation of mt-daapt, See mt-daapd package install - done

Requirements: In order to get this working your going to need the following applications, I suggest you go an download them now:

Configuration:

1. Install PUTTY and ensure that you can make a functional SSH connection to your NSLU, the OpenSSH installation guide should help you do this.

2. Configure a "Port Forwarding" session in PUTTY. The plan is to forward the local daap port 3689 (the default port used by iTunes) to your NSLU at home via a SSH Tunnel.

Putty session port forwarding

In PUTTY this can be done as follows:

Category: Session

  • Set Host Name or IP address
  • Set Port (Probably already correct at its default of 22)
  • Check Protocol is set to SSH

Category: SSH: Tunnels

  • Enter '3689' in the 'Source Port' edit box
  • Enter '127.0.0.1' in the 'Destination' edit box
  • Select the 'Local' radio button
  • Press the 'Add' Button

You should now have the entry 'L3689 127.0.0.1:3689' listed in the forwarded ports list box.

Other options that you may consider setting, but these are not necessary, are: Category: SSH:

  • Don't allocate a pseudo-terminal
  • Don't start a shell or command at all
  • Enable compression

3. Open the Tunneled SSH session that you have just created (you may want to save it first) and login. You will have to keep the PUTTY session open for as long as you want to access your music.

RendevousProxy Settings

4. Now Install RendezvousProxy and add the following host setting:

  • Enter '127.0.0.1' in the 'IP Address' edit box
  • Enter '3689' in the 'Port' edit box
  • Enter 'NSLU Daap' in the 'Host Label' edit box, or some other label of your choice
  • Select '_daap._tcp.(iTunes Host)' as the service type from the drop down

Again you will have to keep RendezvousProxy running for as long as your want access to your music collection.

5. Now install iTunes and startup.

Your shared music library will now hopefully have been detected and listed as available an available source, select it and wait. Be patient, especially if you have a large music collection your poor little slug most likely has a lot of data to transfer but sooner or later you will get a full list of music in your collection.

Select a song, play and enjoy!

NOTE: Unlike some web postings that I have seen there is no need to open/port forward 3689 on your home network, this would most likely just present a security risk. Since your tunneling through SSH the SSH port is the only one that you need opening on your network.

Known Issues: I found that with iTunes set to use the 'Large' buffer, MP3s with bit rates up to 112K bps would play fine with little to no network stalling, (your experience may be different depending on your connection type and connection conditions), once I got above 112K bps the network would start stalling getting worse with higher bit rates. If anyone knows how to increase the iTunes buffer further still or has any other suggestions, perhaps there is a buffer in PUTTY that can be increased, then let me know.

I'm not sure where the bottle neck is, perhaps its just too high a rate for the slug to shift or perhaps the load of encrypting/decrypting the data is to much?

Thanks to Turbocharged5(at)hotmail(dot)com

Edit - History - Print - Recent Changes - Search
Page last modified on May 31, 2005, at 11:25 PM EST