Zandronum

Posted: **Sat Sep 15, 2012 8:30 pm**

Hello.

I'm using Ubuntu 10.04, and have dynamic IP (my router is Dlink dsl2600u)

Tried many ways, but my server still marked as <NO RESPONSE> in Doomseeker. I cannot join even via cmd (Client trying to join endlessly).

What I do:
1) Disabled router firewall

2) Disabled OS firewall

3) Forward TCP/UDP 10666, 10667, and other ports

4) Other network services is ok - port 10666 even worked! But cannot host Zandronum.

5) http://www.canyouseeme.org/ shows

Code: Select all

Error: I could not see your service on 46.159.80.255 on port (10666)
Reason: Connection timed out

my server console output:

Code: Select all

Zandronum v1.0 - SVN revision 120819-2011 - SDL version
Compiled on Aug 19 2012

M_LoadDefaults: Load system defaults.
sv_maxlives will be changed for next game.
deathmatch will be changed for next game.
W_Init: Init WADfiles.
 adding /usr/games/zandronum/zandronum.pk3 (551 files)
 adding /usr/share/games/doom/freedoom.wad (3286 lumps)
I_Init: Setting up machine state.
CPU Vendor ID: AuthenticAMD
  Name: AMD V120 Processor
  Family 16 (16), Model 6, Stepping 3
  Features: MMX SSE SSE2 SSE3
IPFileParser::parseIPList: Couldn't open file: whitelist.txt!
REASON: ENOENT: A component of filename does not name an existing file or filename is an empty string.
IPFileParser::parseIPList: Couldn't open file: banlist.txt!
REASON: ENOENT: A component of filename does not name an existing file or filename is an empty string.
IPFileParser::parseIPList: Couldn't open file: adminlist.txt!
REASON: ENOENT: A component of filename does not name an existing file or filename is an empty string.
S_Init: Setting up sound.
ST_Init: Init startup screen.
P_Init: Checking cmd-line parameters...
G_ParseMapInfo: Load map definitions.
S_InitData: Load sound definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
Patch installed
M_Init: Init miscellaneous info.
P_Init: Init Playloop state.
ParseSBarInfo: Loading default status bar definition.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
using alternate port 10666
player 1 of 1 (1 nodes)
Initializing network subsystem.
Server using alternate port 10666.
NETWORK_Construct: Couldn't bind to 10666. Binding to 10667 instead...
Found interface lo with IP address: 127.0.0.1
Found interface wlan0 with IP address: 192.168.1.2
Using IP address of interface wlan0 as local address.
IP address 192.168.1.2:10667
UDP Initialized.
MAP01 (map01) added to map rotation list at position 1.

*** MAP01: map01 ***

compatflags changed to: 0

Any help? Is there are step-by-step guide?

Posted: **Sun Sep 16, 2012 8:58 am**

From the log it shows that there is something else already listening on port 10666* and thus the server was started on port 10667.
If that's not to your knowledge, it may be a zombie process which can be fixed by rebooting the computer.
Instead of using canyouseeme to check the server availability, temporarily set SV_ShowLauncherQueries to True and watch the console for activity for a moment. If there is activity from clients querying the server it means that the server is publicly visible.

*You can find out what process is using port 10666 with fuser 10666/udp and ps aux | grep 'The process number output from the previous command'.

Posted: **Sun Sep 16, 2012 3:30 pm**

I just typically do a ps ax | grep zandronum and find the PID of the process and kill it.

Posted: **Sun Sep 23, 2012 8:59 pm**

Well, I added 192.168.1.2 address in doomseeker options, now my server is visible for other players

Posted: **Tue Oct 16, 2012 3:04 pm**

im also trying to get servers going, but I got this qierd thing then i use that command konar said, i use port 10666, it tells it directs to 10667 and then i launch the sv_showlauncherquery it says it send a challenge on 192.168.1.13:12999 whats up? O.o
also, if i refresh myself, it says the same with port 51011

Zandronum

Help with server host...

Help with server host...

RE: Help with server host...

RE: Help with server host...

RE: Help with server host...

RE: Help with server host...