[messages] [Technical Support & Bugs] Very slow response

Joel Uckelman uckelman at nomic.net
Sun Mar 1 01:28:13 CET 2015


Thus spake dsoukup:
> 
> I ran reset all systems, tried wireless/wired, ran some ping tests
> (average over 250 ms with about 15-30% packet loss), trace routes (see
> below), released/renewed/flushed the connection/DNS and other basic
> tasks, but I have not been able to determine what is going on. Below is
> a recent traceroute to 68.14.242.201 which I believe is the IP address
> for the VASSAL game server. I am definitely not a network guru... Does
> anybody have any thoughts?

One problem I see right away is that you have the wrong IP address.
68.14.242.201 used to be the IP of the game server, but that's not
been the case for over a year now. How did you get that address?

Similarly, two.vassalengine.org used to be the hostname for the game
server, but that also changed about a year ago. The hostname which
we have built into current versions of VASSAL is game.vassalengine.org,
which should resolve to 62.210.178.7.

> Tracing route to two.vassalengine.org [68.14.242.201]
> over a maximum of 30 hops:
> 
> 1 ms	< 1ms	2 ms	homeportal [192.168.1.254]
> *	*	*	Request timed out.
> 21 ms	18 ms	20ms	71.150.32.178
> 20 ms	21 ms	19 ms	12.83.42.129
> 32 ms	32 ms	33 ms	gar27.dlstx.ip.att.net [12.123.16.77]
> 33 ms	31 ms	30 ms	ae-9.r01.dllstx04.us.bb.gin.ntt.net [129.250.8.237]
> *	29 ms	34 ms	ae-1.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.10]
> *	79 ms	*	ae-3.r20.lsanca03.us.bb.gin.ntt.net [129.250.7.69]
> 65 ms	66 ms	67 ms	ae01.r04.lsanca03.us.bb.gin.ntt.net [129.250.5.2]
> 66 ms	67 ms	66 ms	ae-4.r00.lsanca19.us.bb.gin.ntt.net [129.250.6.203]
> 78 ms	*	77 ms	ae-0.cox.comm.lsanca19.us.bb.gin.ntt.net [129.250.194.166]
> 90 ms	98 ms	100 ms	chnddsrj01-ae1.0.rd.ph.cox.net [68.1.5.211]
> *	*	*	Request timed out.
> *	*	*	Request timed out.
> 114 ms	115 ms	109 ms	router.nexiliscom.com [70.167.214.190]
> *	114 ms	116 ms two.vassalengine.org [68.14.242.201].

If this is output you produced _today_, then I want very much to know
what the command you used looked like and what nameservers you're
using, as this indicates a very serious problem someplace.
 
-- 
J.


More information about the messages mailing list