Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

With IP limit set, accounts are stuck in CLE after logging out, so I cannot quickly switch accounts #658

Open
shea851 opened this issue Sep 9, 2017 · 2 comments
Labels

Comments

@shea851
Copy link
Contributor

shea851 commented Sep 9, 2017

Hi. I have the following rules set to enable an IP limit on server:
World:MaxClientsPerIP 2
World:MaxClientsSimplifiedLogic true

It works properly - I can log in 2 accounts and when I attempt to log in the 3rd it disconnects.

The issue I have is that when I disconnect one account, whether through /q or camp to char select and hit 'esc', then I cannot log in a new account for at least 15 minutes (I get to char select and get disconnected when I try to enter world). The expected behavior is that when one account is camped properly, I can log in a new account right away.

I believe the issue is that when I log off, the logged off account is still in the ClientListEntry. I see entries like this in the world logs, showing that my account camped 15 minutes earlier is still logged on, so it instantly disconnects my account trying to log in.

[09-08-2017 :: 20:12:00] [Client Login] Account ID: 160333 Account Name: myacc01 IP: x.x.x.x.
[09-08-2017 :: 20:12:00] [Client Login] Account ID: 162584 Account Name: myacc02 IP: x.x.x.x.
[09-08-2017 :: 20:12:00] [Client Login] Account ID: 159239 Account Name: myacc03 IP: x.x.x.x.
[09-08-2017 :: 20:12:00] [Client Login] Disconnect: Account myacc03 on IP x.x.x.x.

Thanks all!

@shea851 shea851 changed the title ClientListEntry does not remove or become stale on log out With IP limit set, accounts are stuck in CLE after logging out, so I cannot quickly switch accounts Sep 9, 2017
@SecretsOTheP
Copy link
Contributor

Simplified logic was set up with a 1 IP limit in mind. I'll try and fix this when I get time, unless someone else wants to tackle it.

@Akkadius Akkadius added the Bug label Sep 19, 2017
@Cloudxtreme
Copy link

This is certain not just hitting the databases cache?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants