Advertisement
Page 1 of 1
[4.2.018] Servers Not Listed
I cannot get the server listing to work
#1
Posted 23 June 2014 - 11:48 AM
When I query for servers I get:
"335 servers not listed due to filters, packet loss or pings higher than 800"
My operating system confirms that the q3a client is listening on port 27960 and 27961, which is also where the server responses arrive. A search revealed that people had to add port forwarding to their router configuration to fix this (previously). Which does nothing for me.
I've captured the traffic using wireshark and with or without a port forwarding, the packages arrive at my interface any way.
I've also tested to do a search with sv_master1 = "master.urbanterror.info:27900" from baseq3, which lists all the servers just fine. So I have to conclude that the filtering happens in UrT's ui.qvm.
Any idea what might cause this?
"335 servers not listed due to filters, packet loss or pings higher than 800"
My operating system confirms that the q3a client is listening on port 27960 and 27961, which is also where the server responses arrive. A search revealed that people had to add port forwarding to their router configuration to fix this (previously). Which does nothing for me.
I've captured the traffic using wireshark and with or without a port forwarding, the packages arrive at my interface any way.
I've also tested to do a search with sv_master1 = "master.urbanterror.info:27900" from baseq3, which lists all the servers just fine. So I have to conclude that the filtering happens in UrT's ui.qvm.
Any idea what might cause this?
#2
Posted 23 June 2014 - 11:18 PM
First check your filters on the server browser - view full, view empty, gametype all, etc.
[img]http://i.imgur.com/OQ7HC64.gif[/img]
#3
Posted 24 June 2014 - 10:27 AM
1. The request to the master server: getservers 68 full empty
2. The master server replies with a list of servers (2 packages)
3. The client queries the servers: getinfo xxx
4. Example server response: infoResponse\x0a\\modversion\\4.2.018\\game\\q3ut4\\auth\\1\\pure\\1\\gametype\\8\\sv_maxclients\\14\\clients\\0\\mapname\\ut4_uptown\\hostname\\^1=DK=^2Pistol&Nades^3Classic\\protocol\\68\\challenge\\xxx
So we've got the right version of the mod and the right protocol. Needless to say there are hundreds of requests and responses.
My query settings:
Type: All
Accounts: All
Private: Any
View Full: Yes
View Empty: Yes
Does the VM check the version string that's displayed in the console or somesuch? I only see modversion and that should be fine, at least all the checksums match.
2. The master server replies with a list of servers (2 packages)
3. The client queries the servers: getinfo xxx
4. Example server response: infoResponse\x0a\\modversion\\4.2.018\\game\\q3ut4\\auth\\1\\pure\\1\\gametype\\8\\sv_maxclients\\14\\clients\\0\\mapname\\ut4_uptown\\hostname\\^1=DK=^2Pistol&Nades^3Classic\\protocol\\68\\challenge\\xxx
So we've got the right version of the mod and the right protocol. Needless to say there are hundreds of requests and responses.
My query settings:
Type: All
Accounts: All
Private: Any
View Full: Yes
View Empty: Yes
Does the VM check the version string that's displayed in the console or somesuch? I only see modversion and that should be fine, at least all the checksums match.
This post has been edited by lonkamikaze: 24 June 2014 - 10:28 AM
#4
Posted 24 June 2014 - 11:46 AM
i remember qtracker displaying q3urt42 as a game name for some servers. Though that is probably not the point here.
If it got it correctly that traffic you got is captured outside of UrT?
You could try setting verbose to 1 in UrT (that might spam your console with texture fallbacks and stuff)
Things i could imagine:
Your firewall blocks/sandboxes UrT from incomming connections/traffic.
Your version of the ui qvm is "broken". you could try redownloading it.
There is some random problem between your q3a client (which is logically not the q3-urt client)
Anyway, you can still use qtracker or UrT connector or whatever all those tools are called as a workaround.
If the game doesnt take too long to startup, qtracker is the way to go. i actually only use qtracker. You just have to remember that you have to quit the game and not only disconnect.
If it got it correctly that traffic you got is captured outside of UrT?
You could try setting verbose to 1 in UrT (that might spam your console with texture fallbacks and stuff)
Things i could imagine:
Your firewall blocks/sandboxes UrT from incomming connections/traffic.
Your version of the ui qvm is "broken". you could try redownloading it.
There is some random problem between your q3a client (which is logically not the q3-urt client)
Anyway, you can still use qtracker or UrT connector or whatever all those tools are called as a workaround.
If the game doesnt take too long to startup, qtracker is the way to go. i actually only use qtracker. You just have to remember that you have to quit the game and not only disconnect.
Sorry for my bad spelling - I am still asleep. :)
|=| Iye's UrT Addon |=| Firefox Personas |=| Maps |=|
http://www.mediafire...vk3a602hcfg.jpg
|=| Iye's UrT Addon |=| Firefox Personas |=| Maps |=|
http://www.mediafire...vk3a602hcfg.jpg
#5
Posted 24 June 2014 - 12:03 PM
Iye, on 24 June 2014 - 11:46 AM, said:
i remember qtracker displaying q3urt42 as a game name for some servers. Though that is probably not the point here.
]
If it got it correctly that traffic you got is captured outside of UrT?
You could try setting verbose to 1 in UrT (that might spam your console with texture fallbacks and stuff)
]
If it got it correctly that traffic you got is captured outside of UrT?
You could try setting verbose to 1 in UrT (that might spam your console with texture fallbacks and stuff)
I think I'll try that one.
Iye, on 24 June 2014 - 11:46 AM, said:
Things i could imagine:
Your firewall blocks/sandboxes UrT from incomming connections/traffic.
Your firewall blocks/sandboxes UrT from incomming connections/traffic.
Iye, on 24 June 2014 - 11:46 AM, said:
Your version of the ui qvm is "broken". you could try redownloading it.
Iye, on 24 June 2014 - 11:46 AM, said:
There is some random problem between your q3a client (which is logically not the q3-urt client)
Iye, on 24 June 2014 - 11:46 AM, said:
Anyway, you can still use qtracker or UrT connector or whatever all those tools are called as a workaround.
If the game doesnt take too long to startup, qtracker is the way to go. i actually only use qtracker. You just have to remember that you have to quit the game and not only disconnect.
If the game doesnt take too long to startup, qtracker is the way to go. i actually only use qtracker. You just have to remember that you have to quit the game and not only disconnect.
Advertisement
#6
Posted 24 June 2014 - 12:31 PM
Iye, on 24 June 2014 - 11:46 AM, said:
i remember qtracker displaying q3urt42 as a game name for some servers. Though that is probably not the point here.
ing
If it got it correctly that traffic you got is captured outside of UrT?
You could try setting verbose to 1 in UrT (that might spam your console with texture fallbacks and stuff)
ing
If it got it correctly that traffic you got is captured outside of UrT?
You could try setting verbose to 1 in UrT (that might spam your console with texture fallbacks and stuff)
^3EXEC_NOW globalservers 0 68 full empty
Requesting servers from master master.urbanterror.info...
UI_CIN_PlayCinematic
SCR_PlayCinematic( ut4_granja.roq )
play(ut4_granja.roq), ROQSize<=0
CL packet 178.33.22.115:27900: getserversResponse\.A
CL_ServersResponsePacket
195 servers parsed (total 195)
CL packet 178.33.22.115:27900: getserversResponse\..sbm9\.#MPm<\^
CL_ServersResponsePacket
130 servers parsed (total 325)
CL packet 195.122.135.216:27960: infoResponse
ping time 1ms from 195.122.135.216
CL packet 5.231.57.33:27960: infoResponse
ping time 1ms from 5.231.57.33
CL packet 188.138.115.98:27979: infoResponse
ping time 1ms from 188.138.115.98
CL packet 93.186.198.29:27960: infoResponse
ping time 1ms from 93.186.198.29
…
CL packet 188.138.48.106:27967: infoResponse
ping time 1ms from 188.138.48.106
CL packet 176.31.99.105:27960: infoResponse
ping time 1ms from 176.31.99.105
CL packet 62.210.76.88:27960: infoResponse
ping time 1ms from 62.210.76.88
CL packet 194.116.82.5:27962: infoResponse
ping time 1ms from 194.116.82.5
CL packet 121.99.187.29:27960: infoResponse
ping time 264ms from 121.99.187.29
CL packet 192.99.35.27:27961: infoResponse
ping time 1ms from 192.99.35.27
CL packet 174.4.188.24:27975: infoResponse
ping time 147ms from 174.4.188.24
0 servers listed in browser with 11017 players.
325 servers not listed due to filters, packet loss or pings higher than 800
Page 1 of 1
1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Advertisement