The International Simutrans Forum

 

Author Topic: Announce server issues - assistance requested  (Read 6223 times)

0 Members and 1 Guest are viewing this topic.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Announce server issues - assistance requested
« on: August 19, 2013, 12:32:52 AM »
With the new announce server no longer having a fixed IP, a temporary workaround for issues that I was having with getting the DNS lookup for the announce server to work on Experimental by using the IP no longer work. Having reverted in 11.6 to the proper URL, I find that this issue remains live and has not been fixed by the several merges with Standard that have occurred since the workaround was first installed.

The problem is one that I am afraid that I barely understand. What I know is that, when using the URL rather than the IP address, the announce server function fails completely. I also know that I have not changed the networking code from Standard (except some earlier attempts to solve this very problem, I think), so I am somewhat baffled by this.

When I run the code in a debugger and look in particular at the output of network_file_transfer and the strings that are written by the server there, I note, firstly, that the "err" string is NULL, indicating that the method itself has detected no error. The messages that I get in line 347 (that is, the messages received from the server) are, in order:

Code: [Select]
HTTP/1.0 303 See Other
Location: http://servers.experimental.simutrans.org:80/announce
Content-Length: 0
Connection: close
Date: Mon, 19 Aug 2013 00:25:05 GMT
Server: OpenDNS Guide

Any clue as to where even to begin to try to solve this would be very, very much appreciated indeed.


Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #1 on: August 20, 2013, 12:49:41 AM »
I have just checked specifically. With the exception of the changes implemented in the last few days in relation to the header files for putting network files into their own subfolder, the only difference in network_file_transfer.cc between Standard and Experimental is:

Code: [Select]
-        if(  err = network_receive_file( my_client_socket, filename, len )  ) {
-            goto end;
-        }
-        // Knightly : update iteration limits
-        // wait for routesearch command (tolerate some wrong commands)
-        for(  uint8 i=0;  i<5;  ++i  ) {
-            nwc = network_check_activity( NULL, 10000 );
-            if(  nwc  &&  nwc->get_id()==NWC_ROUTESEARCH  ) break;
-        }
-        if(  nwc==NULL  ||  nwc->get_id()!=NWC_ROUTESEARCH  ) {
-            err = "Protocol error (expected NWC_ROUTESEARCH)";
-            goto end;
-        }
-        ((nwc_routesearch_t*)nwc)->do_command(world);
+        err = network_receive_file( my_client_socket, filename, len );
     }

(This is a reverse .diff - these are the changes to go from Experimental to Standard).

Given that err is always NULL when this method is called for a server announce, it is hard to see how this could have any impact on the issue.

Offline asaphxiix

  • *
  • Posts: 723
Re: Announce server issues - assistance requested
« Reply #2 on: August 26, 2013, 06:21:56 PM »
seems to be a typo: the game server tries to inquire of the domain name 'servers.experimental.simutrans', and gets 'no such name' in response. The missing '.org' should do the trick.

This I see in a packet capture running on my network card when running a server. Strangely however, the http header you put above indicates the game server can communicate with the listing server, only to get the 303 code. If this is the case, then the problem may stem from the fact that on top of a cname (alternative hostname) reply to simlist-experimental.herokuapp.com, for the servers.experimental.simutrans.org hostname, there is also an http redirection done by the web server itself, HTTP 303 meaning 'moved, try a different URI'. A browser can handle this, but I see no reason why simutrans client should, or would use the new URI received from the web server to post the announcement on that former, without being programmed to do so. I wonder if the standard listing server acts the same, and how the standard game server can handle that.
« Last Edit: August 26, 2013, 06:32:39 PM by asaphxiix »

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #3 on: August 26, 2013, 06:30:43 PM »
seems to be a typo: the game server tries to inquire of the domain name 'servers.experimental.simutrans', and gets 'no such name' in response. The missing '.org' should do the trick.

Interesting - how do you come to that conclusion?

The actual code defining the URL is in simversion.h:

Code: [Select]
/* Server to announce status to */
#define ANNOUNCE_SERVER "servers.experimental.simutrans.org:80"

As can be seen, the ".org" is not missing. If you have analysed the request actually sent and found that it is missing the .org, it is getting truncated somewhere, but it is not clear where or why.

Offline asaphxiix

  • *
  • Posts: 723
Re: Announce server issues - assistance requested
« Reply #4 on: August 26, 2013, 06:34:34 PM »
see my edit above.

might you run 'tcpdump -i (interface name) > filename' when announcing and share it?

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #5 on: August 26, 2013, 06:40:34 PM »
I think that the Standard listing server works in the same way, but I am not sure. It may well be that Simutrans is indeed designed to work with a 303.

May I ask (and apologies for being dim) - how do I discover the "interface name" in your command as above?

Offline asaphxiix

  • *
  • Posts: 723
Re: Announce server issues - assistance requested
« Reply #6 on: August 26, 2013, 06:52:32 PM »
apologies as well - run 'route', and use the interface of the default destination line, the last one. usually eth0

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #7 on: August 26, 2013, 09:39:17 PM »
Here is the content of the resulting dump:

Code: [Select]
22:38:17.352529 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54431: Flags [P.], seq 4236960496:4236960608, ack 3862727900, win 213, options [nop,nop,TS val 818578227 ecr 10331840], length 112
22:38:17.354867 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54431: Flags [P.], seq 112:160, ack 1, win 213, options [nop,nop,TS val 818578228 ecr 10331840], length 48
22:38:17.354913 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54431: Flags [P.], seq 160:272, ack 1, win 213, options [nop,nop,TS val 818578228 ecr 10331840], length 112
22:38:17.354934 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54431: Flags [P.], seq 272:320, ack 1, win 213, options [nop,nop,TS val 818578228 ecr 10331840], length 48
22:38:17.355333 IP 438242.vps-10.com.48747 > 46.32.224.30.domain: 5496+ PTR? 250.23.69.82.in-addr.arpa. (43)
22:38:17.355736 IP 46.32.224.30.domain > 438242.vps-10.com.48747: 5496 1/0/0 PTR 82-69-23-250.dsl.in-addr.zen.co.uk. (91)
22:38:17.355837 IP 438242.vps-10.com.37446 > 46.32.224.31.domain: 28025+ PTR? 222.231.32.46.in-addr.arpa. (44)
22:38:17.356215 IP 46.32.224.31.domain > 438242.vps-10.com.37446: 28025 1/0/0 PTR 438242.vps-10.com. (75)
22:38:17.356329 IP 438242.vps-10.com.59095 > 46.32.224.29.domain: 53619+ PTR? 30.224.32.46.in-addr.arpa. (43)
22:38:17.356772 IP 46.32.224.29.domain > 438242.vps-10.com.59095: 53619 NXDomain 0/1/0 (112)
22:38:17.356869 IP 438242.vps-10.com.44035 > 46.32.224.30.domain: 38240+ PTR? 31.224.32.46.in-addr.arpa. (43)
22:38:17.368286 IP 46.32.224.30.domain > 438242.vps-10.com.44035: 38240 NXDomain 0/1/0 (112)
22:38:17.368507 IP 438242.vps-10.com.48610 > 46.32.224.31.domain: 41440+ PTR? 29.224.32.46.in-addr.arpa. (43)
22:38:17.368895 IP 46.32.224.31.domain > 438242.vps-10.com.48610: 41440 NXDomain 0/1/0 (112)
22:38:17.378864 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54431 > 438242.vps-10.com.ssh: Flags [.], ack 0, win 7599, options [nop,nop,TS val 10331848 ecr 818578227], length 0
22:38:17.380802 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54431 > 438242.vps-10.com.ssh: Flags [.], ack 112, win 7592, options [nop,nop,TS val 10331848 ecr 818578227], length 0
22:38:17.383013 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54431 > 438242.vps-10.com.ssh: Flags [.], ack 272, win 7589, options [nop,nop,TS val 10331849 ecr 818578228], length 0
22:38:17.383961 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54431 > 438242.vps-10.com.ssh: Flags [.], ack 320, win 7579, options [nop,nop,TS val 10331849 ecr 818578228], length 0
22:38:17.418001 ARP, Request who-has 859725.vps-10.com tell 46.32.255.254, length 46
22:38:17.418246 IP 438242.vps-10.com.47533 > 46.32.224.29.domain: 29077+ PTR? 11.255.32.46.in-addr.arpa. (43)
22:38:17.418627 IP 46.32.224.29.domain > 438242.vps-10.com.47533: 29077 1/0/0 PTR 859725.vps-10.com. (74)
22:38:17.418747 IP 438242.vps-10.com.34939 > 46.32.224.30.domain: 45566+ PTR? 254.255.32.46.in-addr.arpa. (44)
22:38:17.429759 IP 46.32.224.30.domain > 438242.vps-10.com.34939: 45566 NXDomain 0/1/0 (113)
22:38:17.464652 ARP, Request who-has 46.32.253.254 tell 261709.vps-10.com, length 46
22:38:17.464888 IP 438242.vps-10.com.49761 > 46.32.224.31.domain: 24020+ PTR? 254.253.32.46.in-addr.arpa. (44)
22:38:17.465479 IP 46.32.224.31.domain > 438242.vps-10.com.49761: 24020 NXDomain 0/1/0 (113)
22:38:17.465624 IP 438242.vps-10.com.32839 > 46.32.224.29.domain: 26084+ PTR? 84.253.32.46.in-addr.arpa. (43)
22:38:17.466094 IP 46.32.224.29.domain > 438242.vps-10.com.32839: 26084 1/0/0 PTR 261709.vps-10.com. (74)
22:38:17.687753 IP dev.wealth-dynamix.com.17500 > 255.255.255.255.17500: UDP, length 112
22:38:17.687978 IP 438242.vps-10.com.56752 > 46.32.224.30.domain: 7564+ PTR? 255.255.255.255.in-addr.arpa. (46)
22:38:17.688410 IP 46.32.224.30.domain > 438242.vps-10.com.56752: 7564 NXDomain 0/1/0 (114)
22:38:17.688496 IP 438242.vps-10.com.59414 > 46.32.224.31.domain: 53679+ PTR? 142.231.32.46.in-addr.arpa. (44)
22:38:17.688776 IP dev.wealth-dynamix.com.17500 > 46.32.231.255.17500: UDP, length 112
22:38:17.699124 IP 46.32.224.31.domain > 438242.vps-10.com.59414: 53679 1/0/0 PTR dev.wealth-dynamix.com. (80)
22:38:17.699233 IP 438242.vps-10.com.50273 > 46.32.224.29.domain: 48533+ PTR? 255.231.32.46.in-addr.arpa. (44)
22:38:17.699731 IP 46.32.224.29.domain > 438242.vps-10.com.50273: 48533 NXDomain 0/1/0 (113)
22:38:18.402348 ARP, Request who-has Do_Not_Rebuild tell 46.32.229.254, length 46
22:38:18.402618 IP 438242.vps-10.com.54634 > 46.32.224.30.domain: 58754+ PTR? 23.229.32.46.in-addr.arpa. (43)
22:38:18.414003 IP 46.32.224.30.domain > 438242.vps-10.com.54634: 58754 1/0/0 PTR Do_Not_Rebuild. (71)
22:38:18.414202 IP 438242.vps-10.com.38212 > 46.32.224.31.domain: 21824+ PTR? 254.229.32.46.in-addr.arpa. (44)
22:38:18.414642 IP 46.32.224.31.domain > 438242.vps-10.com.38212: 21824 NXDomain 0/1/0 (113)
22:38:18.465068 ARP, Request who-has 973900.vps-10.com tell 46.32.229.254, length 46
22:38:18.465297 IP 438242.vps-10.com.42720 > 46.32.224.29.domain: 48631+ PTR? 43.229.32.46.in-addr.arpa. (43)
22:38:18.476863 IP 46.32.224.29.domain > 438242.vps-10.com.42720: 48631 1/0/0 PTR 973900.vps-10.com. (74)
22:38:19.201209 ARP, Request who-has 490368.vps-10.com tell 110430.vps-10.com, length 46
22:38:19.201459 IP 438242.vps-10.com.54652 > 46.32.224.30.domain: 34143+ PTR? 85.230.32.46.in-addr.arpa. (43)
22:38:19.212876 IP 46.32.224.30.domain > 438242.vps-10.com.54652: 34143 1/0/0 PTR 490368.vps-10.com. (74)
22:38:19.213022 IP 438242.vps-10.com.55927 > 46.32.224.31.domain: 27971+ PTR? 79.230.32.46.in-addr.arpa. (43)
22:38:19.213414 IP 46.32.224.31.domain > 438242.vps-10.com.55927: 27971 1/0/0 PTR 110430.vps-10.com. (74)
22:38:19.261885 IP 143925.vps-10.com.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 40.47.54.121.in-addr.arpa. (43)
22:38:19.262113 IP 438242.vps-10.com.57927 > 46.32.224.29.domain: 55637+ PTR? 251.0.0.224.in-addr.arpa. (42)
22:38:19.346178 IP 46.32.224.29.domain > 438242.vps-10.com.57927: 55637 NXDomain 0/1/0 (99)
22:38:19.346445 IP 438242.vps-10.com.48837 > 46.32.224.30.domain: 50648+ PTR? 142.229.32.46.in-addr.arpa. (44)
22:38:19.346819 IP 46.32.224.30.domain > 438242.vps-10.com.48837: 50648 1/0/0 PTR 143925.vps-10.com. (75)
22:38:19.369130 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54889 > 438242.vps-10.com.ssh: Flags [P.], seq 1508677549:1508677597, ack 4250116232, win 2636, options [nop,nop,TS val 10332345 ecr 818577125], length 48
22:38:19.371064 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54889: Flags [P.], seq 1:49, ack 48, win 253, options [nop,nop,TS val 818578732 ecr 10332345], length 48
22:38:19.371673 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54889: Flags [P.], seq 49:145, ack 48, win 253, options [nop,nop,TS val 818578732 ecr 10332345], length 96
22:38:19.371742 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54889: Flags [P.], seq 145:193, ack 48, win 253, options [nop,nop,TS val 818578732 ecr 10332345], length 48
22:38:19.372240 IP 438242.vps-10.com.54648 > 46.32.224.30.domain: 19083+ A? bridgewater-brunel.me.uk. (42)
22:38:19.372300 IP 438242.vps-10.com.54648 > 46.32.224.30.domain: 5642+ AAAA? bridgewater-brunel.me.uk. (42)
22:38:19.373147 IP 46.32.224.30.domain > 438242.vps-10.com.54648: 19083 1/0/0 A 46.32.231.222 (58)
22:38:19.373161 IP 46.32.224.30.domain > 438242.vps-10.com.54648: 5642 0/1/0 (122)
22:38:19.373332 IP 438242.vps-10.com.43476 > 46.32.224.31.domain: 23241+ A? bridgewater-brunel.me.uk. (42)
22:38:19.373365 IP 438242.vps-10.com.43476 > 46.32.224.31.domain: 38544+ AAAA? bridgewater-brunel.me.uk. (42)
22:38:19.373609 IP 46.32.224.31.domain > 438242.vps-10.com.43476: 23241 1/0/0 A 46.32.231.222 (58)
22:38:19.373617 IP 46.32.224.31.domain > 438242.vps-10.com.43476: 38544 0/1/0 (122)
22:38:19.374588 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54889: Flags [P.], seq 193:369, ack 48, win 253, options [nop,nop,TS val 818578732 ecr 10332345], length 176
22:38:19.384044 IP 438242.vps-10.com.57364 > 46.32.224.30.domain: 63297+ A? servers.experimental.simutrans. (48)
22:38:19.384093 IP 438242.vps-10.com.57364 > 46.32.224.30.domain: 8004+ AAAA? servers.experimental.simutrans. (48)
22:38:19.384559 IP 46.32.224.30.domain > 438242.vps-10.com.57364: 63297 NXDomain 0/1/0 (123)
22:38:19.399250 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54889 > 438242.vps-10.com.ssh: Flags [.], ack 49, win 2636, options [nop,nop,TS val 10332353 ecr 818578732], length 0
22:38:19.400382 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54889 > 438242.vps-10.com.ssh: Flags [.], ack 193, win 2636, options [nop,nop,TS val 10332353 ecr 818578732], length 0
22:38:19.403527 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54889 > 438242.vps-10.com.ssh: Flags [.], ack 369, win 2641, options [nop,nop,TS val 10332354 ecr 818578732], length 0
22:38:19.418853 ARP, Request who-has 859725.vps-10.com tell 46.32.255.254, length 46
22:38:19.454605 ARP, Request who-has host2.reversednentryhis.in tell 46.32.253.254, length 46
22:38:19.454881 IP 438242.vps-10.com.37902 > 46.32.224.31.domain: 37212+ PTR? 95.252.32.46.in-addr.arpa. (43)
22:38:19.466835 IP 46.32.224.31.domain > 438242.vps-10.com.37902: 37212 1/0/0 PTR host2.reversednentryhis.in. (83)
22:38:19.471530 IP 46.32.224.30.domain > 438242.vps-10.com.57364: 8004 NXDomain 0/1/0 (123)
22:38:19.471639 IP 438242.vps-10.com.60828 > 46.32.224.31.domain: 63265+ A? servers.experimental.simutrans.vps-10.com. (59)
22:38:19.471671 IP 438242.vps-10.com.60828 > 46.32.224.31.domain: 2823+ AAAA? servers.experimental.simutrans.vps-10.com. (59)
22:38:19.472117 IP 46.32.224.31.domain > 438242.vps-10.com.60828: 63265 1/0/0 A 79.170.44.198 (75)
22:38:19.472129 IP 46.32.224.31.domain > 438242.vps-10.com.60828: 2823 0/1/0 (124)
22:38:19.472407 IP 438242.vps-10.com.58582 > 79.170.44.198.http: Flags [S], seq 2654761195, win 14600, options [mss 1460,sackOK,TS val 818578757 ecr 0,nop,wscale 7], length 0
22:38:19.472489 IP 438242.vps-10.com.33674 > 46.32.224.29.domain: 3526+ PTR? 198.44.170.79.in-addr.arpa. (44)
22:38:19.472923 IP 46.32.224.29.domain > 438242.vps-10.com.33674: 3526 NXDomain 0/1/0 (113)
22:38:19.483176 IP 79.170.44.198.http > 438242.vps-10.com.58582: Flags [S.], seq 1129369762, ack 2654761196, win 14480, options [mss 1460,sackOK,TS val 180571623 ecr 818578757,nop,wscale 7], length 0
22:38:19.483207 IP 438242.vps-10.com.58582 > 79.170.44.198.http: Flags [.], ack 1, win 115, options [nop,nop,TS val 818578760 ecr 180571623], length 0
22:38:19.483379 IP 438242.vps-10.com.58582 > 79.170.44.198.http: Flags [P.], seq 1:852, ack 1, win 115, options [nop,nop,TS val 818578760 ecr 180571623], length 851
22:38:19.494430 IP 79.170.44.198.http > 438242.vps-10.com.58582: Flags [.], ack 852, win 127, options [nop,nop,TS val 180571635 ecr 818578760], length 0
22:38:19.494450 IP 79.170.44.198.http > 438242.vps-10.com.58582: Flags [P.], seq 1:459, ack 852, win 127, options [nop,nop,TS val 180571635 ecr 818578760], length 458
22:38:19.494507 IP 438242.vps-10.com.58582 > 79.170.44.198.http: Flags [.], ack 459, win 123, options [nop,nop,TS val 818578762 ecr 180571635], length 0
22:38:19.494902 IP 438242.vps-10.com.58582 > 79.170.44.198.http: Flags [R.], seq 852, ack 459, win 123, options [nop,nop,TS val 818578763 ecr 180571635], length 0
22:38:19.495275 IP 79.170.44.198.http > 438242.vps-10.com.58582: Flags [F.], seq 459, ack 852, win 127, options [nop,nop,TS val 180571635 ecr 818578760], length 0
22:38:19.495288 IP 438242.vps-10.com.58582 > 79.170.44.198.http: Flags [R], seq 2654762047, win 0, length 0
22:38:19.742586 ARP, Request who-has 462968.vps-10.com tell 46.32.253.254, length 46
22:38:19.742887 IP 438242.vps-10.com.52038 > 46.32.224.30.domain: 31106+ PTR? 202.253.32.46.in-addr.arpa. (44)
22:38:19.743297 IP 46.32.224.30.domain > 438242.vps-10.com.52038: 31106 1/0/0 PTR 462968.vps-10.com. (75)
22:38:19.779728 IP 766660.vps-10.com.netbios-dgm > 46.32.231.255.netbios-dgm: NBT UDP PACKET(138)
22:38:19.780021 IP 438242.vps-10.com.37460 > 46.32.224.31.domain: 24907+ PTR? 120.231.32.46.in-addr.arpa. (44)
22:38:19.780364 IP 46.32.224.31.domain > 438242.vps-10.com.37460: 24907 1/0/0 PTR 766660.vps-10.com. (75)
22:38:20.014739 ARP, Request who-has 110430.vps-10.com tell 396511.vps-10.com, length 46
22:38:20.014993 IP 438242.vps-10.com.56569 > 46.32.224.29.domain: 38282+ PTR? 29.230.32.46.in-addr.arpa. (43)
22:38:20.026209 IP 46.32.224.29.domain > 438242.vps-10.com.56569: 38282 1/0/0 PTR 396511.vps-10.com. (74)
22:38:20.104121 ARP, Request who-has 098358.vps-10.com tell 46.32.253.254, length 46
22:38:20.104327 IP 438242.vps-10.com.51703 > 46.32.224.30.domain: 38150+ PTR? 160.252.32.46.in-addr.arpa. (44)
22:38:20.115286 IP 46.32.224.30.domain > 438242.vps-10.com.51703: 38150 1/0/0 PTR 098358.vps-10.com. (75)
22:38:20.131807 ARP, Request who-has 46.32.231.254 tell 338132.vps-10.com, length 46
22:38:20.131981 IP 438242.vps-10.com.45414 > 46.32.224.31.domain: 38185+ PTR? 254.231.32.46.in-addr.arpa. (44)
22:38:20.132401 IP 46.32.224.31.domain > 438242.vps-10.com.45414: 38185 NXDomain 0/1/0 (113)
22:38:20.132485 IP 438242.vps-10.com.44905 > 46.32.224.29.domain: 27077+ PTR? 153.231.32.46.in-addr.arpa. (44)
22:38:20.132899 IP 46.32.224.29.domain > 438242.vps-10.com.44905: 27077 1/0/0 PTR 338132.vps-10.com. (75)
22:38:20.186631 ARP, Request who-has 872597.vps-10.com tell 46.32.229.254, length 46
22:38:20.186917 IP 438242.vps-10.com.55763 > 46.32.224.30.domain: 32048+ PTR? 110.229.32.46.in-addr.arpa. (44)
22:38:20.198909 IP 46.32.224.30.domain > 438242.vps-10.com.55763: 32048 1/0/0 PTR 872597.vps-10.com. (75)
22:38:20.243688 ARP, Request who-has 713752.vps-10.com tell 46.32.229.254, length 46
22:38:20.243927 IP 438242.vps-10.com.40182 > 46.32.224.31.domain: 62881+ PTR? 123.229.32.46.in-addr.arpa. (44)
22:38:20.255278 IP 46.32.224.31.domain > 438242.vps-10.com.40182: 62881 1/0/0 PTR 713752.vps-10.com. (75)
22:38:20.698551 IP 739070.vps-10.com.17500 > 255.255.255.255.17500: UDP, length 207
22:38:20.698753 IP 739070.vps-10.com.17500 > 46.32.229.255.17500: UDP, length 207
22:38:20.698865 IP 438242.vps-10.com.60621 > 46.32.224.29.domain: 28996+ PTR? 187.228.32.46.in-addr.arpa. (44)
22:38:20.711155 IP 46.32.224.29.domain > 438242.vps-10.com.60621: 28996 1/0/0 PTR 739070.vps-10.com. (75)
22:38:20.711287 IP 438242.vps-10.com.51002 > 46.32.224.30.domain: 56702+ PTR? 255.229.32.46.in-addr.arpa. (44)
22:38:20.711805 IP 46.32.224.30.domain > 438242.vps-10.com.51002: 56702 NXDomain 0/1/0 (113)
22:38:20.870907 ARP, Request who-has 46.32.231.254 tell 431537.vps-10.com, length 46
22:38:20.871148 IP 438242.vps-10.com.49642 > 46.32.224.31.domain: 36298+ PTR? 225.231.32.46.in-addr.arpa. (44)
22:38:20.881984 IP 46.32.224.31.domain > 438242.vps-10.com.49642: 36298 1/0/0 PTR 431537.vps-10.com. (75)
22:38:21.422855 ARP, Request who-has 859725.vps-10.com tell 46.32.255.254, length 46
22:38:21.716279 IP 143925.vps-10.com.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 45.165.13.182.in-addr.arpa. (44)
22:38:21.818374 ARP, Request who-has 216584.vps-10.com tell 46.32.229.254, length 46
22:38:21.818669 IP 438242.vps-10.com.37480 > 46.32.224.29.domain: 46342+ PTR? 149.229.32.46.in-addr.arpa. (44)
22:38:21.829597 IP 46.32.224.29.domain > 438242.vps-10.com.37480: 46342 1/0/0 PTR 216584.vps-10.com. (75)
22:38:21.954515 ARP, Request who-has 695851.vps-10.com tell 46.32.229.254, length 46
22:38:21.954821 IP 438242.vps-10.com.50961 > 46.32.224.30.domain: 46463+ PTR? 185.229.32.46.in-addr.arpa. (44)
22:38:21.958532 IP 46.70.81.144.4112 > 839107.vps-10.com.telnet: Flags [S], seq 3826893480, win 5808, options [mss 1452,sackOK,TS val 4652521 ecr 0,nop,wscale 0], length 0
22:38:21.966495 IP 46.32.224.30.domain > 438242.vps-10.com.50961: 46463 1/0/0 PTR 695851.vps-10.com. (75)
22:38:21.966701 IP 438242.vps-10.com.32988 > 46.32.224.31.domain: 6600+ PTR? 187.229.32.46.in-addr.arpa. (44)
22:38:21.977906 IP 46.32.224.31.domain > 438242.vps-10.com.32988: 6600 1/0/0 PTR 839107.vps-10.com. (75)
22:38:21.978063 IP 438242.vps-10.com.35347 > 46.32.224.29.domain: 23014+ PTR? 144.81.70.46.in-addr.arpa. (43)
22:38:21.993013 IP 46.32.224.29.domain > 438242.vps-10.com.35347: 23014 NXDomain 0/1/0 (103)
22:38:22.337879 ARP, Request who-has 098358.vps-10.com tell 46.32.253.254, length 46
22:38:22.693625 ARP, Request who-has 46.32.253.254 tell 659708.vps-10.com, length 46
22:38:22.693918 IP 438242.vps-10.com.43769 > 46.32.224.30.domain: 28998+ PTR? 13.253.32.46.in-addr.arpa. (43)
22:38:22.704857 IP 46.32.224.30.domain > 438242.vps-10.com.43769: 28998 1/0/0 PTR 659708.vps-10.com. (74)
22:38:22.717814 IP 143925.vps-10.com.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 45.165.13.182.in-addr.arpa. (44)
22:38:23.186834 IP 634087.vps-10.com.17500 > 255.255.255.255.17500: UDP, length 162
22:38:23.187090 IP 438242.vps-10.com.48930 > 46.32.224.31.domain: 23024+ PTR? 74.231.32.46.in-addr.arpa. (43)
22:38:23.187414 IP 46.32.224.31.domain > 438242.vps-10.com.48930: 23024 1/0/0 PTR 634087.vps-10.com. (74)
22:38:23.187695 IP 634087.vps-10.com.17500 > 46.32.231.255.17500: UDP, length 162
22:38:23.203152 ARP, Request who-has 617701.vps-10.com tell 110430.vps-10.com, length 46
22:38:23.203407 IP 438242.vps-10.com.42019 > 46.32.224.29.domain: 9637+ PTR? 89.230.32.46.in-addr.arpa. (43)
22:38:23.213950 IP 46.32.224.29.domain > 438242.vps-10.com.42019: 9637 1/0/0 PTR 617701.vps-10.com. (74)
22:38:23.421681 ARP, Request who-has 859725.vps-10.com tell 46.32.255.254, length 46
22:38:23.454061 IP 46.70.81.144.4116 > vps.lloydcobb.co.uk.telnet: Flags [S], seq 3822910816, win 5808, options [mss 1452,sackOK,TS val 4652670 ecr 0,nop,wscale 0], length 0
22:38:23.454281 IP 438242.vps-10.com.59031 > 46.32.224.30.domain: 57610+ PTR? 192.229.32.46.in-addr.arpa. (44)
22:38:23.464936 IP 46.32.224.30.domain > 438242.vps-10.com.59031: 57610 1/0/0 PTR vps.lloydcobb.co.uk. (77)
22:38:23.534220 ARP, Request who-has 819719.vps-10.com tell 46.32.229.254, length 46
22:38:23.534486 IP 438242.vps-10.com.43135 > 46.32.224.31.domain: 7610+ PTR? 219.229.32.46.in-addr.arpa. (44)
22:38:23.546457 IP 46.32.224.31.domain > 438242.vps-10.com.43135: 7610 1/0/0 PTR 819719.vps-10.com. (75)
22:38:23.574848 ARP, Request who-has 46.32.229.254 tell 246506.vps-10.com, length 46
22:38:23.575110 IP 438242.vps-10.com.48549 > 46.32.224.29.domain: 5481+ PTR? 232.229.32.46.in-addr.arpa. (44)
22:38:23.586051 IP 46.32.224.29.domain > 438242.vps-10.com.48549: 5481 1/0/0 PTR 246506.vps-10.com. (75)
22:38:23.741915 ARP, Request who-has 462968.vps-10.com tell 46.32.253.254, length 46
22:38:24.195160 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54431 > 438242.vps-10.com.ssh: Flags [P.], seq 1:49, ack 320, win 7602, options [nop,nop,TS val 10333552 ecr 818578228], length 48
22:38:24.195382 IP 438242.vps-10.com.ssh > 82-69-23-250.dsl.in-addr.zen.co.uk.54431: Flags [P.], seq 320:368, ack 49, win 213, options [nop,nop,TS val 818579938 ecr 10333552], length 48
22:38:24.201610 ARP, Request who-has 826008.vps-10.com tell 110430.vps-10.com, length 46
22:38:24.201831 IP 438242.vps-10.com.51252 > 46.32.224.30.domain: 27111+ PTR? 218.230.32.46.in-addr.arpa. (44)
22:38:24.212880 IP 46.32.224.30.domain > 438242.vps-10.com.51252: 27111 1/0/0 PTR 826008.vps-10.com. (75)
22:38:24.224267 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54431 > 438242.vps-10.com.ssh: Flags [.], ack 368, win 7599, options [nop,nop,TS val 10333559 ecr 818579938], length 0
22:38:24.649532 IP 82-69-23-250.dsl.in-addr.zen.co.uk.54431 > 438242.vps-10.com.ssh: Flags [P.], seq 49:97, ack 368, win 7602, options [nop,nop,TS val 10333666 ecr 818579938], length 48

Offline asaphxiix

  • *
  • Posts: 723
Re: Announce server issues - assistance requested
« Reply #8 on: August 27, 2013, 05:35:35 AM »
Thank you for that.

So here too the only mentions of anything with the word 'servers' in it are:
22:38:19.384044 IP 438242.vps-10.com.57364 > 46.32.224.30.domain: 63297+ A? servers.experimental.simutrans. (48)
22:38:19.384093 IP 438242.vps-10.com.57364 > 46.32.224.30.domain: 8004+ AAAA? servers.experimental.simutrans. (48)
22:38:19.384559 IP 46.32.224.30.domain > 438242.vps-10.com.57364: 63297 NXDomain 0/1/0 (123)
22:38:19.471530 IP 46.32.224.30.domain > 438242.vps-10.com.57364: 8004 NXDomain 0/1/0 (123)
and
22:38:19.471639 IP 438242.vps-10.com.60828 > 46.32.224.31.domain: 63265+ A? servers.experimental.simutrans.vps-10.com. (59)
22:38:19.471671 IP 438242.vps-10.com.60828 > 46.32.224.31.domain: 2823+ AAAA? servers.experimental.simutrans.vps-10.com. (59)
22:38:19.472117 IP 46.32.224.31.domain > 438242.vps-10.com.60828: 63265 1/0/0 A 79.170.44.198 (75)
22:38:19.472129 IP 46.32.224.31.domain > 438242.vps-10.com.60828: 2823 0/1/0 (124)

indeed we can see the request is being made for a bad domain, no .org here.
Strangely enough, for the second A request, # 63265 an answer is given back 79.170.44.198, but I don't see how this could be the right answer. Still, some http packets are exchanged with this address, but I would need a more verbose capture to view the http headers. you can capture them by:
tcpdump -i <interface> -w <filename>.

(sorry, I should have asked for this at first).

note also that this dump shows your own IP address as an ssh client.

Offline TurfIt

  • Dev Team, Coder/patcher
  • Devotee
  • *
  • Posts: 1326
Re: Announce server issues - assistance requested
« Reply #9 on: August 27, 2013, 06:25:16 PM »
Are you by chance compiling your server with USE_IP4_ONLY defined?
network/network.cc:112 contains:
Code: [Select]
#ifdef USE_IP4_ONLY
// Network load. Address format e.g.: "128.0.0.1:13353"
char address[32];

... manipulate cp and stuff into address

cp = address;

...

theHost = gethostbyname( cp );
which looks rather suspicious...

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #10 on: August 27, 2013, 06:40:38 PM »
Asaph - the output is now this, which is rather garbled:

Code: [Select]
Ôò¡          ÿÿ      òR÷£ j   j    Çwp RT ·‹® E \A1@ @. çÞRG ÔlÂ%ÞñFQ(—P ”l¥  ì-¤Ò¾÷"û\j-iêD…ÐP§’DHð}ƒµHÙ†·ÆÕšf_Û˜·'åÖ.NÊο€kB§½ òR6¤ ª   ª    Çwp RT ·‹® E œA2@ @ŒÃ. çÞRG ÔlÂ%ß%FQ(—P ”lå  Ï˺ͦÔÝÙ¶3åÇãív<”sõ _øåOBUþS
›Õ¯´F1÷‘jQšGe­‘[ ;Èý·]Xt²ëb{Ë—*;µÞµ‰¹TuüPó/U_Ì ¾ƒ„ÉÖ.ƒ´‡ ‚È0ó ¡÷QåÊ0"²È04
v2 òRg¤ j   j    Çwp RT ·‹® E \A3@ @. çÞRG ÔlÂ%ß™FQ(—P ”l¥  ±+I}r
f·º4˜Â¿Ñ˾ü„%=û}^ÏàH&Çt£Bxl@¿CV0¿–ªÒ—ʽ  òRûÌ <   <   RT ·‹® Çwp  E  (7þ@ y]{RG. çÞÔl FQ(—Â%ß%P?õÒ         òR×Ï <   <   RT ·‹® Çwp  E  (7ÿ@ y]zRG. çÞÔl FQ(—Â%ßÍP?ËT         òRXy <   <   ÿÿÿÿÿÿRT =y¬   RT =y¬. åE      . åþ                   òRÙq @   @    ^  üRT $±A E  2!  ™J. ü3à  üöÐë ËHD         wpad    òRˆ @   @    ^  üRT $±A E  2"  ™I. ü3à  üöÐë ËHD         wpad    òR/c <   <   ÿÿÿÿÿÿRT MW   RT MW. æO      . æà                   òRæ§
 E   E    ^  üRT Å«º E  7Z´  h. çÖà  üø$ë #Zì2         win374078    òR¡ \   \   ÿÿÿÿÿÿRT $±A E  N#  €Ï. ü3. ýÿ ‰ ‰ :ÂI¤<        FHFAEBEECACACACACACACACACACACAAA     òRg4 E   E    ^  üRT Å«º E  7Zµ  h. çÖà  üø$ë #Zì2         win374078    òRò <   <   ÿÿÿÿÿÿ Çwp     Çwp . ÿþ      . ÿ                   !òRØ  \   \   ÿÿÿÿÿÿRT Å«º E  NZ¾  €³Ê. çÖ. çÿ ‰ ‰ :²>¯¡        FHEJEODDDHDEDADHDICACACACACACAAA    !òRSž <   <   ÿÿÿÿÿÿ Çwp     Çwp . ýþ      . üM                  !òRM \   \   ÿÿÿÿÿÿRT $±A E  N$  €Ï. ü3. ýÿ ‰ ‰ :ÂI¤<        FHFAEBEECACACACACACACACACACACAAA    !òR&‹ <   <   ÿÿÿÿÿÿRT MW   RT MW. æO      . æ                  !òR«/
 @   @    ^  üRT SÜD E  2µ  ·E. ä¤à  üÞ'ë À•l         wpad   !òR%i Ñ   Ñ   ÿÿÿÿÿÿRT ø%j E  Ã?”  €Θ. ýÝÿÿÿÿD\D\ ¯S0{"host_int": 271321214, "version": [1, 8], "displayname": "271321214", "port": 17500, "namespaces": [105208240, 105208258, 105181895, 106374361, 105377631, 174744351]}!òRÅt Ñ   Ñ   ÿÿÿÿÿÿRT ø%j E  Ã?•  €¢w. ýÝ. ýÿD\D\ ¯'{"host_int": 271321214, "version": [1, 8], "displayname": "271321214", "port": 17500, "namespaces": [105208240, 105208258, 105181895, 106374361, 105377631, 174744351]}!òR“x \   \   ÿÿÿÿÿÿRT Å«º E  NZà €³Å. çÖ. çÿ ‰ ‰ :²>¯¡        FHEJEODDDHDEDADHDICACACACACACAAA    !òR · @   @    ^  üRT SÜD E  2¶  ·D. ä¤à  üÞ'ë À•l         wpad   !òRëÞ \   \   ÿÿÿÿÿÿRT SÜD E  N·  €. ä¤. åÿ ‰ ‰ :©mì§        FHFAEBEECACACACACACACACACACACAAA    "òRH5 <   <   ÿÿÿÿÿÿRT µ=   RT µ=. üT      . ýþ                  "òRø{ \   \   ÿÿÿÿÿÿRT $±A E  N%  €Ï. ü3. ýÿ ‰ ‰ :ÂI¤<        FHFAEBEECACACACACACACACACACACAAA    "òR3v j   j   RT ·‹® Çwp  E  \8@ y]BRG. çÞÔt 3=\ûÚß3P?Ásü  Ó]ðƒ÷I Á“¯éËŸS­„~¹”#ꪻë-‘yRtGÇrVq_X­
„_×5½e·‘7]"òR} š   š    Çwp RT ·‹® E Œ ~@ @Á‡. çÞRG ÔtûÚß33=\BP ”lÕ  °Ã4¢2«†™aaîìkyÿõøô?ý„2›ÃÞSš\'UäûÄm äg ´0V7×Q§ø¥ª‡ªHƒyq‹'î(rºƒÙ9-Èdº_¶%+€¨¨Ê’KÝŠF5 O -¯½)Ä"òR€ T   T    Çwp RT ·‹® E  Fð@ @&Z. çÞ. à‹ 5 2$¯        bridgewater-brunelmeuk   "òRÚ€ T   T    Çwp RT ·‹® E  Fð@ @&Y. çÞ. à‹ 5 2$ð"        bridgewater-brunelmeuk   "òRñƒ ¤   ¤   RT ·‹® Çwp  E  –  @ >. à. çÞ 5‹ ‚çÍð"€      bridgewater-brunelmeuk   À     Ddns1netplaninternetcoÀ"helpdesk
netsecretsÀKwü”Š  *0   :€ Q€"òR„ d   d   RT ·‹® Çwp  E  V  @ >Z. à. çÞ 5‹ BX+¯€      bridgewater-brunelmeuk   À   O . çÞ"òR¬„ T   T    Çwp RT ·‹® E  Fð@ @&Y. çÞ. à°H 5 2$‚Œi        bridgewater-brunelmeuk   "òR„ T   T    Çwp RT ·‹® E  Fð@ @&X. çÞ. à°H 5 2$‚ ·        bridgewater-brunelmeuk   "òR?† d   d   RT ·‹® Çwp  E  V  @ >Y. à. çÞ 5°H BŠŠŒi€      bridgewater-brunelmeuk   À   Qw . çÞ"òRG† ¤   ¤   RT ·‹® Çwp  E  –  @ >. à. çÞ 5°H ‚${ ·€      bridgewater-brunelmeuk   À     Ddns1netplaninternetcoÀ"helpdesk
netsecretsÀKwü”Š  *0   :€ Q€"òRî‰ ê   ê    Çwp RT ·‹® E Ü @ @Á6. çÞRG ÔtûÚß—3=\BP ”m%  *á•+U­ÖnDÕÃZœs̆ŒßWòaqÝ'6~]œYêY«f|´•Ý–!
É‚Ö^*Æ”¿vE›Cg°<”Afjm“ˆ&¶Î*eA 4ìî\B ‰¡­xE×&_ç—¯©8 –®çÚƒ^Tð¨˜E¶>èSfñŒ°" Ñ
f°™Ý¥7
GÐÙ™‘Ù]ÒÝÓN#±žpòZÀÌڿꞢ×}›Ñ8ÏÅl×WAƒÅ"òR6 Z   Z    Çwp RT ·‹® E  Lð@ @&U. çÞ. àÛ× 5 8$†         servers experimental simutrans   "òRM Z   Z    Çwp RT ·‹® E  Lð@ @&T. çÞ. àÛ× 5 8$†¸n        servers experimental simutrans   "òR  ¥   ¥   RT ·‹® Çwp  E  —  @ >. à. çÞ 5Û× ƒâT ƒ      servers experimental simutrans       
 @a root-serversnet nstld verisign-grscom wý4M    „ :€ Q€"òR ¥   ¥   RT ·‹® Çwp  E  —  @ >. à. çÞ 5Û× ƒ6[¸nƒ      servers experimental simutrans       
 @a root-serversnet nstld verisign-grscom wý4M    „ :€ Q€"òRk e   e    Çwp RT ·‹® E  Wð@ @&H. çÞ. à±" 5 C$’Ì•        servers experimental simutransvps-10com   "òR€ e   e    Çwp RT ·‹® E  Wð@ @&G. çÞ. à±" 5 C$’´å        servers experimental simutransvps-10com   "òR4’ u   u   RT ·‹® Çwp  E  g  @ >I. à. çÞ 5±" Sc£Ì•€      servers experimental simutransvps-10com   À    L Oª,Æ"òRB’ ¦   ¦   RT ·‹® Çwp  E  ˜  @ >. à. çÞ 5±" „û´偀      servers experimental simutransvps-10com   À+   
 5nsmainnameserverÀ2
hostmasterÀJwý4• Q€ :€ $ê   *0"òR|“ J   J    Çwp RT ·‹® E  <(@ @€1. çÞOª,Æî, P[Ø      9’  ´
1êð    "òRj² <   <   RT ·‹® Çwp  E  (8@ y]uRG. çÞÔt 3=\BûÚàKP?{ÃÑ        "òR¾ J   J   RT ·‹® Çwp  E  <  @ 7±MOª,Æ. çÞ Pî,ñ?,Š[Ø
 8_Р ´
Dù11êð"òR)¾ B   B    Çwp RT ·‹® E  4(@ @€8. çÞOª,Æî, P[Ø
ñ?,‹€ s’•  
1êðDù1"òR×¾ •  •   Çwp RT ·‹® E ‡(@ @|ä. çÞOª,Æî, P[Ø
ñ?,‹€ s•è  
1êðDù1POST /announce HTTP/1.1
User-Agent: Simutrans/r1108
Host: servers.experimental.simutrans.org:80
Content-Type: application/x-www-form-urlencoded
Content-Length: 680

&dns=bridgewater-brunel.me.uk&port=13353&aiv=900&st=1&rev=1108&ver=Simutrans "112" "." "3" " Experimental" " " (r1108) built "Aug 23 2013"&pak=Pak128.Britain-Ex-0.9.0&start=1,1785&name=Bridgewater-Brunel&comments=This%20server%20is%20set%20up%20to%20run%20large%20Pak128.Britain-Ex%20games%20on%20a%20VPS%20with%203Gb%20of%20RAM%20available%20and%20one%20dedicated%20core.&email=jamespetts%40yahoo.com&pakurl=https%3A%2F%2Fgithub.com%2Fdownloads%2Fjamespetts%2Fsimutrans-pak128.britain%2FPak128.Britain-Ex.zip&infurl=http%3A%2F%2Fwww.bridgewater-brunel.me.uk&time=9,2009&size=2048,1664&active=11&locked=3&clients=0&towns=469&citizens=12972644&factories=293&convoys=5170&stops=5251"òRcê B   B   RT ·‹® Çwp  E  4Õ·@ 7۝Oª,Æ. çÞ Pî,ñ?,‹[Û`€ ÃL  
Dù<1êð"òRVë B   B   RT ·‹® Çwp  E  4Õ¹@ 7Û›Oª,Æ. çÞ Pî,ñ?.U[Û`€ Á  
Dù<1êð"òRbë     RT ·‹® Çwp  E þÕ¸@ 7ÙÒOª,Æ. çÞ Pî,ñ?,‹[Û`€ „<  
Dù<1êðHTTP/1.1 404 Not Found
Date: Tue, 27 Aug 2013 18:38:26 GMT
Server: Apache/2
Content-Length: 292
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /announce was not found on this server.</p>
<hr>
<address>Apache/2 Server at servers.experimental.simutrans.org Port 80</address>
</body></html>
"òR‰ë N   N    Çwp RT ·‹® E  @(@ @€*. çÞOª,Æî, P[Û`ñ?,‹° s’¡  
1êðDù<
ñ?.Uñ?.V"òR¦ë B   B    Çwp RT ·‹® E  4( @ @€5. çÞOª,Æî, P[Û`ñ?.V€ {’•  
1êðDù<"òR'î B   B    Çwp RT ·‹® E  4(!@ @€4. çÞOª,Æî, P[Û`ñ?.V€ {’•  
1êðDù<"òR‡  \   \   ÿÿÿÿÿÿRT Å«º E  NZÈ  €³À. çÖ. çÿ ‰ ‰ :²>¯¡        FHEJEODDDHDEDADHDICACACACACACAAA    "òRð
 <   <   ÿÿÿÿÿÿ Çwp     Çwp . ýþ      . ýó                  "òRü
 \   \   ÿÿÿÿÿÿRT SÜD E  N¿  €ü. ä¤. åÿ ‰ ‰ :©mì§        FHFAEBEECACACACACACACACACACACAAA    "òR7ø <   <   ÿÿÿÿÿÿRT MW   RT MW. æO      . æ*                  #òRV" <   <   ÿÿÿÿÿÿ Çwp     Çwp . ýþ      . ýÒ                  #òR  <   <   ÿÿÿÿÿÿ Çwp     Çwp . ÿþ      . ÿ                   #òRZr E   E    ^  üRT Å«º E  7ZÉ  gú. çÖà  üø$ë #FJØ         win374078   #òRiû E   E    ^  üRT Å«º E  7ZË  gø. çÖà  üø$ë #FJØ         win374078   #òR3 \   \   ÿÿÿÿÿÿRT SÜD E  NÇ  €ô. ä¤. åÿ ‰ ‰ :©mì§        FHFAEBEECACACACACACACACACACACAAA    #òRr˜ <   <   ÿÿÿÿÿÿRT MW   RT MW. æO      . æd                  #òRž <   <   ÿÿÿÿÿÿRT MW   RT MW. æO      . æÇ                  #òRSg ª  ª  ÿÿÿÿÿÿRT #t¢ E œjÄ  €¢Ô. çx. çÿ Š Šˆ ™Ò. çx Šr   FHEJEODHDGDGDGDGDACACACACACACAAA  FHEPFCELEHFCEPFFFACACACACACACAAA ÿSMB%                   ÿþ      Ò               \ Ò \      é \MAILSLOT\Rhino\FVReg  Ò   WIN766660-ceb29ba6    WIN766660 VcnK1GFU0qz+vxwHXplygXat4g+cXuw/hInYsImFzGLXZvi0RJAa332dDz61o6I69w/ICqS5K36AKM7GcZrSlchesl68yp/AjmsFNGZDqvgvxmEDRczlw0k8ESDtQbNl1dioNXgCca0ojhdj4Ys4rJV4qSMbZwMHcJlse4fnjXQ= #òR5… <   <   ÿÿÿÿÿÿ Çwp     Çwp . ýþ      . üè                  #òR S
 \   \   ÿÿÿÿÿÿRT Å«º E  NZÏ  €³¹. çÖ. çÿ ‰ ‰ :²=¯¢        FHEJEODDDHDEDADHDICACACACACACAAA    $òR7 ¥   ¥   ÿÿÿÿÿÿRT Rx E  —A¹  €äÈ. å´ÿÿÿÿD\D\ ƒ’×{"host_int": 339253252, "version": [1, 8], "displayname": "339253252", "port": 17500, "namespaces": [173081698, 173075468]}$òR€8 ¥   ¥   ÿÿÿÿÿÿRT Rx E  —Aº  €Ч. å´. åÿD\D\ ƒ~·{"host_int": 339253252, "version": [1, 8], "displayname": "339253252", "port": 17500, "namespaces": [173081698, 173075468]}$òR)h \   \   ÿÿÿÿÿÿRT Å«º E  NZØ  €³°. çÖ. çÿ ‰ ‰ :²=¯¢        FHEJEODDDHDEDADHDICACACACACACAAA    $òRj @   @    ^  üRT $±A E  2)  ™B. ü3à  üöÐë åù)Р        wpad   $òRè»
 @   @    ^  üRT $±A E  2*  ™A. ü3à  üöÐë åù)Р        wpad   %òRd  @   @    ^  üRT _na E  2lf  Z4. äà  üÐøë ¸Y•w         wpad   %òRŒ“ \   \   ÿÿÿÿÿÿRT $±A E  N+  €Ï . ü3. ýÿ ‰ ‰ :ÂH¤=        FHFAEBEECACACACACACACACACACACAAA    %òR¯ñ j   j   RT ·‹® Çwp  E  \8@ y]=RG. çÞÔl FQ(—Â%ßÍP?Ëçr  —«MaC5‚.„œ7Öq>T¼œÆš%&<ðn#¾9¾‡évK†‘®Nâk

TurfIt - I am not compiling with USE_IP4_ONLY defined, so I do not think that this can be the issue; thank you for the suggestion, however.

Offline TurfIt

  • Dev Team, Coder/patcher
  • Devotee
  • *
  • Posts: 1326
Re: Announce server issues - assistance requested
« Reply #11 on: August 27, 2013, 06:57:24 PM »
Looking further, in the non IP4 only part:
Code: [Select]
else {
// Copy the address part
tstrncpy( address, cp, cp2 - cp > 31 ? 31 : cp2 - cp + 1 );
}
Still suspicious...

rev 3742 changed address[32] to address[1024], but the 31 above remains. Either somewhere later is limited to 32 or this was forgotten. So, you can either shorten the name you're trying to use, or see if this can be enlarged...

This whole section of code looks designed for numeric ip addresses, yet names are getting in.

Offline asaphxiix

  • *
  • Posts: 723
Re: Announce server issues - assistance requested
« Reply #12 on: August 27, 2013, 07:00:11 PM »
James, could you kindly share the file on a site? So I can open it with Wireshark (a program to decode these). I'm trying to work on getting a capture of a standard server announcement.

Code: [Select]
POST /announce HTTP/1.1
User-Agent: Simutrans/r1108
Host: servers.experimental.simutrans.org:80
Content-Type: application/x-www-form-urlencoded
Content-Length: 680

&dns=bridgewater-brunel.me.uk&port=13353&aiv=900&st=1&rev=1108&ver=Simutrans "112" "." "3" " Experimental" " " (r1108) built "Aug 23 2013"&pak=Pak128.Britain-Ex-0.9.0&start=1,1785&name=Bridgewater-Brunel&comments=This%20server%20is%20set%20up%20to%20run%20large%20Pak128.Britain-Ex%20games%20on%20a%20VPS%20with%203Gb%20of%20RAM%20available%20and%20one%20dedicated%20core.&email=jamespetts%40yahoo.com&pakurl=https%3A%2F%2Fgithub.com%2Fdownloads%2Fjamespetts%2Fsimutrans-pak128.britain%2FPak128.Britain-Ex.zip&infurl=http%3A%2F%2Fwww.bridgewater-brunel.me.uk&time=9,2009&size=2048,1664&active=11&locked=3&clients=0&towns=469&citizens=12972644&factories=293&convoys=5170&stops=5251"òRcê B   B   RT ·‹® Çwp  E  4Õ·@ 7۝Oª,Æ. çÞ Pî,ñ?,‹[Û`€ ÃL  

Code: [Select]
HTTP/1.1 404 Not Found
Date: Tue, 27 Aug 2013 18:38:26 GMT
Server: Apache/2
Content-Length: 292
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /announce was not found on this server.</p>
<address>Apache/2 Server at servers.experimental.simutrans.org Port 80</address>
</body></html>


Either with all the DNS and redirection weirdness, the game server somehow reaches a "fake" server which still answers as servers.experimental.simutrans.org, or the problem is on the server side. Unless the post request should be on a different URL than /announce ?




Offline TurfIt

  • Dev Team, Coder/patcher
  • Devotee
  • *
  • Posts: 1326
Re: Announce server issues - assistance requested
« Reply #13 on: August 27, 2013, 07:05:24 PM »
The 'fake' server is seen above. Request for 'servers.experimental.simutrans.vps-10.com.' is returning 79.170.44.198 rather than NXDomain. Bad bad evil vps-10.com!

Offline asaphxiix

  • *
  • Posts: 723
Re: Announce server issues - assistance requested
« Reply #14 on: August 27, 2013, 07:26:52 PM »
Indeed - this address is a default page of the vendor. So the problem is indeed in the DNS request as suggested above - the server tries for a bad domain. I've seen this happen on my machine as well, so I don't think it's being truncated anywhere outside the game.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #15 on: August 27, 2013, 08:17:54 PM »
Thank you very much for all your help. Asaph: here is the raw dump file. I hope that it helps.

TurfIt - it is interesting that you write that the code seems designed for numeric IP addresses: when the previous announce server had a fixed IP, using this is what enabled it to work. Do you think that modifying 31 to 1023 will assist here?

Offline TurfIt

  • Dev Team, Coder/patcher
  • Devotee
  • *
  • Posts: 1326
Re: Announce server issues - assistance requested
« Reply #16 on: August 27, 2013, 08:23:35 PM »
Well, something is clearly truncating the name to 31 characters, and that code does just that. Possibly there's more locations doing the truncations, possibly the truncation is necessary in later code. I don't know why the buffer was enlarged from 32 to 1024, while still truncating at 31. Maybe needed, maybe forgotten. You can certainly try changing it...

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #17 on: August 27, 2013, 08:36:55 PM »
Thank you for that insight. This is particularly interesting, as it might explain why the error appears in Experimental but not Standard despite the code being the same (as the name "servers.experimental.simutrans.org" is longer than 30 characters, whereas "servers.simutrans.org" is not). I have modified the 11.x branch with this fix, and it runs without errors, but running a local server does not produce something on the announce server - but that might be because it is registering as 127.0.0.1, which the announce server might find to be invalid. I shall try this in the next release version and see what transpires.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #18 on: August 28, 2013, 09:44:43 PM »
Aha - the truncation thing it was. 11.9 now works. Thank you very much, TurfIt!

Offline prissi

  • Developer
  • Administrator
  • *
  • Posts: 9557
  • Languages: De,EN,JP
Re: Announce server issues - assistance requested
« Reply #19 on: August 28, 2013, 09:51:10 PM »
I enlarge the strcpy for standard as well. Very well hidden bug this!

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Announce server issues - assistance requested
« Reply #20 on: August 28, 2013, 09:53:26 PM »
Indeed - difficult to spot if the default string is in fact below the limit. Do you think that the announce server URL should be configurable in simuconf.tab?

Offline TurfIt

  • Dev Team, Coder/patcher
  • Devotee
  • *
  • Posts: 1326
Re: Announce server issues - assistance requested
« Reply #21 on: August 28, 2013, 11:09:46 PM »
I enlarge the strcpy for standard as well. Very well hidden bug this!
umm. sizeof(address) = sizeof(char*) = 4  (for 32-bit)  no? Sorry. Brainfart...
err_str now subject to buffer overflow...


Do you think that the announce server URL should be configurable in simuconf.tab?
Probably not. If you need to change the server address, you likely know how to recompile. If address easily changeable in a config file, easier for some kiddie to spam some unrelated server somewhere...
« Last Edit: August 31, 2013, 02:03:13 AM by TurfIt »