[Fixed] GAE should not bind to TCP port 61357 when entering the 'New Game' menu

Started by tomreyn, 14 April 2011, 17:28:39

tomreyn

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

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.
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

silnarm

Glest Advanced Engine - Code Monkey

Timeline | Downloads

ultifd

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

silnarm

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.
Glest Advanced Engine - Code Monkey

Timeline | Downloads