TaG_Belial Posted October 12, 2006 Share Posted October 12, 2006 It would appear the old tradition from Ghost Recon has followed us to GRAW Not only does it appear that servers can be fully boomed and crashed but also player booming (Kicking players in game) Works as well. To say I am non plussed that this hole in the game security was not plugged for GRAW is the biggest understatement this year. Have any other server owners or Server Admins found this happing to them yet, or is it just the ::TaG:: and =XE= Servers that are being targeted? There is no point going down the its your hardware route, it isn’t, we have Very high spec systems that only run 2 game servers to a system. They are all dual core Opteron 4200 running 4 gigs of Muskin redline. They work perfectly with no lag when full, But every now and again some little ###### bag script kiddie will either start kicking the players while they are in game, or crash the server completely. Will GRIN look at doing something to stop these attacks. In GR we used to manage to stop them by changing ports and password protecting servers. However that only stopped it happening in matches. As GRAW hasn’t even got off the ground yet, never mind matching neither of these options is viable (Not sure if port change is possible) Any ideas would be welcomed Oh and I posted this in the main area, not support, because I will post the crash specifics in support and secondly I wanted to see what the community had to say, not the small amount of ppl that go to support. Thanks B Quote Link to comment Share on other sites More sharing options...
-|-aMMo-|- Posted October 12, 2006 Share Posted October 12, 2006 Are you sure they are even attacks and not just normal game activity? Its not perfect ya know alot of people crash and rooms crash because of bugs. Quote Link to comment Share on other sites More sharing options...
JJUK Posted October 12, 2006 Share Posted October 12, 2006 It would appear the old tradition from Ghost Recon has followed us to GRAW Not only does it appear that servers can be fully boomed and crashed but also player booming (Kicking players in game) Works as well. To say I am non plussed that this hole in the game security was not plugged for GRAW is the biggest understatement this year. Have any other server owners or Server Admins found this happing to them yet, or is it just the ::TaG:: and =XE= Servers that are being targeted? There is no point going down the its your hardware route, it isn’t, we have Very high spec systems that only run 2 game servers to a system. They are all dual core Opteron 4200 running 4 gigs of Muskin redline. They work perfectly with no lag when full, But every now and again some little ###### bag script kiddie will either start kicking the players while they are in game, or crash the server completely. Will GRIN look at doing something to stop these attacks. In GR we used to manage to stop them by changing ports and password protecting servers. However that only stopped it happening in matches. As GRAW hasn’t even got off the ground yet, never mind matching neither of these options is viable (Not sure if port change is possible) Any ideas would be welcomed Oh and I posted this in the main area, not support, because I will post the crash specifics in support and secondly I wanted to see what the community had to say, not the small amount of ppl that go to support. Thanks B we have thought this ourselves but cant confirm. Quote Link to comment Share on other sites More sharing options...
sui317 Posted October 12, 2006 Share Posted October 12, 2006 this week grin did open testing on server side solutions maybe that would bring a patch that works these issues out Quote Link to comment Share on other sites More sharing options...
Beaver Posted October 12, 2006 Share Posted October 12, 2006 (edited) It would appear the old tradition from Ghost Recon has followed us to GRAW Not only does it appear that servers can be fully boomed and crashed but also player booming (Kicking players in game) Works as well. To say I am non plussed that this hole in the game security was not plugged for GRAW is the biggest understatement this year. Have any other server owners or Server Admins found this happing to them yet, or is it just the ::TaG:: and =XE= Servers that are being targeted? There is no point going down the its your hardware route, it isn’t, we have Very high spec systems that only run 2 game servers to a system. They are all dual core Opteron 4200 running 4 gigs of Muskin redline. They work perfectly with no lag when full, But every now and again some little ###### bag script kiddie will either start kicking the players while they are in game, or crash the server completely. Will GRIN look at doing something to stop these attacks. In GR we used to manage to stop them by changing ports and password protecting servers. However that only stopped it happening in matches. As GRAW hasn’t even got off the ground yet, never mind matching neither of these options is viable (Not sure if port change is possible) Any ideas would be welcomed Oh and I posted this in the main area, not support, because I will post the crash specifics in support and secondly I wanted to see what the community had to say, not the small amount of ppl that go to support. Thanks B There is no exploit to BOOM graw servers at the moment. I would hazard a guess that you havent set the CPU affinity for each graw process to use just 1 CPU, Currently GR:AW dedicated is very unstable using dual-core or 2 cpu's & you will see alot of people being kicked/crashes. I noticed this early on when running graw dedicated on our dual opteron 250 cpu box & since I set the affinity of the process to always use just 1 cpu, its very stable and works just fine. PM me, if you want some help in setting the CPU affinity permanently for the graw-dedicated.exe, without having to do it via task manager everytime. Edit: It also depends on what maps/gamemode your playing on the server, there are a few 'bugged' maps that cause problems. Edited October 12, 2006 by Beaver Quote Link to comment Share on other sites More sharing options...
TaG_Belial Posted October 12, 2006 Author Share Posted October 12, 2006 Beaver, thanks for your input However let me re-state. The severs run very stable nearly 99% of the time even when both are maxed out with 32 players each with no lag. If we had a CPU issue (I don’t set that stuff up, I have game server experts that do that) Then logically the problem would happen then. However, I have noticed this began to happen as soon as I kicked someone for suspected cheating in game (Only 16 ppl in server at the time), He was kicked, returned in game then boom bye bye server, We are also noticing that you can be happily playing in game with 20 or less people in it, then systematically one by one each player is dropped leaving you the only one in the server. As I say most of the other times the run fine maxed out. I say Boomed because exactly the same thing happened last night in a GR server I was playing in (Not Mine) and that was 100% a boom. Sorry mate, I just don’t see it as CPU, I see it as script kiddie. I will however get with the Server Set Up admin find out how he has it set up and re post once he is on. Quote Link to comment Share on other sites More sharing options...
sui317 Posted October 12, 2006 Share Posted October 12, 2006 isn't there a log file who connects to the server ?? then you can find out for sure if it is a script kid (i mean the fysical server not just graw server software) Quote Link to comment Share on other sites More sharing options...
Beaver Posted October 12, 2006 Share Posted October 12, 2006 (edited) isn't there a log file who connects to the server ?? then you can find out for sure if it is a script kid (i mean the fysical server not just graw server software) This is something we've asked the devs for though for in-game admin/server logs. Edit: I think I'll take a look at the old method we used to use for logging IP's/Names of players who connect to the server, using winpcap. Edited October 12, 2006 by Beaver Quote Link to comment Share on other sites More sharing options...
FI_FlimFlam Posted October 12, 2006 Share Posted October 12, 2006 No logs ATM. That is what we have been requesting from GRIN since the Beta. Hopefully with the next patch some sort of connection logging will be available. Quote Link to comment Share on other sites More sharing options...
ROCO*AFZ* Posted October 12, 2006 Share Posted October 12, 2006 Haven't seen it happen to use...even when matching in TWL and TCZ in fact i just restarted our server yesterday for the 1st time since 1.30 came out. I had a bandwith monitor app go awol, stop detecting anything going through it, and everyone's pings maxed out. restart cleared it. Just to confirm... these were stock maps right? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.