How i ban some1?

how can i ban some1 for specific days?
e.g:
ban acc for 30 days because of using AC.
and normal ban..(for ever)
thannks...

here is just few ways..
"JustPTAdminMode44Blocker" [enable in SERVER_619]
"InputIDBlock" [enable in SERVER_619 you can choose how much time u want to ban]

and of course the "PT Admin Tool (Made by Sandurr)" [you can find too in SERVER_619]

i think that enough xD

You can also add their ID to the BlackUser list, and block their IP in your firewall.

Dynamic IPs are a git, and if need be, and it's not too common, ban their entire ISPs IP block. You may want to consider informing their ISP of any unsavoury behaviour by one of their users... but you may also want to warn the user that you will do this if they persist.

i have question ill ask it here
i never banned some one [ip ban] then what u mean ban in firewall?
thanks

Firewall software traditionally works on ACL style lists for Port and IP objects the same as NT security works ACLs for File, Registry and Windows Name Space objects. That's where MS got the ACL analogy from.

An ACL (Access Control List) entry specifies "Allow" "Deny" or "Unset" for a specific object. In Firewall terms the Objects are Ports, Protocols and IPs... Each entry may specify a Port, or range of ports, an IP or a range of IPs, and one or more protocols... usually nothing more than TCP, UDP, ICMP... but sometimes MMS and RTSP are included as options as well. My routers firewall only supports TCP, UDP or Both, and that is enough. My PCs firewall supports ICMP as well. It all depends how advanced your firewall is.

Anyway... you want your server secure, so you Deny Ports 0-79 inclusive, you Deny Ports 81-10008 (for example) inclusive and your Deny Ports 10010- 65535 inclusive, as your basic security.

That blocks everything except access to your website and your game server, so nobody is going to telnet in, RDC in, get at SMB shares or Remote Registry admin shares & named pipes... all of which is open to everyone by default on Windows.

When you find a hacker, you find their IP... either in your Router Log, or your user logs, or by the fact that they where in your Router Log but never logged in to your server. Then you add a new ACL to your firewall that Denies all TCP & UDP access on ANY port for that IP.

They don't hack you no more. Not in game, and not out of it. They can't DDoS you (though they can have a go at your provider) etc.

If they are on a DynIP ISP, they can disconnect from the internet and will get a new IP when they reconnect. Boo Hiss. Okay... we don't like DynIP ISPs, and this one is nasty... so you WhoIs the IP, and that tells you which ISP he uses and what range of IPs they are allocated. So you Deny all access to that range of IPs, apologise to any other users on that ISP, and notify the ISP of the abhorrent actions of their user giving them a bad name with details of what IP they had at which times... they can tract that back to a MAC address, which will equal a street address they can post a Cease and Desist or we don't want your kind of custom letter.

Of course some ISPs around the world just don't care, then you recommend your users don't use those ISPs, as you have blacklisted them for the number of disruptive users they host.

Simple... hahahaha... yea, not really. But that's the way it should work. The real game of life is never that easy. :wink:

I've taken Ethical hacking classes, hacked into my own servers a thousand times and every time I close one hole users want some service that opens up another. When you get into ghosts, spoofing, packet splicing and zombi hacks... consider yourself a pro. Those things I will not discuss from ANY perspective. Go take evening classes if you want to learn more. :wink: