Bogus IP Header Length Packet Sniff

[towbes]

I had the same issue with TT, after about 30s in zone ping spiked up to 4k then eventually d/ced me. I was however able to log back in eventually and make my way to the seb orb and zone in. That makes sense on the MTR analysis. I know I'm seeing packet loss, I'm not questioning that. I just think the server is severing the connection too quickly, and the client is missing the message that the connection was severed so it just keeps trying. What's especially frustrating is circumstances where the character client never loads into a zone (just sits at the previous zone screen with the busy cursor), however when you manually close the client and attempt to log back in, it says you still have a character in zone. So what's happening there? Why isn't the client being sent messages telling it that it zoned? Probably the only way to pinpoint the issue is to setup a local server, and monitor the connection to that local server to find out what it's supposed to look like, and use something like burpsuite to kill certain packets and find that one that is causing the problems. (Not even sure it would be capable of performing quickly enough to allow a game session to occur though, just theorizing)

[Latex]

I have been having issues since this last patch. Failing to zone, timing out on login, once logged in server list isn't populated, etc. It's incredibly frustrating. P99 has run smoothly for the past year until this last patch for me.

[Ruien]

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

I have been having issues since this last patch. Failing to zone, timing out on login, once logged in server list isn't populated, etc. It's incredibly frustrating. P99 has run smoothly for the past year until this last patch for me.

I'm pretty sure that the latest P99 patch is 100% orthogonal to the connection to the login server. The only possible way that you could see issues such as a more frequent blank server select screen would be something related to the network. You might want to try the tests demonstrated earlier in this thread to see if you, too, are seeing packet loss issues. Given all the new issues I've seen pop up on the forums recently, it's very possible that some important router somewhere took a dump, some ISP pairings changed, some international connection piplines became saturated, or something of that nature. The timing of the latest patch is probably an unfortunate coincidence but unrelated if you're seeing issues related to the login server.

The zoning code on p99 did change, resulting in differences in the way that the zoning sequence looks in Wireshark. In theory it should only help, but might have unexplored implications. So, I'm not ruling out the possibility of problems being caused by that change, only saying that if you're seeing an increase in the frequency of issues connecting to the login server (even before connecting to p99) then the evidence suggests the underlying issue lies elsewhere.

[towbes]

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

I'm pretty sure that the latest P99 patch is 100% orthogonal to the connection to the login server. The only possible way that you could see issues such as a more frequent blank server select screen would be something related to the network. You might want to try the tests demonstrated earlier in this thread to see if you, too, are seeing packet loss issues. Given all the new issues I've seen pop up on the forums recently, it's very possible that some important router somewhere took a dump, some ISP pairings changed, some international connection piplines became saturated, or something of that nature. The timing of the latest patch is probably an unfortunate coincidence but unrelated if you're seeing issues related to the login server.

The zoning code on p99 did change, resulting in differences in the way that the zoning sequence looks in Wireshark. In theory it should only help, but might have unexplored implications. So, I'm not ruling out the possibility of problems being caused by that change, only saying that if you're seeing an increase in the frequency of issues connecting to the login server (even before connecting to p99) then the evidence suggests the underlying issue lies elsewhere.

I'm not exactly sure what you mean by orthogonal, but when you watch wireshark as you login, you're sending packets to the same IP as the gameserver when you are logged into P1999. 66.55.145.2 The code is all related:

https://github.com/EQEmu/Server