Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

[recvPing:221] Bad NET_PING packet, alleged sender is 1 #4363

Closed
wzdev-ci opened this issue May 4, 2016 · 7 comments
Closed

[recvPing:221] Bad NET_PING packet, alleged sender is 1 #4363

wzdev-ci opened this issue May 4, 2016 · 7 comments

Comments

@wzdev-ci
Copy link
Contributor

wzdev-ci commented May 4, 2016

resolution_fixed type_bug | by klasskill


this always happens if a person joins by IP


Issue migrated from trac:4363 at 2022-04-16 11:55:10 -0700

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented May 4, 2016

Cyp changed blocking which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented May 4, 2016

Cyp changed blockedby which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented May 4, 2016

Cyp commented


Tried joining myself via IP, couldn't reproduce. Maybe it has to be two different computers?

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented May 6, 2016

Cyp <cyp@...> changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented May 6, 2016

Cyp <cyp@...> changed owner from `` to Cyp <cyp@wz2100.net>

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented May 6, 2016

Cyp <cyp@...> changed resolution from `` to fixed

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented May 6, 2016

Cyp <cyp@...> commented


In Warzone2100/warzone2100@f2a0901:

#CommitTicketReference repository="" revision="f2a090105c32d5c477e06352e01a97f06ce22f8c"
Don't print «Bad NET_PING packet» to console if the network is slow.

If a client sent 2 (or more) pings before getting an answer, the reply to the first would be considered bad.

Fixes #4363.

@wzdev-ci wzdev-ci closed this as completed May 6, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant