03-19-2012, 08:47 AM
03-19-2012, 08:56 AM
Try using a web-based IRC client such as Mibbit. I think gamesurge may also have their own web client.
03-19-2012, 08:58 AM
(03-19-2012, 08:56 AM)Evil Cheese link Wrote: [ -> ]Try using a web-based IRC client such as Mibbit. I think gamesurge may also have their own web client.
mibbit is blocked too. I'll check on gamesurge
03-19-2012, 09:52 AM
It's possible that they block everything, route all http/https traffic into a content inspector.
You may find that they allow SSH traffic. Nab a copy of putty and see if you can connect to a shell, try brbuninstalling.com and see if you get a login prompt.
If you do, try bugging Ain for a shell account
You may find that they allow SSH traffic. Nab a copy of putty and see if you can connect to a shell, try brbuninstalling.com and see if you get a login prompt.
If you do, try bugging Ain for a shell account
03-19-2012, 10:49 AM
(03-19-2012, 09:52 AM)HeK link Wrote: [ -> ]It's possible that they block everything, route all http/https traffic into a content inspector.
You may find that they allow SSH traffic. Nab a copy of putty and see if you can connect to a shell, try brbuninstalling.com and see if you get a login prompt.
If you do, try bugging Ain for a shell account
Nope, no dice. Says connection refused. This is assuming I'm doing it right, which is not guaranteed.Â
03-19-2012, 11:55 AM
Sounds like 6667 and ssh are both blocked. I doubt anything will work except for http, https, possibly ftp and pop.
You will need to find a friend with either a socks proxy or a ssh shell running on port 443 which you can connect through.
Generally, content inspectors cannot look into the encrypted traffic used in https (443) unless they are using a ssl man-in-the-middle 'attack'.
The web proxy at my work does this, which is one reason why our section pays for commercial internet and separate terminals.
You will need to find a friend with either a socks proxy or a ssh shell running on port 443 which you can connect through.
Generally, content inspectors cannot look into the encrypted traffic used in https (443) unless they are using a ssl man-in-the-middle 'attack'.
The web proxy at my work does this, which is one reason why our section pays for commercial internet and separate terminals.
rumsfald
03-19-2012, 06:02 PM
Time to start bringing doughnuts for the IT guys. Mix it up with bagels now and then.
03-19-2012, 08:52 PM
No clue but since you won't be on IRC, hope you get better and can leave the hospital soon.
03-21-2012, 06:36 AM
use a proxy, or a server with a different port.