Results -9 to 0 of 27

Threaded View

  1. #19
    Player
    DoomAngel's Avatar
    Join Date
    Apr 2020
    Posts
    67
    Character
    Doom Angel
    World
    Midgardsormr
    Main Class
    Dark Knight Lv 80
    Quote Originally Posted by Moronica View Post
    The last screenshot only shows packets of one connection because Wireshark’s filter was “(ip.addr eq 192.168.1.146 and ip.addr eq 204.2.229.93) and (tcp.port eq 58899 and tcp.port eq 55026)”. Any additional TCP connection(s) from 192.168.1.146 to 204.2.229.93:55026 wouldn’t match these filter criteria.

    There’s also no indication of dropped packets. The last two chunks of data sent by the client at 205.284423 and 205.296661 weren’t acknowledged by the server with an ACK most likely because it had already sent the FIN by the time it received those packets. That’s probably what caused the RST packets following the FIN, because received data can’t be acknowledged if the application already closed the socket and it thus unable to read that data.

    If something along the way would drop or mangle TCP packets, the server would simply not receive those packets or ignore packets with an invalid checksum. That didn’t happen AFAICS, because the screenshot shows no retransmits and ACKs of the server for all data sent by the client (except for the last two chunks already mentioned).

    Someone™ has to check the logs of the server to figure out what’s going on…
    I just did the Wireshark conversation filter >TCP to capture all sessions between those two IP's. Those two ports are the only ones that were open for that connection.

    Regarding dropped packets, while playing the game and capturing data, I've seen packet loss and the game hasn't disconnected at times, and have seen the game drop during times without packet loss. *shrug*
    (0)
    Last edited by DoomAngel; 06-27-2020 at 05:58 AM.