Jump to content
Sign in to follow this  
poesel

Linux: no servers

Recommended Posts

Hi!

I don't get any servers after I hit refresh.

The system is an Ubuntu 5.10. Updating to 0.9.43 did not help.

I do find servers from my Mac on the same net (even though that is still 0.9.42).

From the DropTeam.log I see that its trying to ping several servers (and retrying). I can ping them from the terminal without problems.

Any ideas?

Share this post


Link to post
Share on other sites

Sorry to answer myself...

There has been a similar question from nirse before but with no conclusion. I just wanted to answer the questions asked there:

The DropTeam.log (minus graphics)

[..]

CAMPAIGNINPROGRESS: Loading ../data/Campaigns.progress

LOBBY: Pinging server 129.16.117.169:9967

LOBBY: Pinging server 209.11.246.130:9967

LOBBY: Pinging server 209.11.240.218:9967

LOBBY: Pinging server 82.165.243.126:9967

LOBBY: Retrying server 129.16.117.169:9967

LOBBY: Retrying server 209.11.246.130:9967

LOBBY: Retrying server 209.11.240.218:9967

LOBBY: Retrying server 82.165.243.126:9967

LOBBY: Pinging server 129.16.117.169:9967

LOBBY: Pinging server 209.11.246.130:9967

LOBBY: Pinging server 209.11.240.218:9967

LOBBY: Pinging server 82.165.243.126:9967

LOBBY: Retrying server 129.16.117.169:9967

LOBBY: Retrying server 209.11.246.130:9967

LOBBY: Retrying server 209.11.240.218:9967

LOBBY: Retrying server 82.165.243.126:9967

LOBBY: Pinging server 129.16.117.169:9967

LOBBY: Pinging server 209.11.246.130:9967

LOBBY: Pinging server 209.11.240.218:9967

LOBBY: Pinging server 82.165.243.126:9967

LOBBY: Retrying server 129.16.117.169:9967

LOBBY: Retrying server 209.11.246.130:9967

LOBBY: Retrying server 209.11.240.218:9967

LOBBY: Retrying server 82.165.243.126:9967

LOBBY: Pinging server 129.16.117.169:9967

LOBBY: Pinging server 209.11.246.130:9967

LOBBY: Pinging server 209.11.240.218:9967

LOBBY: Pinging server 82.165.243.126:9967

LOBBY: Retrying server 129.16.117.169:9967

LOBBY: Retrying server 209.11.246.130:9967

LOBBY: Retrying server 209.11.240.218:9967

LOBBY: Retrying server 82.165.243.126:9967

LOBBY: Pinging server 129.16.117.169:9967

LOBBY: Pinging server 209.11.246.130:9967

LOBBY: Pinging server 209.11.240.218:9967

LOBBY: Pinging server 82.165.243.126:9967

LOBBY: Retrying server 129.16.117.169:9967

LOBBY: Retrying server 209.11.246.130:9967

LOBBY: Retrying server 209.11.240.218:9967

LOBBY: Retrying server 82.165.243.126:9967

LOBBY: Pinging server 129.16.117.169:9967

LOBBY: Pinging server 209.11.246.130:9967

LOBBY: Pinging server 209.11.240.218:9967

LOBBY: Pinging server 82.165.243.126:9967

LOBBY: Retrying server 129.16.117.169:9967

LOBBY: Retrying server 209.11.246.130:9967

LOBBY: Retrying server 209.11.240.218:9967

LOBBY: Retrying server 82.165.243.126:9967

MAIN: Quitting normally

Pinging tbgsoftware.com:

kita@kita:~$ ping tbgsoftware.com

PING tbgsoftware.com (82.165.243.126) 56(84) bytes of data.

64 bytes from u15170997.onlinehome-server.com (82.165.243.126): icmp_seq=1 ttl=51 time=101 ms

[..]

--- tbgsoftware.com ping statistics ---

12 packets transmitted, 12 received, 0% packet loss, time 11009ms

rtt min/avg/max/mdev = 96.424/98.669/100.407/1.093 ms

My username in the game is posel71. I'm behind a NAT router but no firewall. There are two Macs behind the same router without that problem.

And last but not least the tcpdump:

17:17:52.214836 IP 192.168.24.178.ipp > 192.168.24.255.ipp: UDP, length 116

17:17:56.215554 IP 192.168.24.178.ipp > 192.168.24.255.ipp: UDP, length 114

17:18:02.216346 IP 192.168.24.178.ipp > 192.168.24.255.ipp: UDP, length 116

17:18:04.052259 IP 192.168.24.187.32768 > ns1.ish.de.domain: 3750+ A? tbgsoftware.com. (33)

17:18:04.061433 IP ns1.ish.de.domain > 192.168.24.187.32768: 3750 1/2/0 A u15170997.onlinehome-server.com (93)

17:18:04.061547 IP 192.168.24.187.32769 > ns1.ish.de.domain: 62337+ PTR? 126.243.165.82.in-addr.arpa. (45)

17:18:04.061634 IP 192.168.24.187.45494 > u15170997.onlinehome-server.com.9964: S 30391249:30391249(0) win 5840 <mss 1460,sackOK,timestamp 9405329 0,nop,wscale 2>

17:18:04.076645 IP ns1.ish.de.domain > 192.168.24.187.32769: 62337 1/3/3 (201)

17:18:04.164753 IP u15170997.onlinehome-server.com.9964 > 192.168.24.187.45494: S 527847137:527847137(0) ack 30391250 win 5792 <mss 1460,sackOK,timestamp 2879924156 9405329,nop,wscale 0>

17:18:04.164799 IP 192.168.24.187.45494 > u15170997.onlinehome-server.com.9964: . ack 1 win 1460 <nop,nop,timestamp 9405432 2879924156>

17:18:04.648565 IP u15170997.onlinehome-server.com.9964 > 192.168.24.187.45494: P 1:81(80) ack 1 win 5792 <nop,nop,timestamp 2879924205 9405432>

17:18:04.648606 IP 192.168.24.187.45494 > u15170997.onlinehome-server.com.9964: . ack 81 win 1460 <nop,nop,timestamp 9405916 2879924205>

17:18:04.648890 IP u15170997.onlinehome-server.com.9964 > 192.168.24.187.45494: F 81:81(0) ack 1 win 5792 <nop,nop,timestamp 2879924205 9405432>

17:18:04.648969 IP 192.168.24.187.45494 > u15170997.onlinehome-server.com.9964: F 1:1(0) ack 82 win 1460 <nop,nop,timestamp 9405917 2879924205>

17:18:04.649464 IP 192.168.24.187.32769 > iota249.dd.chalmers.se.9967: UDP, length 9

17:18:04.649768 IP 192.168.24.187.32769 > CUSTOMER.VPLS.NET.9967: UDP, length 9

17:18:04.650059 IP 192.168.24.187.32769 > CUSTOMER.VPLS.NET.9967: UDP, length 9

17:18:04.650347 IP 192.168.24.187.32769 > u15170997.onlinehome-server.com.9967: UDP, length 9

17:18:04.659151 IP 192.168.24.187.32770 > ns1.ish.de.domain: 16010+ PTR? 169.117.16.129.in-addr.arpa. (45)

17:18:04.705980 IP ns1.ish.de.domain > 192.168.24.187.32770: 16010 1/3/2 (167)

17:18:04.709081 IP 192.168.24.187.32770 > ns1.ish.de.domain: 38874+ PTR? 130.246.11.209.in-addr.arpa. (45)

17:18:04.747768 IP u15170997.onlinehome-server.com.9964 > 192.168.24.187.45494: . ack 2 win 5792 <nop,nop,timestamp 2879924214 9405917>

17:18:06.999601 IP ns1.ish.de.domain > 192.168.24.187.32770: 38874 1/2/2 (144)

17:18:06.999940 IP 192.168.24.187.32770 > ns1.ish.de.domain: 62740+ PTR? 218.240.11.209.in-addr.arpa. (45)

17:18:07.150075 IP 192.168.24.187.32769 > iota249.dd.chalmers.se.9967: UDP, length 9

17:18:07.150378 IP 192.168.24.187.32769 > CUSTOMER.VPLS.NET.9967: UDP, length 9

17:18:07.150709 IP 192.168.24.187.32769 > CUSTOMER.VPLS.NET.9967: UDP, length 9

17:18:07.151003 IP 192.168.24.187.32769 > u15170997.onlinehome-server.com.9967: UDP, length 9

17:18:09.345186 IP ns1.ish.de.domain > 192.168.24.187.32770: 62740 1/2/2 (144)

17:18:09.651127 IP 192.168.24.187.32769 > iota249.dd.chalmers.se.9967: UDP, length 9

17:18:09.651507 IP 192.168.24.187.32769 > CUSTOMER.VPLS.NET.9967: UDP, length 9

17:18:09.651812 IP 192.168.24.187.32769 > CUSTOMER.VPLS.NET.9967: UDP, length 9

17:18:09.652238 IP 192.168.24.187.32769 > u15170997.onlinehome-server.com.9967: UDP, length 9

Share this post


Link to post
Share on other sites

When you said no firewall, are you talking about firewall on the NAT box ?

Does Ubuntu have iptables turned on by default ?

Suggestion: you could do the same tcpdump on the MAC and see if the traces differ.

Share this post


Link to post
Share on other sites

When you are pinging the servers I bet the ping goes to different port. This could be why normal ping works but the games ping doesn't.

Share this post


Link to post
Share on other sites

Drusus,

If you want to get detailed, ping is ICMP at the IP layer (no port). The client is using UDP which is on layer on top of IP (which uses a random port numbered between 1023-65535). Ping just mean the server actually has IP connectivity, it does not mean the server is running (the server is listening at UDP port 9967 for incomming client request). smile.gif

Share this post


Link to post
Share on other sites

So thats the dump from the mac box (its trimmed - theres some other software running too):

21:41:17.442595 IP u15170997.onlinehome-server.com.9964 > 192.168.24.178.63437: F 81:81(0) ack 1 win 5792 <nop,nop,timestamp 2883014235 748372403>

21:41:17.442694 IP 192.168.24.178.63437 > u15170997.onlinehome-server.com.9964: . ack 1 win 65535 <nop,nop,timestamp 748372403 2883014212>

21:41:17.443192 IP u15170997.onlinehome-server.com.9964 > 192.168.24.178.63437: P 1:81(80) ack 1 win 5792 <nop,nop,timestamp 2883014235 748372403>

21:41:17.443235 IP 192.168.24.178.63437 > u15170997.onlinehome-server.com.9964: . ack 82 win 65535 <nop,nop,timestamp 748372403 2883014235>21:41:17.443441 IP 192.168.24.178.63437 > u15170997.onlinehome-server.com.9964: F 1:1(0) ack 82 win 65535 <nop,nop,timestamp 748372403 2883014235>

21:41:17.444617 IP 192.168.24.178.54559 > iota249.dd.chalmers.se.9967: UDP, length: 9

21:41:17.445296 IP 192.168.24.178.54559 > customer.vpls.net.9967: UDP, length: 9

21:41:17.445818 IP 192.168.24.178.54559 > customer.vpls.net.9967: UDP, length: 9

21:41:17.446300 IP 192.168.24.178.54559 > u15170997.onlinehome-server.com.9967: UDP, length: 9

21:41:17.543925 IP u15170997.onlinehome-server.com.9964 > 192.168.24.178.63437: . ack 2 win 5792 <nop,nop,timestamp 2883014245 748372403>

21:41:19.949449 IP 192.168.24.178.54559 > customer.vpls.net.9967: UDP, length: 9

21:41:19.951245 IP 192.168.24.178.54559 > customer.vpls.net.9967: UDP, length: 9

21:41:19.952151 IP 192.168.24.178.54559 > u15170997.onlinehome-server.com.9967: UDP, length: 9

21:41:22.483749 IP 192.168.24.178.54559 > customer.vpls.net.9967: UDP, length: 9

21:41:22.484438 IP 192.168.24.178.54559 > customer.vpls.net.9967: UDP, length: 9

21:41:22.485002 IP 192.168.24.178.54559 > u15170997.onlinehome-server.com.9967: UDP, length: 9

Iptables is enabled, but shouldn't be the cause: all chains have policy accept (can't show you the output of 'iptables -L' as I'm typing this on the Mac)

I could create a server on the Mac and connect from the Linux box, though. Everything worked fine and stable.

Now I don't know what to do further. I will test anything you want.

Share this post


Link to post
Share on other sites

After a quick look the second trace looks like the first one. It is surprising that the second traces does not show any packets from the servers responding to the client using source port UDP 9967 although it is suppose to be working (there is a tcp session between u15170997.onlinehome-server.com, but I do not know the signicance of it).

Share this post


Link to post
Share on other sites

Hmm, seein is believin? smile.gif

root@kita:/home/kita# iptables -L

Chain INPUT (policy ACCEPT)

target prot opt source destination

Chain FORWARD (policy ACCEPT)

target prot opt source destination

Chain OUTPUT (policy ACCEPT)

target prot opt source destination

I'm afraid that iptables is not the source.

About the second tcpdump: it may be that I deleted too much so some lines may be missing.

This is a fresh Ubuntu 5.10 install on my old PC I did just to play DropTeam. So you may easily recreate the setup if you want.

Of course I will continue to try what you propose.

thanks

Share this post


Link to post
Share on other sites
Hmm, seein is believin?
Yeah, well, you know how it is... smile.gif

Thanks for the output. You're right that iptables isn't it. Digging around for a suitable test box to put Ubuntu on now ... sigh ... smile.gif

Will advise when we know more.

Share this post


Link to post
Share on other sites

Yes and no smile.gif

I tried several times and finally: dada - a server!

DD_Gothenburg running 0.9.42

But: the JOIN - button is grey and I can't click on it. Maybe because of the different versions?

Hmm, where are the other servers? So I started the Mac version and found only the same one. I noticed I had to click on the servers name to get JOIN to lighten up. So I switched back to Linux (both machines are on the same monitor), hit refresh several times but again no server.

???

Sooo, next try: turn off DropTeam on the Mac and reset the router - voila - again I find Gothenburg on Linux!

1) so whenever I had started DT on the Mac, it won't find a server on Linux. The other way round is no problem

2) even if I find a server I can't join, because the button stays grey no matter what or where I click

1) is strange (its a bog standard D-Link DL-524) but now I know its solvable

2) is really annoying. Now that I'm so close... smile.gif

Hope you find something.

Share this post


Link to post
Share on other sites

poesel71,

If it helps any, based on network trace, it looks like:

1) DT client exchange info with u15170997.onlinehome-server.com via TCP port 9964.

2) u15170997.onlinehome-server.com sends back list of servers.

3) DT Client start polling servers on UDP port 9967 based on received list.

4) The DT server selected for joining answers the Client.

Question to DT developers: If poesel71 give you his "real" IP address, could you find out if the UDP packets gets to the server using iptables/tcpdump ?

Share this post


Link to post
Share on other sites

Yes, we can, and we already have a volunteer lined up who also has this problem - he's going to refresh while we're watching in the debugger, which will be even better. Poesel, if you're able and willing to schedule a time for such a test that would be a big help, too. Email me if so.

I strongly suspect some kind of PAT issue, but there's little point in speculating until we see what's really happening. However, any theories are greatly welcome, Type98!

Share this post


Link to post
Share on other sites

From the D-link web site, the DL-524 apparently has four different versions of firmware. It is also a wireless router which I am not versed in. The trouble could be linux wireless support rather than the game software.

Best suggestion to isolate that would be to move the offending system to wired and retry the game (or swap the NIC).

Share this post


Link to post
Share on other sites

Yes, testing directly without the router should not be a problem.

I will be at home at around 1800h GMT+1 (you should be awake by then smile.gif . If you give me your Skype/Jabber/ICQ/IRC/... - number/name I will contact you.

I have the current german version of the firmware. The linux box is connected by wire, the macs wireless.

Share this post


Link to post
Share on other sites

Found the solution: its the &$%$@#% router.

Plugging the cable directly in the modem and everything works. I will now try to find out whats wrong there....

Share this post


Link to post
Share on other sites

Ok, the solution is to configure the router to DMZ the linux box. That works reliable although its somehow strange that I have to.

The only difference between the wireless macs and the linux box was that the macs were on static dhcp. But doing that for the linux box didn"t change anything.

?

Well now to something completly different: has someone got the teamspeak feature running under linux? The mic is fine (I can do recordings) but noone hears me in the game (after pressing 'p' of course)

thanks

Share this post


Link to post
Share on other sites

No,after putting it in the DMZ I have something like 5 servers. Although I would like to see more people on the Gothenburg server because I have the best ping to it. smile.gif

Share this post


Link to post
Share on other sites
Sign in to follow this  

×
×
  • Create New...