Very slow response

I got a reply from AT&T about the bouncing emails. They claim they’ve removed our mail server from their blacklist now (though without ever providing any explanation for why it was added in the first place…).

I’ve not had the reply I was promised via Twitter yet. Are people on AT&T still having trouble connecting to our server?

Took about 2 minutes after sync complete message for the map to pop up for The Devil’s Cauldron, but after that, all was quick and immediate response on the moves, so it looks like problem solved;-)

This was using the DMZ plus setting that I set up with you, right? If so, it might be that this is what’s working. Since I have had no issues to date, I am going to post that procedure as a workaround for others that might be having issues without it.

Is anyone still having this problem?

Yes.

I can’t play live games anymore. It is taking 3 minutes to send a message and get a response. I thought it was because the X-Wing players were bogging down the server.

But during the daytime, I am finding it taking long to upload files. It took 3 minutes to upload a 44KB file (thumbnail) for a Vassal module. It is a killer to upload the 5-10MB .vmod files, the screenshot (about 200 KB) and the thumbnail. Heck, it takes a long time, just to bring up the module page.

I have no idea how to even complain to AT&T. I’m not that tech savvy. Is there some standard form I could send and is there an address I could send it to?

Still having problems also. Only time of day I can expect to join/play games smoothly is past 2am central. Anywhere remotely close to prime time takes 8+ minutes to join a game

Thus spake shazbot:

Still having problems also. Only time of day I can expect to join/play
games smoothly is past 2am central. Anywhere remotely close to prime
time takes 8+ minutes to join a game

What did AT&T’s tech support say when you called them?


J.

Thus spake airjudden:

I have no idea how to even complain to AT&T.

Call their tech support.


J.

I cant even get on the website

Trace below

We are getting stuck on your end

C:\Users\Tim>tracert vassalengine.org

Tracing route to vassalengine.org [62.210.178.7]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]

2 36 ms 35 ms 25 ms 70-138-80-3.lightspeed.hstntx.sbcglobal.net
[70.

138.80.3]

3 26 ms 24 ms 25 ms 71.144.129.18

4 28 ms 26 ms 27 ms 12.83.36.5

5 55 ms 49 ms 52 ms ggr3.dlstx.ip.att.net [12.122.139.17]

6 49 ms 48 ms 53 ms 192.205.37.50

7 70 ms 69 ms 69 ms ash-bb3-link.telia.net [80.91.252.121]

8 160 ms 159 ms 161 ms prs-bb3-link.telia.net [80.91.251.242]

9 159 ms 158 ms 166 ms prs-b8-link.telia.net [213.155.131.1]

10 152 ms 154 ms 153 ms online-ic-305116-prs-b8.c.telia.net
[62.115.40.8

6]

11 * * * Request timed out.

12 149 ms 153 ms 148 ms one.vassalengine.org [62.210.178.7]

Trace complete.

C:\Users\Tim>

From: messages [mailto:messages-bounces@vassalengine.org] On Behalf Of Joel
Uckelman
Sent: Friday, April 03, 2015 7:19 AM
To: The mailing list for VASSAL
Subject: Re: [messages] [Technical Support & Bugs] Very slow response

Thus spake airjudden:

I have no idea how to even complain to AT&T.

Call their tech support.


J.

Thus spake “Tim McCarron”:

I cant even get on the website

Trace below

We are getting stuck on your end

Which part of that trace makes you think the problem is on the VASSAL
server end?


J.

I noticed just now that I have a machine for which the route from it to vassalengine.org goes via Telia but not via AT&T—this happens to be my server in Tucson which is on a Cox business DSL line. This is what I see from traceroute:

[uckelman@charybdis ~]$ traceroute vassalengine.org
traceroute to vassalengine.org (62.210.178.7), 30 hops max, 60 byte packets
1 wsip-68-14-242-193.ph.ph.cox.net (68.14.242.193) 0.454 ms 0.384 ms 0.410 ms
2 * * *
3 172.21.3.164 (172.21.3.164) 10.453 ms 10.524 ms 10.461 ms
4 bellcorc02-te-0-0-0-5.ph.ph.cox.net (70.169.72.188) 28.259 ms 38.590 ms 38.470 ms
5 ae56.bar1.Phoenix1.Level3.net (4.31.188.61) 14.759 ms 14.737 ms 14.677 ms
6 * ae-2-70.edge1.LosAngeles9.Level3.net (4.69.144.74) 24.539 ms 24.395 ms
7 * ae-3-80.edge1.LosAngeles9.Level3.net (4.69.144.138) 24.818 ms 24.711 ms
8 Telia-level3-4x10G.LosAngeles.Level3.net (4.68.70.130) 23.942 ms 23.845 ms 23.577 ms
9 nyk-bb1-link.telia.net (213.155.135.116) 95.336 ms ash-bb3-link.telia.net (213.248.80.9) 78.011 ms nyk-bb1-link.telia.net (213.155.135.116) 95.197 ms
10 prs-bb2-link.telia.net (213.155.135.6) 185.077 ms prs-bb3-link.telia.net (213.155.135.4) 195.293 ms prs-bb3-link.telia.net (80.91.253.121) 194.463 ms
11 prs-b8-link.telia.net (62.115.138.139) 174.600 ms 174.458 ms prs-b8-link.telia.net (213.155.132.225) 180.209 ms
12 online-ic-305116-prs-b8.c.telia.net (62.115.40.86) 187.085 ms 202.595 ms 199.437 ms
13 45x-s31-1-a9k2.dc3.poneytelecom.eu (195.154.1.35) 175.505 ms * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I tried transferring a 6MB file from there to vassalengine.org and got around 890KB/s, which seems quite good. This makes me think the problem is not with Telia, either.

I have two friends on AT&T (one on U-verse, and the other on DSL I believe) that have been having intermittent problems with lag on the central Vassal server for several weeks now. Here are some TRACERT results:

[code] 1 1 ms <1 ms <1 ms dsldevice.att.net [192.168.1.254]
2 24 ms 75 ms 22 ms 108-224-48-2.lightspeed.lnngmi.sbcglobal.net [10
8.224.48.2]
3 * * * Request timed out.
4 23 ms 22 ms 23 ms 12.83.72.9
5 35 ms 34 ms 32 ms ggr4.cgcil.ip.att.net [12.122.133.33]
6 32 ms 32 ms 31 ms chi-b21-link.telia.net [213.248.87.253]
7 48 ms 48 ms 49 ms nyk-bb1-link.telia.net [213.155.136.72]
8 149 ms 152 ms 154 ms prs-bb3-link.telia.net [213.155.135.4]
9 147 ms 146 ms 150 ms prs-b8-link.telia.net [213.155.136.207]
10 150 ms 145 ms 151 ms online-ic-305116-prs-b8.c.telia.net [62.115.40.8
6]
11 145 ms * * 45x-s31-1-a9k2.dc3.poneytelecom.eu [195.154.1.35
]
12 142 ms 144 ms 145 ms one.vassalengine.org [62.210.178.7]

Trace complete.[/code]

[code]Tracing route to one.vassalengine.org [62.210.178.7]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 22 ms 27 ms 25 ms 12.83.32.133
5 41 ms 43 ms 47 ms ggr4.cgcil.ip.att.net [12.122.133.33]
6 34 ms 36 ms 31 ms chi-b21-link.telia.net [213.248.87.253]
7 48 ms 89 ms 46 ms nyk-bb1-link.telia.net [62.115.140.68]
8 145 ms 145 ms 147 ms prs-bb3-link.telia.net [80.91.253.121]
9 146 ms 142 ms 142 ms prs-b8-link.telia.net [213.155.131.1]
10 176 ms 174 ms 171 ms online-ic-305116-prs-b8.c.telia.net [62.115.40.8
6]
11 175 ms 177 ms 178 ms 45x-s31-1-a9k2.dc3.poneytelecom.eu [195.154.1.35
]
12 177 ms 176 ms 177 ms one.vassalengine.org [62.210.178.7]

Trace complete.[/code]

Someone posted on the U-verse support forums last month (forums.att.com/t5/Troubleshoot- … -p/4203601) but they just got a copy/paste response and nothing else since then.

In the meantime we’ve been using the P2P connection to connect everyone up together using a forwarded port, but ran into some problems with 6 people at once and no problems with only 4 people. Is there any additional documentation on using the P2P connection so we can try to smooth that out a bit more?

Thus spake cerebus13:

Someone posted on the U-verse support forums last month
(forums.att.com/t5/Troubleshoot- … -p/4203601[1]) but they
just got a copy/paste response and nothing else since then.

Have they tried contacting AT&T themselves?


J.

Hello,

I am on AT&T U-Verse and am also having issues with Vassal. Here’s a trace route:

Tracing route to one.vassalengine.org [62.210.178.7]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 23 ms 22 ms 23 ms 99.134.205.78
4 27 ms 26 ms 26 ms 12.83.114.17
5 50 ms 37 ms 37 ms 12.122.117.97
6 34 ms 40 ms 35 ms 192.205.33.42
7 91 ms 62 ms 61 ms ash-bb4-link.telia.net [62.115.137.72]
8 137 ms 140 ms 141 ms prs-bb2-link.telia.net [80.91.251.246]
9 133 ms 148 ms 136 ms prs-b8-link.telia.net [213.155.136.209]
10 142 ms 142 ms 141 ms online-ic-305116-prs-b8.c.telia.net [62.115.40.8
6]
11 135 ms 138 ms 137 ms 45x-s31-1-a9k2.dc3.poneytelecom.eu [195.154.1.35
]
12 140 ms 141 ms 140 ms one.vassalengine.org [62.210.178.7]

Trace complete.

I’ve tried wired connection, I’ve tried DMZplus mode, still no solution. I have contacted AT&T and sent them the trace route, a link to this thread, and everything I’ve tried. I will update with a response.

Has anyone found a solution for this yet? This is very frustrating!

I had been running smooth without major porblems until a couple of days ago. Now, I’m back to having problems even though I thought the direct ethernet cable had fixed it. As such, I reported it to AT& T tonight.

General instructions for reporting to At&T via chat:
1)Go to att.com/esupport/index.jsp
2) On the right of the screen there will be a little “chat now” button. click on it
3) Answer a few questions and it will start a chat session.
4) The agent was helpful but wanted me to run speed tests and clear cache, etc. What seemed to get the point across was when I referenced this forum and topic. ( I gave them the link https://forum.vassalengine.org/t/very-slow-response/7535/1)

The issue is known, and they said they are working on it. If you are having the issue though and are an At&T customer, then it seems the only thing you can do to hurry it along is report it in this method.

By the by, find a bill. They will want your Uverse account number.

Thus spake VaynMaanen:

Has anyone found a solution for this yet? This is very frustrating!

Have you called AT&T about the problem? That should be your first
step.

I finally have an email address for someone there who might be able
to help us. I intend to pursue that avenue this evening.


J.

Called At&T support, but of course connection was great then.

Any luck? It’s gotten really bad in recent days. I have ow talked to three differecent AT&T support people. Their offical position seems to be that it is not an At&T problem, but if I’d like to pay a one-time $50 fee , they wil reasearch the problem. I really don’t want to to do this expecially since I believe they will end up saying it is an “application” problem.

Any suggestions?

Anyone try changing their DNS servers as it might be an issue with AT&T’s default DNS being screwed up?

Possibly something google public DNS: developers.google.com/speed/pub … sing?csw=1

Tried changing the DNS server. It didn’t help.

Thanks anyway , though.