When I specify a proxy as server, and enter my credentials, then mudlet connects to the proxy but is not able to log in me correctly. I think it sends the wrong commands to the proxy server:
watch this screen video:
http://www.youtube.com/watch?v=xxBbNWQXn2U
edit: now swtiched youtube broadcast from private to public. sorry!
What should I do?
how to connect to MUD through proxy?
how to connect to MUD through proxy?
Last edited by gurke111 on Fri May 01, 2009 1:58 pm, edited 1 time in total.
Re: how to connect to MUD through proxy?
I need more info on the type of proxy you are using?
The video link doesnt work.
The video link doesnt work.
Re: how to connect to MUD through proxy?
Seems to be something "homegrown":
Dr.Globus(tm) [to you]: I can show you the source code if you like, but I think it's just a matter of sending "connect username password" instead of "@connect username password" to initiate a session
edit: hmm I am confused.. sorry. Could you please delete the other thread?
Dr.Globus(tm) [to you]: I can show you the source code if you like, but I think it's just a matter of sending "connect username password" instead of "@connect username password" to initiate a session
edit: hmm I am confused.. sorry. Could you please delete the other thread?
Re: how to connect to MUD through proxy?
Okay, now I have more information for you:
1) the video link in my first post now should work
2) I specified dummy credentials: USERNAME and PASSWORD, then connected:
1) the video link in my first post now should work
2) I specified dummy credentials: USERNAME and PASSWORD, then connected:
Then I typed the login command manually:Welcome to the proxy server for Waterfall Glen
Invalid command <USERNAME>
Invalid command <PASSWORD>
but it even returns an error msg:connect user pass
It should say "connection refused" because of bad login data... whats wrong here?Invalid command <connect user pass>
Re: how to connect to MUD through proxy?
The issue has been fixed. Your proxy seems to be a really broken custom version
The problem was that Mudlet sends a couple of telnet init sequences to haggle certain options with the server, but your server got completely confused.
Mudlet doesn't start up the telnet negotiation anymore and your proxy works.
The problem was that Mudlet sends a couple of telnet init sequences to haggle certain options with the server, but your server got completely confused.
Mudlet doesn't start up the telnet negotiation anymore and your proxy works.