MegaGlest Forum

Archives (read only) => Glest Advanced Engine => Bug reports => Topic started by: tomreyn on 14 April 2011, 17:28:39

Title: [Fixed] GAE should not bind to TCP port 61357 when entering the 'New Game' menu
Post by: tomreyn on 14 April 2011, 17:28:39

When you enter the 'New Game' menu but have already something else bound to the 61357 TCP port, GAE bails out with an error:

Code: [Select]

Socket Error in : bind() [Error code: 98]
Address already in use

While the 'New Game' menu can be used to start a network game, it does not do so by default (the default seems to be a local human vs AI game), so it should not expect to be able to bind to this port. In fact, it should not do any socket operations until  the user actually opens a network player slot.

Title: Re: GAE should not try to bind to TCP port 61357 when entering the 'New Game' menu
Post by: silnarm on 15 April 2011, 06:26:25

507472d..

done.

Title: Re: [Fixed] GAE should not bind to TCP port 61357 when entering the 'New Game' menu
Post by: ultifd on 15 April 2011, 06:35:21

Thanks, I've always had this problem! I thought it was something else before.

Title: Re: [Fixed] GAE should not bind to TCP port 61357 when entering the 'New Game' menu
Post by: silnarm on 15 April 2011, 06:52:26

Quote from: ultifd on 15 April 2011, 06:35:21

Thanks, I've always had this problem! I thought it was something else before.

There was a ini setting for server port too, it wasn't 'hooked up' at all, not sure why, maybe got wiped during the network revert...  Anyway, is used now.