banning? crashing help?

[dee]

Howdy all.
few questions in here!
I seems to have a big problem. My server was getting crashed over & over last nite. Now today im going through my c.i. logs & im pretty sure i found the loser doing it! In my logs I see this guys name & ip changing constantly entering & leaving the server within minutes (obviously he's using a network or somthin) anyhow i notice his 1st set of ip numbers are allways in the 200's but it seems he's geting help from another ip thats changing 1st set 80's.. How do i bann that entire string of ip's.also does that really matter if i bann the string? or he can just change the 1st ip numbers also?
please help im a little lost in this department.
Also would really like to know if there are any uncrAshable mohAa servers out there? or are they all crashable to somone who knows what there doing?

this is all the same guy i know this cause of the pattern he uses with the name & ip changeing & this is when the server kept going down!
notice his 1st 3 numbers are in the 200's can i bann that whole 200 string & keep him out?
also notice the times & how quikly he's entering & leaving the server with the same ip & different name? wierd huh? PLEASE! help me get rid of him he's been doing this for a year! whenever he gets in the mood i guess. cause everytime i get the crash complaints i see this type of crap in my log files!!

Actually i did bann some strings today & kept him out for quite awhile. till he wound up using the same numbers in the begging of my ip! doh! then i starting moving into the next set & so on!! is there a better way?

anyway heres some of the log files
obviously i cant bann somone like this his ip changes in game!?

6:41:22 PM [)r@g()n$@!y@n/213.119.76.139 has left the battle
6:41:22 PM /213.119.76.139 has joined the battle.
6:38:32 PM KoRnFreAk/213.224.182.201 has joined the battle.
7:25:01 PM KoRnFreAk/200.42.187.213 has left the battle
7:25:02 PM LA GEISHA/200.42.187.213 has joined the battle.
7:27:11 PM LA GEISHA/200.42.187.213 has joined the battle.

[SNYPE]

First thing I would do is make sure that you have all of the patches to stop server crashing installed. We have some in our Download section and you can also find some at InvisibleWarriors.com (http://InvisibleWarriors.com) in their Downloads. That should stop the crashes.
Next these guys are not all the same. You need to get a tool such as Visual Route (http://www.visualware.com/personal/index.html) and input the IPs. It will trace where they come from and you can get the info on their Provider and see what the IP range is that they own. For instance the guy with the 200.42.187.213 is in Uraguay and his Provider owns IPs 200.0.0.0-200.255.255.255. The guy with the IP 213.224.182.201 is in Belgium and his Provider has the IP range of 213.224.128.0 - 213.224.223.255 so he cant change his IP to 200.x.x.x.
The third guy 213.119.76.139 is also in Belgium but has a different Provider. That range is 213.118.160.0 - 213.119.255.255.
You can ban by subnets using CI but the higher the octet, the more IPs you are banning. For instance 200.0.0.* will ban 255 IPs. Banning 200.0.*.* will ban about 65,000 and so on. Of course if you dont care about players from these parts of the world coming to your server, its not an issue, but if you live in Belgium and you ban those last 2 Provider's IP ranges you could lose an awful lot of players.

[dee]

ok so i take ot you checked those out?
now so the guy with the 213 if i put 213 in my ban list he's gone right?
& same goes for the 200?

[dee]

ok witch program did you use where you found the ip ranges? lookout route or call id?

[GaSplat]

DNS stuff has great tools (http://www.dnsstuff.com/) In the middle column of options, you will find several for IP look ups. By using the IP Whois you will find the isp data. The ISP may have a line like this:

inetnum: 200.42.176/20

which describes a block of IPs it has. Cut and paste the 200.42.176/20 in to the CIDR Netmask lookup in the dnsstuff page and you will find out that this represents:

CIDR range 200.42.176/20
Netmask 255.255.240.0
Wildcard Bits 0.0.15.255
First IP in range 200.42.176.0 (network address)
Last IP in range 200.42.191.255 (broadcast address)
First useable IP in range 200.42.176.1
Last useable IP in range 200.42.191.254
Number of useable IPs in range 4094

[dee]

hi thx heres the cidr results of the guy who crashes my server. now what do i do with this info ? lol?

CIDR range 83.135.0.0/16
Netmask 255.255.0.0
Wildcard Bits 0.0.255.255
First IP in range 83.135.0.0 (network address)
Last IP in range 83.135.255.255 (broadcast address)
First useable IP in range 83.135.0.1
Last useable IP in range 83.135.255.254
Number of useable IPs in range 65534

now lets say my ping kick kicks by the 1st set of numbers if i place 83 in my ping kick would that get rid of him?
anyhow i think im just getting out of the mohaa unsupported world! although i love the game. C.O.D. Is pretty cool also & i hear there arent problems of peeps just coming in & crashing servers!
mohaa is a bit to hard to handdle unless ya know how to patch the game problems yer self!

[SNYPE]

hi thx heres the cidr results of the guy who crashes my server. now what do i do with this info ? lol?

CIDR range 83.135.0.0/16
Netmask 255.255.0.0
Wildcard Bits 0.0.255.255
First IP in range 83.135.0.0 (network address)
Last IP in range 83.135.255.255 (broadcast address)
First useable IP in range 83.135.0.1
Last useable IP in range 83.135.255.254
Number of useable IPs in range 65534

now lets say my ping kick kicks by the 1st set of numbers if i place 83 in my ping kick would that get rid of him?
anyhow i think im just getting out of the mohaa unsupported world! although i love the game. C.O.D. Is pretty cool also & i hear there arent problems of peeps just coming in & crashing servers!
mohaa is a bit to hard to handdle unless ya know how to patch the game problems yer self!
From the info above if you want to ban this guy I would ban 83.135.*
That will cover all 65,534 IPs that belong to his provider.
As I originallly said you need to apply the patches to insure that they (or anyone else!) cant crash your server. There are only 3 patches that need to be installed and they are very easy to apply:

1. AA Server Crash Fix: is a new gamex86.dll file that replaces the original one in the MOHAA folder.
2. Localization Crash Fix: apply this one if you a bad word filter localization file.
3. AA Server Cras Fix, Grenade Routine: apply this one too its a pk3 file that stops a bug involving grenades that can cause a crash.

Heres the link to them all:
http://invisiblewarriors.com/iw/modules.php?name=Downloads&d_op=viewdownload&cid=5

Hang on for Pacific Assault! Its due out in September and will include PunkBuster which will spell the END of cheaters in MOH.

[dee]

thats what i dont understand i have all the fixes!
the only thing i did different was add a ckr mod ! i heeard the ckr mod could cause a problem but i removed the grenade scr.s from the mod & left the grenade fix mod in the server main!
i/m pretty sure those 3 fixes for mohaa that have been out for over a year now! & the new/ 8 months old! buzz goodies ladder crash fix! are not the only ways to crash an mohaa server cause im up to date with all that!! & someone has been violently crashing my server over & over! my server is packed 24 -7 now its empty 24-7!

[GaSplat]

Is it just the game, or the server itself that is crashing / rebooting? Do you get any error messages? Does the server restart or does it actually crash?

[SNYPE]

Also, if you have logging turned on you can check the logs to see what happens just before it crashes.