|
Notes |
|
|
|
It's normal that your server uses the local IP since that is the IP of your network adapter. "-useip" can only select IPs of network adapters in your machine. Your router has to be configured to forward incoming packets to your server, the same applies to 2.0 and 3.0 though.
So you are saying that 2.0 (do you mean 2.1.2?) works on your machine, but 3.0 does not? And you are not changing anything except the Zandronum binary? |
|
|
|
(0016226)
|
|
masos
|
|
2016-11-20 21:07
|
|
|
Yeah, sorry, not 2.0, 2.1.2. 2.1.2 works fine, but 3.0 does not. I don't change anything except Zandronum versions. Like I said in issue description, I already did a port forward on my router. If I wouldn't, people wouldn't be able to connect to me when I was on 2.1.2, right? |
|
|
|
|
Right.
Can you start both the 2.1.2 and the 3.0 server (one after another, not both at once) with "+logfile log" and upload the log files that will be written with this option? |
|
|
|
(0016246)
|
|
masos
|
2016-11-21 12:48
(edited on: 2016-11-21 12:57) |
|
Uploaded.
For some reason now 2.1.2 doesn't work too. What could be changed if I didn't change anything myself? Also, I tried mapping other apps to same port 10666. Strangely, they worked fine (of course, I did not try to use them at the same time with running the server, because only one app can bind the port). I previously hosted various game servers, and all worked fine too.
UPD: Uploaded router config screenshot to be totally sure.
UPD2: Firewall is turned off so it doesn't interfere.
|
|
|
|
|
|
Is your external IP listed on the master server (possibly as non responding)? |
|
|
|
(0016261)
|
|
masos
|
|
2016-11-21 19:17
|
|
|
I can't find it myself, but people on Zandronum IRC say it is listed and yes, as non-responding. |
|
|
|
|
|
The master server should report the same server list to everybody. If your IP is on it and somebody sees it, you should also see it. With some ISPs, you can't communicate with your own external IP, so your server could be listed as non-responding for you, but as responding for others, but if the IP is on the list, you should see it. Can you double check that it is really not on the list for you? |
|
|
|
(0016266)
|
|
masos
|
|
2016-11-21 19:45
|
|
|
Nevermind, found it. So much servers, it's hard to find the one I need especially when it doesn't have a name. So yes, it is on the list, I see it now. But still no response from it. |
|
|
|
|
|
Ok, then the server -> master server communication works and it likely is a port forwarding / firewall problem. Did you try using UPnP, i.e. starting the server with "-upnp"? |
|
|
|
(0016268)
|
|
masos
|
|
2016-11-21 20:56
|
|
|
Like I said, port forwarding works ok with hosting other games' servers and therefore I am pretty sure I can do it. Firewall is off. I tried using -upnp, but it showed me "Failed to use UPnP: NAT device not found" or something like that, don't really remember. |
|
|
|
|
|
Is the port listed for your server on the master server correct? |
|
|
|
(0016270)
|
|
masos
|
|
2016-11-21 21:04
|
|
|
No, it is not. For some reason it shows port 23794. Server window still shows port 10666, though. |
|
|
|
(0016271)
|
|
Torr Samaho
|
2016-11-21 21:09
(edited on: 2016-11-21 21:12) |
|
Then that is your problem. Zandronum has no control over which external port your router assigns to Zandronum's outgoing UDP connection and the master always uses that port to list the server. You either need to forward that port or force your router to assign the port you want.
EDIT: 0000992 has some more information on this.
|
|
|
|
(0016272)
|
|
masos
|
|
2016-11-21 21:30
|
|
|
Cannot find that option in my router. Still, I forwarded 23794 and set my server to run also on 23794. Now it at least accepts connections on 23794 even though it doesn't show up in master list correctly. |
|
|
|
|
Quote from masos
even though it doesn't show up in master list correctly.
Can you elaborate? If the entry on the master server list is wrong, nobody will be able to connect to your server. |
|
|
|
(0016274)
|
|
masos
|
2016-11-21 21:38
(edited on: 2016-11-21 21:39) |
|
I just wanted to play with my friend, and he can connect directly by IP. Master server's not needed for it.
UPD: I'd fix it ASAP if I knew how.
|
|
|
|
|
|
Ah, I see. Thanks for clarifying. So it's working fine for your purposes now? |
|
|
|
(0016276)
|
|
masos
|
|
2016-11-21 21:47
|
|
|
Yeah. Broadcasting to master server would be awesome too, but it seems much too complicated to do. I wonder how did it even work before without these tweaks? |
|
|
|
(0016277)
|
|
masos
|
|
2016-11-21 21:57
|
|
|
Is there a way to force master server listing port to be the same as my server port? Before this issue started it was done automatically. |
|
|
|
|
Quote from masos
Is there a way to force master server listing port to be the same as my server port?
Currently, not. The master server protocol needs to be extended to make this possible.
Quote from masos
Before this issue started it was done automatically.
If it worked before, then your router assigned the same external port as your internal port. I can't say why your router stopped doing that. |
|
|
|
(0016287)
|
|
masos
|
|
2016-11-22 14:12
|
|
|
OK, thanks. You can now mark the issue as resolved. |
|
|
|
|
|
I'll do. Since 0000992 is still open, adding a port override will stay on the radar. |
|
log3_0.log (13,328) 2016-11-21 12:39
Безымянный.png (66,123) 2016-11-21 12:54