Zugg Software :: View topic - Forcing the client to reconnect to another ip/port

Beginner Joined: 27 Aug 2010 Posts: 25

I seem to recall connecting to a MUD years ago which put me into a waiting queue. When it was my turn to play the game, my client automatically disconnected and reconnected to another ip/port to play the actual MUD. Maybe I was hallucinating this. I make MUDs and I was trying to figure out if this was something that zMUD or CMUD was doing, if there was an old telnet protocol that could do it (I found nothing in the relevant RFC), or something else entirely. Maybe it's a Pueblo or MXP protocol? If anyone can chime in with any information, it would be greatly appreciated. I would like to set up my MUD to have a connection server, but then divert to the actual game after authentication. Unfortunately, the MUD driver I'm using has a lot number of allowed users, so I would like to offer a waiting queue if needed.

Posted: Tue Aug 21, 2018 4:48 pm

The closest thing to that I ever heard of was using an SSH tunnel, and a home machine to mask the actual port you are using when at work.
Which sounds cool, but frankly I never attempted to make use of it to offer more information on the process.

I would assume you could approximate this serverside, perhaps with a switch, and pass the connection on from the handshake to the actual game server.
But that is purely theoretical.

Newbie Joined: 25 Jul 2019 Posts: 1

yeah he is right