Your network at work won't allow an outbound SSH tunnel?  That is usually one of the few outbound ports that are allowed.  You could try setting your tunnel up on a different port (80), usually the firewall/proxy are not protocall specific, however they can be.  Ask your network admin (very nicely) to allow outbound SSH traffic.

On 8/5/05, sbjaerum < [EMAIL PROTECTED]> wrote:

chris Wrote:
> I personally wouldn't do this. I also use SSH to tunnel the connection,
> but my slimserver is on a linux machine.
>
> This leads interesting results, and shows you what may happen:
> http://www.google.com/search?q=intitle%3A%22welcome.to.squeezebox%22+

Unfortunately, the firewall/proxy at work does not allow ssh
connection. Anyway, I have managed to set up ssh on my slimserver.
Tested by successful tunneling from another machine on my home network.


So at the moment, my only option is to connect using http.
How effective/robust is the IP blocking feature available at Server
settings -> Security?
I guess I should only allow IP adresses matching the local network and
the domain at work.
Will the server be visible (e.g. for Google), but not allow
connections, or will the server be invisible for all IP adresses
outside the allowed range?

Steinar


--
sbjaerum
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss



--
Do meddle in the affairs of Dragons,
for you are crunchy and good with Tabasco.
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to