Login Server Issues

[Garnaak]

So, let me step back a bit. Maybe there is some network node out there messing with things. (That still does not explain why I have no issues with PEQ, but I will play along.)

Here is my traceroute to P99 login server.

$ sudo traceroute -I login.eqemulator.net
traceroute to login.eqemulator.net (160.72.227.52), 30 hops max, 60 byte packets
1 10.0.2.1 (10.0.2.1) 3.064 ms 3.055 ms 6.120 ms
2 10.19.112.1 (10.19.112.1) 20.531 ms 22.876 ms 27.910 ms
3 te0-6-0-10.rcr21.b052488-1.sea02.atlas.cogentco.com (38.88.253.169) 27.911 ms 27.900 ms 27.895 ms
4 be2074.ccr22.sea02.atlas.cogentco.com (154.54.47.109) 27.892 ms 33.997 ms 33.989 ms
5 be2029.ccr32.slc01.atlas.cogentco.com (154.54.86.109) 54.373 ms 54.364 ms 54.350 ms
6 be3038.ccr22.den01.atlas.cogentco.com (154.54.42.98) 83.455 ms 66.302 ms 66.199 ms
7 be3036.ccr22.mci01.atlas.cogentco.com (154.54.31.90) 63.379 ms 63.201 ms 69.274 ms
8 be2832.ccr42.ord01.atlas.cogentco.com (154.54.44.170) 77.690 ms 78.563 ms 78.487 ms
9 be2718.ccr22.cle04.atlas.cogentco.com (154.54.7.130) 84.540 ms 83.529 ms 83.477 ms
10 be2879.ccr22.alb02.atlas.cogentco.com (154.54.29.174) 99.265 ms 94.867 ms 94.812 ms
11 be3600.ccr32.bos01.atlas.cogentco.com (154.54.0.222) 101.467 ms 101.447 ms 103.073 ms
12 38.142.179.114 (38.142.179.114) 103.038 ms 99.704 ms 99.632 ms
13 ae3-bstpmalljp1.lightower.net (144.121.35.37) 103.670 ms 99.847 ms 103.883 ms
14 160.72.248.57.lightower.net (160.72.248.57) 103.873 ms 100.936 ms 103.906 ms
15 ae0-brtnmas6j81.lightower.net (65.254.31.58) 103.805 ms 99.989 ms 103.049 ms
16 144.121.39.122.lightower.net (144.121.39.122) 103.005 ms 98.574 ms 98.525 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

And here is my traceroute to the PEQ login server

$ sudo traceroute -I login.projecteq.net
traceroute to login.projecteq.net (51.79.10.190), 30 hops max, 60 byte packets
1 10.0.2.1 (10.0.2.1) 3.004 ms 2.989 ms 2.976 ms
2 10.19.112.1 (10.19.112.1) 20.639 ms 36.197 ms 36.188 ms
3 te0-6-0-10.rcr21.b052488-1.sea02.atlas.cogentco.com (38.88.253.169) 37.489 ms 37.472 ms 37.454 ms
4 be2074.ccr22.sea02.atlas.cogentco.com (154.54.47.109) 37.434 ms 37.415 ms 37.397 ms
5 be3284.ccr21.slc01.atlas.cogentco.com (154.54.44.74) 46.052 ms 46.037 ms 46.029 ms
6 be3037.ccr21.den01.atlas.cogentco.com (154.54.41.146) 57.845 ms 78.042 ms 92.185 ms
7 be3035.ccr21.mci01.atlas.cogentco.com (154.54.5.90) 94.996 ms 76.375 ms 76.345 ms
8 be2831.ccr41.ord01.atlas.cogentco.com (154.54.42.166) 76.311 ms 73.323 ms 77.046 ms
9 be2717.ccr21.cle04.atlas.cogentco.com (154.54.6.222) 83.778 ms 85.462 ms 85.436 ms
10 be2993.ccr31.yyz02.atlas.cogentco.com (154.54.31.226) 105.624 ms 87.754 ms 93.210 ms
11 yto-tr1-bb1-a9.on.ca (142.44.208.242) 96.084 ms 90.642 ms 93.596 ms
12 192.99.146.163 (192.99.146.163) 102.340 ms 95.168 ms 100.688 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 ip190.ip-51-79-10.net (51.79.10.190) 102.844 ms 111.524 ms 111.475 ms

By all appearances, lightower.net (or whoever is right after them in the chain) is where the problems start.

[u_lock]

Again, you have one of three issues. A traceroute doesn't mean whatever you think it means.

[Garnaak]

Originally Posted by u_lock [You must be logged in to view images. Log in or Register.]

Again, you have one of three issues. A traceroute doesn't mean whatever you think it means.

And I am saying, I have changed NOTHING on my end since playing P99 without issue for 9 years until recently. You are advocating for an issue that spontaneously shows up without any cause.

[u_lock]

Upstream filtering (contact your ISP)

[Garnaak]

Wrong. I use a VPN and the full route out of that network is shown in both traceroutes, both P99 and PEQ. If my VPN provider is mangling packets, they would be mangling PEQ's packets just the same as P99. That does not appear to be the case, unless the PEQ client somehow compensates for it in ways the P99 client does not.

[sadawe]

might it be another wineq issue?

[u_lock]

1. Use a real full-tunnel VPN
2. Provide PCAP or GTFO

[Garnaak]

Originally Posted by u_lock [You must be logged in to view images. Log in or Register.]

1. Use a real full-tunnel VPN
2. Provide PCAP or GTFO

I'll wireshark both the P99 and PEQ logins this weekend.

And, I use openvpn with Private Internet Access as my vpn provider. Been using them for years and played P99 for years over it.

[Garnaak]

Originally Posted by sadawe [You must be logged in to view images. Log in or Register.]

might it be another wineq issue?

Not for me. I am old school and just use a batch file the start the clients "eqgame.exe patchme"

[MasterCS]

Originally Posted by Garnaak [You must be logged in to view images. Log in or Register.]

Not sure about everyone else, but I do not use AT&T for my connection. I also route all my traffic through a VPN anyway.

Also, I was able to use PEQ login server and play with no issue, so the issue is not on my end.

I'm in the same boat, and I do not have AT&T. I've never had issues playing P99 until about a month ago, which is why I started the thread. I've had the same ISP, router, etc for the last four years, and I've never had an issue playing until until now. I find it hard to believe that all of these people have just started having issues at the same time, and we're all supposed to believe it's just coincidence or our ISP's just recently changed something.

I did recently set my PC to a static IP, and update all of my drivers (just built a new rig about 4 months ago). It has seemed to help a little, but I still have troubles logging in and zoning.