- This topic has 2 replies, 1 voice, and was last updated 17 years, 6 months ago by
.
-
Posts
-
Maybe someone else can help with this – I’m stumped at this point. Here’s what I’ve done so far:
Installed Firefly svn-1586 on an nslu2 at home. From within the home network everything works just dandy. I can connect with iTunes, Rhythmbox, and XBMC.
At work I am unable to get connected via my SSH tunnel. Here’s how I’m doing it:
ssh -L 3689:localhost:3689 my.nslu2box.com
From here I can see the web-based control panel at work by browsing to http://localhost:3689. So far so good. I run this command to advertise daap to my local machine:
avahi-publish-address -v -H gecko.local -s “sluggo” _daap._tcp. 3689
Now I can actually see the share called “sluggo” in my shared music area in Banshee. But clicking on the share does nothing – it just sits there and says “Connecting to sluggo” . . .
Rhythmbox won’t recognize the daap share at all.
What am I doing wrong here? I’m used to port forwarding “just working” as if the service were running on localhost. Is there some missing piece of the puzzle that is not allowing banshee or rhythmbox to connect to the daap server?
It appears that what was missing is the -g flag on my SSH command. When I do this:
ssh -L 3689:localhost:3689 my.nslu2box.com -g
Then banshee is able to connect to mt-daap via the ssh tunnel. I do get these errors while it’s starting up in the server logs but it seems to work now:
2007-05-22 13:47:09 (031ec004): Thread 3192: could not read: Success
2007-05-22 13:47:10 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:11 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:34 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:34 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:36 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:38 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:42 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:43 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:45 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:46 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:47 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:49 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:51 (031f0004): Thread 3193: Bad arg:
2007-05-22 13:47:51 (031f0004): Thread 3193: Bad arg:I have modified this a bit so that the localhost port is 9999. So my new configuration is as follows. Since I couldn’t ever get the /etc/avahi/services/mt-daap.service file working correctly I put this in my Gnome startup session commands:
avahi-publish -s -v -H gecko.local “sluggo” _daap._tcp. 9999
Then I fire up a tunnel to the slug:
ssh -g -L 9999:localhost:3689 sluggo
This works ok now, but my next question is, how do I tell Avahi not to advertise this daap share to the whole network? What if I just want to keep it on my local computer?
- The forum ‘Setup Issues’ is closed to new topics and replies.