Proxies and Muds

Posted by Jarakin on Mon 12 May 2003 05:33 PM — 5 posts, 23,089 views.

#0
Hey all,

Wondering if any of you have any solutions to the following problem. I posted something about it before but, now I have more information. I operate on a network which has a few restrictions in place. I have been trying to connect to the MUD for a long time now, without avail. I have tried a variety of different clients and techniques but still no dice.

I have now, however obtained the address of the Proxy Server the network uses. If in the webbrowser I enter the MUD I am trying to connect to's address, it will load up and connect no problem. It shows the first mud line then repeats it because the browser gets confused i guess.That tells me that access is not restricted, right? So, what could i do to access the MUD using a Client?

Any ideas, comments or suggestions? Perhaps i need something else? Let me know.

-Jarakin
Australia Forum Administrator #1
Recent versions of MUSHclient support Socks 4/5 proxies. What you could try is set your proxy server address and port in the IP address screen of MUSHclient (try both Socks 4 and 5), leaving the MUD's address in the usual place (the upper address box).

However they may use HTTP proxying which MUSHclient doesn't support - the reason being that I thought that HTTP proxies actually interpret the HTTP commands (eg. GET and so on) which the MUD wouldn't make much sense of.
Australia #2
The HTTP CONNECT mechanism is what most http proxies support. See http://www.ietf.org/rfc/rfc2817.txt (and others, probably) for details.
Amended on Tue 13 May 2003 10:21 AM by Dave
Australia Forum Administrator #3
I see it expects something like this:

CONNECT server.example.com:80 HTTP/1.1
Host: server.example.com:80
(blank line)

Could this not be sent directly from the client? I don't know exactly how to test this as I don't have a HTTP proxy server handy. However as it seems to be straight text (unlike the Socks protocols) you should be able to do it in the "initial connect" screen.

eg. as a suggestion:


CONNECT my-mud.com:4000
Host: my-mud.com:4000

character-name
password


However I am guessing somewhat. Anyone who can get that to work please let us know.

I warn you that the proxy server may well be configured to refuse such requests, as they effectively represent quite a big security hole.
Amended on Wed 14 May 2003 04:40 AM by Nick Gammon
USA #4
If this is a corporate environment that needs a reasonable level of security, you can almost guarantee telnet services are blocked at router/firewall/ACL/(whatever else they use for security). If this is a school, odds are they have still blocked telnet services as that is what most games use and we all know they dont want ppl playing games during class. Btw, did you type in the address as an http address or as a telnet request? Yes, you can access a remote telnet port with a web browser but it wont do more than display the greeting screen and first line before the browser is unable to interpret the incoming command requests properly. If you used a telnet request from the web browser command line and could access it, odds are the network firewall is designed to exclude all 'unofficial' software. However what you described sounds like you used a standard http address instead of a telnet request to test your access to the mud. Try a telnet attempt from the browser command line and see what happens, if you can access the mud, it's an issue with the firewall restricting software, if not, telnet is blocked on your network and yer pretty much shit outa luck for playing from there.