I assure you constable, the error is yours...
September 3, 2006 11:27 PM Subscribe
I'm trying to run soulseek through SSH tunnels to avoid a restrictive college newtork policy. It doesn't seem to be working terribly well.
I'm doing something like this:
ssh -L 2240:server.slsknet.org:2240 -R 2600:127.0.0.1:2600 -l bjorn myserver.phrontist.org
Where 2600 is the port the client is setup to accept connections on. A hole has been poked in the server's firewall accoordingly.
I appear to be able to connect to the server, and occasionally download songs, but I get a lot of "disconnected by peer" errors.
Both machines (laptop at college, server at home) are running linux (SuSE 10.1 for the laptop, debian sarge on the server). Is there a better way to do this? Some sort of real VPN solution?
I also use SSH tunnels and an HTTP proxy... but constantly messing with tunnels is kind of annoying.
I'm doing something like this:
ssh -L 2240:server.slsknet.org:2240 -R 2600:127.0.0.1:2600 -l bjorn myserver.phrontist.org
Where 2600 is the port the client is setup to accept connections on. A hole has been poked in the server's firewall accoordingly.
I appear to be able to connect to the server, and occasionally download songs, but I get a lot of "disconnected by peer" errors.
Both machines (laptop at college, server at home) are running linux (SuSE 10.1 for the laptop, debian sarge on the server). Is there a better way to do this? Some sort of real VPN solution?
I also use SSH tunnels and an HTTP proxy... but constantly messing with tunnels is kind of annoying.
You could try installing Hamachi and running it, it works very well out of the box to give you an end to end encrypted channel between computers. Once you connect the two, you should be able to use a proxy on your home computer via its Hamachi IP and get connection.
Hamachi may or may not be allowed on your network, at my school network, but you might not, if you can connect via the SSH already. Doubly Hamachi is nice because the solution you use to relay your traffic doesn't need to be encrypted, because it already is through the Hamachi net.
posted by gregschoen at 5:41 AM on September 4, 2006
Hamachi may or may not be allowed on your network, at my school network, but you might not, if you can connect via the SSH already. Doubly Hamachi is nice because the solution you use to relay your traffic doesn't need to be encrypted, because it already is through the Hamachi net.
posted by gregschoen at 5:41 AM on September 4, 2006
Quite often this kind of thing boils down to a misconfigured public IP address in the client. I don't know Soulseek specifically, but if it has a configurable public IP address, make sure it's set to myserver.phrontist.org.
posted by flabdablet at 5:43 AM on September 4, 2006
posted by flabdablet at 5:43 AM on September 4, 2006
AFAIK Hamachi is Windows-only.
posted by flabdablet at 5:43 AM on September 4, 2006
posted by flabdablet at 5:43 AM on September 4, 2006
Scroll down on the download page. Hamachi for Linux.
posted by gregschoen at 5:45 AM on September 4, 2006
posted by gregschoen at 5:45 AM on September 4, 2006
Best answer: Hi,
I don't know exactly what soulseek uses as port numbers but from what I understand:
-L 2240:server.slsknet.org:2240 forwards localport 2240 to server.slsknet.org:2240 -- which seems to be fine as you can connect to the server.
the "-R 2600:localhost:2600" exports the localport 2600 to the remote host 2600. Observer that with a default configuratio of SSH only proceses local to the remote host will be able to connect to your local port 2600. To allow other physical hosts you need "-R -g 2600:localhost:2600"
Basically, read up on the "-g" parameter, it might be what you're looking for.
posted by gadha at 11:08 AM on September 4, 2006
I don't know exactly what soulseek uses as port numbers but from what I understand:
-L 2240:server.slsknet.org:2240 forwards localport 2240 to server.slsknet.org:2240 -- which seems to be fine as you can connect to the server.
the "-R 2600:localhost:2600" exports the localport 2600 to the remote host 2600. Observer that with a default configuratio of SSH only proceses local to the remote host will be able to connect to your local port 2600. To allow other physical hosts you need "-R -g 2600:localhost:2600"
Basically, read up on the "-g" parameter, it might be what you're looking for.
posted by gadha at 11:08 AM on September 4, 2006
Response by poster: I found a solution that works for me, in case any future mefites stumble upon this:
I run Museek on the server, and the museeq client, connected through a tunnel, on my laptop. I transfer the files back from my server through sftp.
Take that network goons!
posted by phrontist at 5:32 PM on September 9, 2006
I run Museek on the server, and the museeq client, connected through a tunnel, on my laptop. I transfer the files back from my server through sftp.
Take that network goons!
posted by phrontist at 5:32 PM on September 9, 2006
« Older Where's a unique place in NY to go to and write... | Help me to get WinXP to recognise my new SATA RAID... Newer »
This thread is closed to new comments.
posted by phrontist at 11:27 PM on September 3, 2006