azinck3 wrote:
Rob McKaughan;180061 Wrote:
Any ideas on how to do this?
I want to go over to my friend's house and have her squeezebox connect
to my server, thus being able to play and navigate my collection from
her squeezebox. The key is that I want the UI to be the squeezebox,
not the web interface. Ideally, too, I'd leave an m3u or some such to
make it easy to connect via the squeezebox UI.
It's sorta like connecting to Squeezenetwork, but it connects to my
server.
And, of course, I want to do this as securely as possible.
And a pony...
It doesn't appear that connecting to http://myhouse:9000/stream.mp3
helps because it doesn't let me navigate my collection from the
squeezebox. I want her squeezebox to appear like it's on my LAN
(unless, of course, she wants to play her own music).
The secure and good way to do this if you intend a long-term setup is
to use SSH and port forwarding (just do a search in these forums, I'm
sure someone's written a step-by-step). Doing this, however, is a
nuisance for a number of reasons...not the least of which being that it
requires that you run an SSH client on a computer on her LAN.
No, the secure and good way to do this is by using VPN technology.
SSH kind of works but is not very good at pretending to be a VPN.
The easier, unsecure way to do it (indeed, the way that I do it) is to
open port 9000 (tcp) and 3483 (tcp and udp) in your firewall and set up
port forwarding on your router for those two ports so that all incoming
requests on those ports go to your computer running slimserver. It's
only insecure in as much as 1) communication between your squeezebox
and server is unencrypted (who cares), 2) anyone who knows your ip
address could stream music from you (unlikely, but possible) and 3)
though there are no currently known exploits, it's possible that these
open ports could more readily allow a hacker to attack and access your
system.
I don't like 2) and 3) at all. This solution is perfectly fine as long
as you can use IP filtering, which is only really possible if both sides
have static IP's
The real trouble with the easy setup is that it only really works well
if the network where slimserver is located has a static global ip
address. Most home internet connections do not enjoy such a luxury.
Services like ipupdater and dyndns provide the helpful ability to
reference your home computer at any time via dns without having to know
your current IP, but the squeezebox cannot resolve named addresses. So
you might get lucky and have a static IP, or a dynamic IP that changes
infrequently enough so as to be effectively static, but odds are that
you'll have to look up your IP address every time you want to access
your collection with her squeezebox. If you want the longer-term setup
then use SSH.
Or openvpn or hamachi, which works without any party having static ip
addresses.
Regards,
Peter
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
