Re: [VANILLA-LIST:2361] UDP -> TCP -> UDP = Ghostbust forced quit.

[Dave Ahn <ahn@vec.wfubmc.edu>]

On Wed, Jun 16, 1999 at 11:34:22AM -0400, Dave Ahn wrote:
> On Wed, Jun 16, 1999 at 03:32:10AM +0000, James Cameron wrote:
> > If you are in UDP mode, force reset to TCP, and then select UDP again,
> > you get ghostbusted; the reconnect works, but RSA reverification fails,
> > and you can only quit.
> 
> Does this happen on the older servers (2.9pl2) before the recent changes
> to the networking code?

Answering my own question, no it does not.  mit.netrek.org uses an earlier
version of the networking code, and I'm able to switch back and forth
without problems.

When I connect to anx or pickled, I'm able to switch, but switching from
UDP->TCP->UDP puts me in a state where only TCP messages seem to reach
the server.  That is, I'm able to send distresses, but I can't control
the ship (move, fire, etc).  Given enough switching back and forth from
TCP<->UDP, I eventually do get a ghostbust with:

Tried to write 7, 0x7fff2a00, 12
write: Destination address required
gwrite failed.
Whoops!  We've been ghostbusted!
Pray for a miracle!
Waiting for connection (port 18752). 

Once, I also got this without a ghostbust:
Tried to write 7, 0x7fff2b40, 4
write: Connection refused

I have pinpointed the problem to the UDP_PORTSWAP code in the server and
will take a closer look at it tonight.

-- 
Dave Ahn <ahn@vec.wfubmc.edu>        |  "When you were born, you cried and the
                                     |  world rejoiced.  Try to live your life
Virtual Endoscopy Center             |  so that when you die, you will rejoice
Wake Forest Univ. School of Medicine |  and the world will cry."  -1/2 jj^2