...also forgot to mention https port 443 is already being used for the
website on my web computer, and so is port 80... both for the website.
I don't think SSH would work then on the same port.

On Sat, Feb 25, 2012 at 8:37 PM, Patrick Schmalstig / WRRJ Radio
<xana...@gmail.com> wrote:
> The campus will not permit ANY open ports on my computer there.
>
> I do have a wireless network but it is low power and I cannot afford a
> high power network, which unfortunately I will be more than 2 miles
> away from where the web server computer will be located (probably like
> 7-10 miles away).
>
> On Sat, Feb 25, 2012 at 6:54 PM, Rob Landry <41001...@interpring.com> wrote:
>>
>>
>> On Sat, 25 Feb 2012, Patrick Schmalstig / WRRJ Radio wrote:
>>
>>> SSH connections I fear would probably also not be permitted at my
>>> college campus for fear they would think I'm either hacking a computer
>>> or using another computer to bypass their proxy.
>>
>> If you can make outbound SSH connections from your campus, you can make a
>> connection to your home machine that sets up a reverse SSH tunnel. For
>> instance, you can make port 22 on your campus machine show up as port 1100
>> on your home machine; then when your home machine wants to connect to the
>> campus one it makes a connection to localhost port 1100.
>>
>> I've been using this technioque for several months now, and while there
>> are pitfalls -- for instance, the need to reestablish the connection if
>> something breaks it -- I find it answers quite well.
>>
>> If you can't make outbound SSH connections on port 22, set your home
>> machine to accept SSH connections on port 443. That port is unlikely to be
>> blocked because it's the standard port for https.
>>
>>
>> Rob
>> _______________________________________________
>> Rivendell-dev mailing list
>> Rivendell-dev@lists.rivendellaudio.org
>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev

Reply via email to