Jump to content

Question

Posted (edited)

Hello, I've recently started developing my own server. I have ran into an issue.

 

When someone tries to log in 3 times with a wrong password the client simply closes, but the IP is not banned. After closing the client i can open it up again and log in just fine. I have found in LoginServer.ini:

 

# ---------------------------------------------------------------------------
# Security
# ---------------------------------------------------------------------------

# How many times you can provide an invalid account/pass before the IP gets banned.
# Default: 5
LoginTryBeforeBan = 5

# Time you won't be able to login back again after LoginTryBeforeBan tries to login.
# Default: 900 (15 minutes)
LoginBlockAfterBan = 900

# If set to True any GameServer can register on your login's free slots
# Default: True
AcceptNewGameServer = True

# Flood Protection. All values are in MILISECONDS.
# Default: True
EnableFloodProtection = True

 

But no matter what i do here nothing changes. What am i missing?

Sorry if this has been asked before, I checked everywhere and didn't find an answer.

 

 

Edited by vmilon
Better expanation

6 answers to this question

Recommended Posts

  • 0
Posted

Could be the client is overriding the server in this. Try lowering the  tries before ban to 3, try again and if the account gets banned my assumption would be correct and you will have to blame the client.

  • 0
Posted
13 minutes ago, ZaNteR said:

Could be the client is overriding the server in this. Try lowering the  tries before ban to 3, try again and if the account gets banned my assumption would be correct and you will have to blame the client.

Thanks for the quick reply. I tried this and it works, the login server console says that the IP is banned. So you were right and it probably IS a client issue. Any ideas?

  • 0
Posted

You dont need that option IMO, it will just complicate the player's life more


LoginTryBeforeBan = 50
LoginBlockAfterBan = 10

 

do not forget to restart the Auth

  • 0
Posted

 

On 5/27/2024 at 5:45 PM, Dorie said:

You dont need that option IMO, it will just complicate the player's life more


LoginTryBeforeBan = 50
LoginBlockAfterBan = 10

 

do not forget to restart the Auth

 

I don't need it. The thing is that even if i put "LoginTryBeforeBan = 50" after 3 wrong attempts the client crashes.

That's what i'm trying to figure out.

  • 0
Posted
8 hours ago, vmilon said:

 

 

I don't need it. The thing is that even if i put "LoginTryBeforeBan = 50" after 3 wrong attempts the client crashes.

That's what i'm trying to figure out.

What pack is that? Chronicle?

  • 0
Posted (edited)

In the loginserver, try to change the LoginFailReason from

REASON_USER_OR_PASS_WRONG (0x02) to REASON_ACCESS_FAILED (0x15)

 

If the client doesn't crash anymore then I guess there's an internal counter that you have to patch (it was like this in one of the client i tried).

 

Or you can use, as a workaround, another error that you would never need (for example REASON_WEEK_USAGE_FINISHED (0x1E) and then just modify the corresponding systemmessage in the .dat file)

 

Troll solutions at their best xD

Edited by ratchet

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • https://web.archive.org/web/20260306183214/https://maxcheaters.com/topic/241828-l2j-l2damage/page/3/ https://l2topzone.com/forum/l2-server-support-problems/9/l2damage-stopped/30514 Also we will try to push longer seasons ever ! (1135-100)/9 = 115 online
    • ONE SIDE – AND EVERYTHING BREAKS ▪ Looks like a simple case: Florida DL, back side, barcode – “clean and minimal”. ▪ In reality, these are exactly the tasks that fail most often. – data provided as plain text – request only for the back side – focus on the barcode (PDF417) ▪ And here’s the key point: ▪ A barcode is not just a “picture on the back”. It’s compressed logic of the entire document. ▪ If it doesn’t match the front, format, and data structure – the system flags it instantly. ▪ Many create a “similar-looking” code. But systems don’t read “similar” – they read by specification. ▪ In cases like this, it’s not about design. It’s about correct data assembly and how it behaves inside the format. ▪ Today only – 15% off for verification cases. ▪ Want it to pass, not just look right? Describe your case – we’ll show where even clean files break. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #editing #photoshop #documents #verification #case
    • Your anonymity is a corpse. Blockchain forgets nothing. Your transactions are direct footprints in the hands of anyone who takes an interest. [✘] Still believe in "mixing"? Forget it. Classic Bitcoin mixers are an illusion of security. For Chainalysis and Elliptic algorithms, any attempt to hide tracks in the ledger is transparent. Your "mixing" is an artifact that gets filtered out in seconds. Every transaction leaves a trail that leads to frozen assets or unwanted questions from exchanges.  We don't mix. We break the link. [-] Input: Your "dirty" coins (Dirty BTC/ETH) with all their history and digital markers stay with us. [+] Output: You receive absolutely clean assets (Clean Crypto) from our reserves, which have never intersected with your past. This isn't a game of hide and seek. This is the surgical removal of your financial history from the system.   ------------------------------------------------------------------- Technical indexing: Bitcoin Mixer, Crypto Mixer, Clean BTC, Clean ETH, Anti-Chainalysis, Best Bitcoin Mixer, Anonymous Crypto Exchange, NoLog Mixing Service.
    • Here you are: https://l2crypt.com/l2-tools/l2editor-source/
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..