Posterous theme by Cory Watilo

Singnet Block Port 80?

Recently, I needed to access my home network from behind some restrictive networks. The only ports that were open was 80 and 443 (SSL), oh and I almost forgot to mention its through an internal proxy only. Yeah, not just any simple proxy such as squid. This proxy have the ability to terminate SSL traffic to inspect the contents and even actively make security decisions such as blocking the site if its cert is self signed. So this is where the problem lies. I usually connect back home using HTTPS and it works fine at most places. But this time round, it doesn't let me through unless my SSL cert back home is signed by some trusted CA. Of course I'm not willing to spend hundreds of dollars to get the SSL cert signed. 

So that leave me with port 80. I changed the inbound ports to 80 and... it can't work! From what I could recall, 1 or 2 years back it was working fine back then. So could my ISP be blocking port 80? Lets find out shall we?

1screen_shot_2011-06-16_at_am_1

I've configured the NAT to forward request from port 80.

0screen_shot_2011-06-16_at_am_1
So its blocked. Lets try incrementing the port number to 81 and see what happens.

Screen_shot_2011-06-16_at_am_1

The inbound port is set to 81.

3screen_shot_2011-06-16_at_am_1
aaaand.... success!

2screen_shot_2011-06-16_at_am_1

This is really Singet (I left the first 2 octets uncensored) as you can see. I wonder is there any ISP that dosen't block port 80? A few years back, I've heard people complaining that Starhub is blocking port 80 and some of them switched over to Singnet because of that. That is also a big reason why I've stayed with Singnet for so long. Dissapointed /sigh...
| Viewed
times