ISP blocked port 80,443,563...now what?
 

Couple of questions:

1) Did Rogers recently block ports 80, 443 and 563 for everyone or am I the only poor bastard that is a victim? It was fine for years until two days ago. Funny...they left SMTP port 25 open which I'm happy for.

2) My dilemma is not ports 80 or 443 as those aren't too hard to get around. My problem is port 563, because it's not an http port. I used to ssh to my box via port 563 from work as it is the only open port we seem to have. However, I can't seem to think of a workaround now that Rogers blocks 563 while my workplace still has it open. Port 563 is still allowed through the proxy at my workplace so connecting OUT from work is not the problem...it's connecting IN to my sshd box. It wouldn't be a problem to change sshd to run on port 443 instead but unfortunately Rogers blocks that too.

The only thing I can think of is finding a way to remote in using port 563 through my proxy at work to some online service which will redirect port 563 to say port 5563 to my box. Unfortunately, such a service doesn't exist...the ones that do are for ports like 25 and 80 only. Unfortunately, it MUST be port 563 (NTTPS).

The only other solution which I thought of that would probably work is the new http-tunnel which works online, but you have to pay for that.

I'm hoping there's someone smarter than me on finding a workaround to this problem ;-)

Thanks.

do you have a third box (maybe a friend or something) who could provide you with ssh forwarding to a non-blocked port on your home box?? also, is it possible for you to ask the network adminsitrator to allow you to make outbound connections to a non-blocked port at your home?? maybe if he's a nice guy he'll help you out...

Are you kidding me? This is ROGERS Highspeed we're talking about. There's no way you can negotiate with them. Although I have a "friend or something", they wouldn't let me ssh-forward anything so I don't have to ask. I was hoping for a better solution/work-around. However, I appreciate you trying.

Anyway, 3 days later and the ports are working for me again. I've no idea why but I suspect Rogers was either testing something network wide or just on my subnet. I know it wasn't my configuration because I've tried several sources outside my home and both could not connect on any of the 3 ports...however, they can today. Go figure!

Thanks,
Andrew.

notice how i said "outbound" - i was refering to your network admin at work, not your ISP...

no problem, you're welcome...

hehe, cool... i hope it was indeed a temporary thing... but if i was you i'd still try to find an alternative to use as a secondary method when they filter your ports again...

Agreed. Unfortunately, I don't see another alternative, hence the reason me posting about it here. Net admin will not open ports...whether it's Rogers or a workplace...unless maybe you're friends with the guy and even then he'd be risking a lot should anything go wrong later.

Anyway, I lost enough time finding no answer. I'll give myself a break for a while.