Forum

ASSIST, AMERICA'S ARMY COMMUNITY - RELIVE THE GLORY DAYS OF AMERICA'S ARMY 2.5

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - [SWISS]Merlin

Pages: 1 ... 21 22 [23] 24 25 ... 185
331
General Chat / Re: DDoS and the facts about it
« on: Wednesday, June 08, 2016, 18:24:23 PM »
my very last try for Ronski: i did that say not as a fact, are you that stupid or do you ignore me ;)
shame on you playing this game you do. but i dont wonder really.

332
General Chat / Re: DDoS and the facts about it
« on: Wednesday, June 08, 2016, 14:57:03 PM »
i know i am not the clown, what about you? you dont get it, right.
so say what you want, i dont care. maybe others do understand. if not, no more a place for me.
i dont know why other admins look on what you are doing. Paulo, Nate, ELiZ, the real admins. but i should not care anymore. i really hope i can give a feedback in here in 2-3 weeks. then you would be the biggest clown on earth.

and if you are to stupid or scared to find those entries, then - again - call a admin that can do it!

333
General Chat / Re: DDoS and the facts about it
« on: Wednesday, June 08, 2016, 12:08:51 PM »
201.29.60.184 < see edit notes;.
187.78.164.96
None of those IPs are in our database and logs, so If I have played with them, how does it wasn't logged anywhere other than in your sever? I ask any other admin to check this, plz.

you can have the full server log of this day if you want. all what i say is the truth. and thanks for thinking that i would edit a logfile as well as i would try to kill this game. here with the logout of your account (i show this only because you say i am a liar):
Code: [Select]
L:\aa250logs\LogGUID.txt:L:\aa250logs\Logs\Server30.log:05/02/16 21:49:26 Log: 25AssistSM: Player GUID Computed 7695df6c0524a57e511e2f720f56db46(-) (slot #8) 201.29.60.184:53314 Possessed
L:\aa250logs\LogGUID.txt:L:\aa250logs\Logs\Server30.log:05/02/16 22:04:39 Log: 25AssistSM: Player GUID Computed 7695df6c0524a57e511e2f720f56db46(-) (slot #4) 201.29.60.184:64031 Possessed
L:\aa250logs\LogGUID.txt:L:\aa250logs\Logs\Server30.log:05/02/16 22:39:43 Log: 25AssistSM: Player GUID Computed 7695df6c0524a57e511e2f720f56db46(-) (slot #5) 201.29.60.184:54918 Possessed
L:\aa250logs\LogGUID.txt:L:\aa250logs\Logs\Server30.log:05/21/16 03:21:17 Log: 25AssistSM: Player GUID Computed 7695df6c0524a57e511e2f720f56db46(-) (slot #2) 187.78.164.96:55316 Possessed
L:\aa250logs\LogOut.txt:L:\aa250logs\Logs\Server30.log:05/02/16 22:04:33 Log: 25AssistSM: Lost Connection (slot #8) 201.29.60.184:53314 7695df6c0524a57e511e2f720f56db46(-) Possessed
L:\aa250logs\LogOut.txt:L:\aa250logs\Logs\Server30.log:05/02/16 22:39:28 Log: 25AssistSM: Lost Connection (slot #4) 201.29.60.184:64031 7695df6c0524a57e511e2f720f56db46(-) Possessed
L:\aa250logs\LogOut.txt:L:\aa250logs\Logs\Server30.log:05/02/16 22:52:18 Log: 25AssistSM: Lost Connection (slot #5) 201.29.60.184:54918 7695df6c0524a57e511e2f720f56db46(-) Possessed
L:\aa250logs\LogOut.txt:L:\aa250logs\Logs\Server30.log:05/21/16 03:21:27 Log: 25AssistSM: Lost Connection (slot #2) 187.78.164.96:55316 7695df6c0524a57e511e2f720f56db46(-) Possessed

and i repeat, it was the server of =(wA'tNc)= we Ain't No clan \_/ - a present of mine to them. if you still say i do lie, then i will ask a player who was online that day. he will remember you. just that much about "i can't find any entries in our database". maybe you have to ask ELiZ, he can confirm this for sure. if you have the need doing so.

@ Ronski: i never did say as a fact (also not in #5) that it was Possessed. i only did say to Possessed that he should listen about the specialists (he made a joke about "my specialists" at shoutbox)

@ Teddy: sure the IP's are not from Possessed, i did never say. they all are from the region of Brazil. it's called a "local botnet". only this i did say. so the attacker is - no fact yet - from Brazil. that's all. i repeat, no need to comment more, i will come back with the results.

334
General Chat / Re: DDoS and the facts about it
« on: Tuesday, June 07, 2016, 13:11:20 PM »
can you give an answer to Mia's question?

335
General Chat / Re: DDoS and the facts about it
« on: Tuesday, June 07, 2016, 11:48:24 AM »
if you would understand more about this all ronski, then you would see that i did not tell shit in here at all. 2 of us here do know what happend, one is me.
i did talk about a FINAL proof from very high professionals, you should read more carefully and without emotions. would help you. for me its sure who it was.

and as so often, you do say i am a bigmouth and liar, so where is your proof? read the facts and tell me where i did lie. so wait until i will get the results. and btw., any other attack will change my mind about not taking action against it.

336
General Chat / Re: DDoS and the facts about it
« on: Tuesday, June 07, 2016, 02:00:32 AM »
just for the protocol Mr. Ronski. It is NOT me, who is doing these attacks. and again, give me 2-3 weeks and you will (maybe) have the proof. I am not able to catch DDoSser, but as i told here, i have the connection to guys who can (maybe) do it. it they dont can, then nobody can do it.

337
General Chat / Re: DDoS and the facts about it
« on: Monday, June 06, 2016, 19:12:29 PM »
:) this now is more then funny. also a reason i left all this. some of you do know that it is almost impossible to catch a fucking DDoS attacker. But with the trap i had to do befor the 4th attack has been done, there is a good change for the "top" ones of Switzerland to get the attacker. I do really hope that they can do it. so maybe just wait, stop talking about things you do not know and be surpriced. i bet you will be. then i guess some of you in here do have finally no more friends in here. and that will not be me ;). shame, but the truth will help you maybe a bit to forget. cya when i get the results (would take about 3-4 weeks, because they have other priorities then this).

338
General Chat / Re: DDoS and the facts about it
« on: Sunday, June 05, 2016, 10:35:54 AM »
last point from me:
i guess it is not only clear for you, for many others it is also. i would like to see possessed to be a man and tell in here that he did attacked my servers. as i already did tell, i will not take any actions against him. but it has to be stopped now. this would be the right step. and a sorry also wouldn't the the badest thing.
closed.

339
General Chat / Re: DDoS and the facts about it
« on: Sunday, June 05, 2016, 08:09:52 AM »
i start to like you Bart, but i guess you know that already :)

its like a company is building a car, then you change the weels. now you have control of the car?
you have to explain that a bit more :)

JonnyM and ELiZ did the job what is called today Assist. they did all needed to get this game running WITH honors (auth server) and cheat detection. therefore i give a very loud applause!
but as i did write above, the car is aa25 game, the wheels are aa25assist. that's a fact as well.

about the argument of needing admin rights on the car (the game itself) because of kicking hackers immediately is just a joke, but not even a good one. you know the well known servers are always populated with server owners with admin rights. so really no need to kick any player sitting inside the car (the game). first you have to proof - and you do very very long as i can see with this phyro (which i think is very good to have a correct proof before you ban) - then you have to ban. so it really doesn't matter if a player, who did maybe play this game for years with hacks, just plays another 5-6 hours.

it is just not correct doing so, jumping into the car (the game) as a driver. the owner did buy the car, you only changed the weels (assist). but i also dont care about this. most of you did not abuse it, that i can say here loud and clear. but the power point part is bullshit and you should stop that. because it is hidden.

and the part of restricting me here at the forum is also not correct. before a post of mine is released, an admin or mod has to "control" it. this is a poor part as well as banning pit after years for his behavior agaist a woman who maybe isn't that she do say to all. this i care about. because it looks to me (and others) that you will not hear some facts. YOU do decide what people can read and what not (sounds a bit like a dictatorship you are doing). and vegeta did already say it: we all pay for the server of the auth system (only one is needed). so maybe think again about that all.
doing steps like this will not take out the bullet in the breast of this game.

340
General Chat / Re: DDoS and the facts about it
« on: Saturday, June 04, 2016, 18:37:04 PM »
i start to like you Bart, but i guess you know that already :)

its like a company is building a car, then you change the weels. now you have control of the car?
you have to explain that a bit more :)

341
General Chat / Re: DDoS and the facts about it
« on: Saturday, June 04, 2016, 16:45:42 PM »
i did not say i will plan actions against him by law. i did say i will hold my rights to do so if it goes on. that's all.
its only a game, nothing more. so no need to play with some ones life. really not. but enough is enough, this was my message above.

and i did NEVER EVER manipulate any log files nor the post in here. possessed, it was on a server you did play, it was wantc's. also one of mine.

so now maybe time to stop that shit at all. shake hands, it was funny a bit, but now we should go back to normal.
ok?
and release that moderator shit on forum on my account. thanks.

342
General Chat / Re: DDoS and the facts about it
« on: Saturday, June 04, 2016, 12:14:54 PM »
I have no reason keep playing on any of your servers, as it would be unplayable for me.

only a short sequence of not playing on my server:
Code: [Select]
aa250logs\Logs\Server30.log:05/02/16 21:49:26 Log: 25AssistSM: Player GUID Computed 7695df6c0524a57e511e2f720f56db46(-) (slot #8) 201.29.60.184:53314 Possessed
aa250logs\Logs\Server30.log:05/02/16 22:04:39 Log: 25AssistSM: Player GUID Computed 7695df6c0524a57e511e2f720f56db46(-) (slot #4) 201.29.60.184:64031 Possessed
aa250logs\Logs\Server30.log:05/02/16 22:39:43 Log: 25AssistSM: Player GUID Computed 7695df6c0524a57e511e2f720f56db46(-) (slot #5) 201.29.60.184:54918 Possessed
aa250logs\Logs\Server30.log:05/21/16 03:21:17 Log: 25AssistSM: Player GUID Computed 7695df6c0524a57e511e2f720f56db46(-) (slot #2) 187.78.164.96:55316 Possessed

just another hint for you:
read all more carefully. i did never say that i will send the special forces to you down to Brazil. why should i? only because you did attack 4 times now my servers with DDoS ? :).

you did it again yesterday midnight. thanks a lot for that, because i had to set a trap for you. and remember, this is only a game. players can go to every other server as they like. i will for sure not start to cry when players will be kicked out. but maybe it will disturb the community and the picture of you as well. could be.

i will use your attack now for a test at my work as well as for the work together with the Government's special forces. but for sure i will hold my rights up for taking action against you by law.

343
General Chat / Re: DDoS and the facts about it
« on: Friday, June 03, 2016, 15:10:14 PM »
fact #5:

because its only a game, i dont really care. i did ask - listen Possessed - my "specialists" at work. and i was really surprised, because they offered
me - oh yeah, i forgot to say what part of specialists they are. they are our ciber crime specialist, btw. at one of the biggest financial institute
of Switzerland - to contact the friends of them at the Swiss Gouverment working for Melanie (this is the Swiss part of the NSA in the States) to analyse
my router/firewall logs in a very deep way. i do stay back with this, but if you try it again, i would like to see what happend there; it will be
a kind of test for me what they can do.

344
General Chat / Re: DDoS and the facts about it
« on: Friday, June 03, 2016, 15:09:13 PM »
fact #4:                  

this attack is done by a method called smurf attack. my router had within 60 minutes 100'000 request to handle. he did it, but it went laggy for sure.
so all player did leave the nomad servers because of that. as a result of it, you can have a look at the end of my router log after stoping the attack:                     

Code: [Select]

02.06.2016 21:40 191.36.176.138:44560  192.168.1.61:8080          [type=Flood-Detection(4026531840)] TCP-Flood Action: Drop Packet
02.06.2016 21:40 179.4.87.187:13288    192.168.1.61:8080          [type=Flood-Detection(4026531840)] TCP-Flood Action: Drop Packet
02.06.2016 21:40 191.203.201.27:57443  192.168.1.61:8080          [type=Flood-Detection(4026531840)] TCP-Flood Action: Drop Packet
02.06.2016 21:40 191.82.98.255          92.107.22.140              [type=ICMP-Decoder(4043309086)] icmp-smurf Action: Drop Packet
02.06.2016 21:41 179.182.157.255        92.107.22.140              [type=ICMP-Decoder(4043309086)] icmp-smurf Action: Drop Packet
02.06.2016 21:41 191.6.100.255          92.107.22.140              [type=ICMP-Decoder(4043309086)] icmp-smurf Action: Drop Packet
02.06.2016 21:41 191.223.54.255        92.107.22.140              [type=ICMP-Decoder(4043309086)] icmp-smurf Action: Drop Packet
               
                     
you can easy see that my router could catch the end of the attack with this entries (see also above, no entries there after the real attack:

Code: [Select]
02.06.2016 21:40 191.82.98.255          92.107.22.140              [type=ICMP-Decoder(4043309086)] icmp-smurf Action: Drop Packet
02.06.2016 21:41 179.182.157.255        92.107.22.140              [type=ICMP-Decoder(4043309086)] icmp-smurf Action: Drop Packet
02.06.2016 21:41 191.6.100.255          92.107.22.140              [type=ICMP-Decoder(4043309086)] icmp-smurf Action: Drop Packet
02.06.2016 21:41 191.223.54.255        92.107.22.140              [type=ICMP-Decoder(4043309086)] icmp-smurf Action: Drop Packet
                  

this means that the attacker system had IP adresses of:

191.82.98.255
179.182.157.255   
191.6.100.255
191.223.54.255   
                     
                     
this does mean that the attacking servers are located at - funny but true - Brazil.

345
General Chat / Re: DDoS and the facts about it
« on: Friday, June 03, 2016, 15:08:25 PM »
fact #3:

using a local bot net is much more cheap then using a big one, working with computers together loacated all over the world.
the following extract of my router logfile does show:
Code: [Select]
Date Time Source Port Target Type Action IP Location

02.06.2016 20:34:47 191.22.145.76 11256 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.164.61.48 22765 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.153.233.208 13013 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:47 191.50.131.29 58317 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.41.38.220 34340 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.75.189.181 32913 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:47 191.88.179.46 56253 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:47 191.23.31.159 24530 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.168.85.128 57035 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 179.141.255.122 5283 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.233.32.56 21893 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Japan
02.06.2016 20:34:47 179.55.60.239 24615 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.182.107.232 25673 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.212.139.126 50328 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.29.246.181 36160 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.93.29.116 15848 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:47 179.96.148.253 37840 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.164.8.87 17908 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 179.253.198.231 54719 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.57.26.104 21420 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.209.228.181 3216 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 179.122.198.187 58627 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.217.16.223 786 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.94.55.176 47195 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:47 179.129.118.226 10919 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:47 191.197.49.208 22846 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.230.45.116 26206 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.173.23.55 26431 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.192.246.243 4652 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.122.133.134 46124 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.130.102.199 31634 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.90.32.236 27 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.182.54.75 6475 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.104.66.6 32630 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.69.19.39 3270 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.229.46.216 12745 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.230.31.154 4102 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 179.15.60.114 30438 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.84.136.150 27849 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Argentina
02.06.2016 20:34:48 179.212.25.176 38225 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.60.136.95 15975 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.114.226.146 36411 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:48 191.68.68.176 50488 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.127.202.85 35969 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:48 191.136.147.227 1971 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.102.221.254 8107 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.10.180.207 53979 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.59.40.2 29224 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.141.14.246 56847 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.157.213.83 10573 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.223.185.72 2671 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.87.28.67 44763 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Bolivia
02.06.2016 20:34:48 179.58.117.62 51689 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:48 191.117.2.220 3593 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:48 191.119.158.20 9154 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:48 191.134.50.115 36094 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.229.133.28 27148 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.238.103.51 29667 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Ireland
02.06.2016 20:34:48 191.182.239.204 35494 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.106.139.155 24260 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.35.194.247 64275 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.94.23.29 63218 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.118.222.163 2919 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:48 191.27.96.206 11391 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.22.146.17 19425 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.11.91.82 33318 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.60.192.203 20561 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 179.86.104.34 39607 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 179.218.127.28 42472 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.199.255.166 25818 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 179.32.196.75 59188 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.4.192.93 12852 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.76.33.138 55070 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.165.175.142 43483 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.95.208.113 65522 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.248.129.183 39598 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.106.168.110 34871 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.43.30.162 8050 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.85.215.114 9905 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Argentina
02.06.2016 20:34:48 191.72.34.179 22186 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.94.68.134 10479 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.66.64.165 50720 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.115.105.166 25374 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:48 191.187.3.157 59211 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.211.201.42 32162 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.80.174.196 60143 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Argentina
02.06.2016 20:34:48 179.206.37.107 25701 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.34.31.78 45483 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.84.30.220 35974 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Argentina
02.06.2016 20:34:48 179.183.10.219 54594 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.14.217.246 34220 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.198.54.4 65223 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.196.86.68 32617 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.142.41.22 14115 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.59.10.158 39024 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.104.203.72 30956 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.83.189.236 31847 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Argentina
02.06.2016 20:34:48 191.179.65.11 9546 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.48.136.52 6813 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.248.106.69 54866 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.168.196.152 1114 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.111.71.124 31493 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 179.226.109.5 24284 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.74.70.174 49179 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.239.130.202 56528 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Japan
02.06.2016 20:34:48 191.86.199.141 13259 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.225.110.213 39624 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.65.2.8 35147 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.183.141.66 18078 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.239.207.214 20752 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.183.155.44 56682 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.86.33.76 30015 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 191.67.57.227 16239 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Colombia
02.06.2016 20:34:48 191.197.71.252 19314 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil
02.06.2016 20:34:48 179.9.182.88 19953 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:49 191.117.3.197 27190 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:49 191.223.2.49 39992 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Chile
02.06.2016 20:34:49 179.98.174.186 23343 192.168.1.61:8080 [type=Flood-Detection(4026531840)] Drop Packet Brazil

Pages: 1 ... 21 22 [23] 24 25 ... 185

Download Assist

×

Download Game Client

Important: Battletracker no longer exists. However, old Battletracker accounts may still work. You can create a new 25Assist account here

Download Server Manager