Naughty Lifco

Play Now
Status
Not open for further replies.
MentaL

MentaL

Jev For Admín!
VIP
Mar 3, 2004
3,843
552
385
Cardiff
I am not defending Lifco but wondering if these logs can be posted because really you cannot properly check for a DDOS against a server unless you got some sort of remote access directly to the server.... (most will require the assitance of a datacenter for network traffic logs)....

As for ddos... you really want to monitor inbound connections and so forth, unless you are saying he is attempting to overflow apache then ok you will have a connection amount in the apache logs, but this would also use proxied ips.... but if you mean sending all his upload bandwidth data from a home comnnection to a standard 10/100mbit then that sounds fishy.


Can you show me these logs because im finding it abit far fetched as of this moment.
 
kyndigs

kyndigs

LOMCN Developer
Developer
Feb 19, 2009
1,126
117
190
Reading, UK
Tom27 said:
I know that you see many tw@ts around LOMCN..
But lifco to DOS a server is just completely unbeleiveable bulls**t.

Everybody knows that lifco is one of the safest guys on LOMCN constantly helping anyone he can when he can & always releasing new sets of server files etc..

I know milo has backed u guys up but tbh I think its alot of rubbish.
Lifco has no reason in the world to do an attack on his own files..
Kinda stupid aint it?
Click to expand...

His amateur coding left a massive bug in the files allowing people to spawn mobs as he didnt set permissions right in the hero/slave. Which proved he didnt actually know what the hell he was doing in the first place.

The log is on the server, when i can connect ill gladly post it lol.
 
HeadHunter

HeadHunter

Golden Oldie
Golden Oldie
Jun 18, 2007
962
13
105
Stoke, UK
This thread is just getting stupidly childish now, none of you can really believe that Lifco did this. And I don't understand how a reliable Smod on these forums can go around giving out peoples I.p. Addresses, because that ain't sensible one bit when you think about what can be done with it. And secondly if Lifco wanted to screw the server up surely he'd either just create a hack and use it on the server or even just put a bug back into the server files, by rushing to conclusions you have all ****ed it up for all of us. No mod or person has ever released more than Lifco. 3-4 of the mods were promising a release of their server files, but only when they had set their server up and it had gained it's Market share let's say. We all know that Milo has a grudge against Lifco and alot of people don't like lifco either, but seriously to try and get rid of him in this way is insane.

/Jenix
 
kyndigs

kyndigs

LOMCN Developer
Developer
Feb 19, 2009
1,126
117
190
Reading, UK
TCP 192.168.1.65:80 87.194.182.226:64001 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64006 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64011 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64013 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64016 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64021 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64036 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64042 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64070 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64071 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64078 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64094 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64026 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64034 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64047 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64049 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64060 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64062 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64064 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64066 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64071 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64081 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64093 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64096 LAST_ACK

This goes on for a few pages, this is all i could salvage atm before being cut off again lol :/
 
solvent

solvent

LOMCN Veteran
Veteran
Jul 24, 2006
457
0
43
On The Sun
tbh if its true that lifco done this and and ppl atm belive he didnt coz of the stuff lifco release's etc and y would he dos he own server files..(bare it in mind seem lif has a nice rep for release's etc thats a perfect excuse to get numnuts on his side..) the server lifco aprently dos'd is lifco a gm on it or help run it? if not then wtf does it matter if there his files or not?.. means nothing.. imo

also lifco saying this ent true he ent dun fck all, then why the hell he running away from lomcn for good if he dun nothing wrong?
would ne of u lot run away if u havnt done nothing wrong or would u stay and just tell ppl to fo? coz i no wat i would do :) seems fishy tbh
 
solvent

solvent

LOMCN Veteran
Veteran
Jul 24, 2006
457
0
43
On The Sun
kyndigs said:
TCP 192.168.1.65:80 87.194.182.226:64001 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64006 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64011 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64013 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64016 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64021 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64036 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64042 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64070 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64071 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64078 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64094 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64026 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64034 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64047 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64049 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64060 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64062 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64064 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64066 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64071 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64081 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64093 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64096 LAST_ACK

This goes on for a few pages, this is all i could salvage atm before being cut off again lol :/
Click to expand...


serously this is crap ne 1 can spend 5mins typing that up got a printscreen?
 
kyndigs

kyndigs

LOMCN Developer
Developer
Feb 19, 2009
1,126
117
190
Reading, UK
solvent said:
serously this is crap ne 1 can spend 5mins typing that up got a printscreen?
Click to expand...

Why would i waste my time typing up loads of that ill gladly post the whole thing when i get it, thats from a week ago, the one this time is proxied.
 
kyndigs

kyndigs

LOMCN Developer
Developer
Feb 19, 2009
1,126
117
190
Reading, UK
Active Connections

Proto Local Address Foreign Address State

TCP 192.168.1.65:80 87.194.182.226:49190 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:49310 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:49328 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:49492 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:49496 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:49557 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:49781 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:49861 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50040 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50045 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50050 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:50051 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50131 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50138 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50356 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50360 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50367 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50371 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50373 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50423 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:50435 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50452 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50454 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50470 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50499 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50575 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:50583 CLOSING
TCP 192.168.1.65:80 87.194.182.226:50587 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50652 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50653 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50661 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50663 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50664 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50665 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50666 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50761 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:50979 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51019 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51121 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:51196 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:51200 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51329 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51336 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51337 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51430 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:51687 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51736 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51881 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:51907 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:52180 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:52272 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62815 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62816 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62828 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62851 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62871 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62922 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62923 CLOSING
TCP 192.168.1.65:80 87.194.182.226:62926 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62929 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:62931 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62932 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62934 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:62938 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:62939 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62940 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:62951 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:62956 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62958 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62961 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62962 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62963 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62964 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62973 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62974 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:62983 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:62994 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63012 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63016 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63026 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63027 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63028 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63030 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63046 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63053 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63054 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63058 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63066 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63075 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63079 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63081 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63092 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63106 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63115 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63116 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63121 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63124 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63128 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63147 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63158 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63170 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63185 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63212 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63213 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63214 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63215 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63245 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63253 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63273 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63274 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63297 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63302 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63307 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63309 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63313 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63315 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63319 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63341 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63367 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63391 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63394 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63395 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63401 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63403 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63404 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63405 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63408 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63430 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63436 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63437 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63449 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63537 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63619 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63628 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63629 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63644 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63657 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63668 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63670 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63677 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63683 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63690 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63697 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63731 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63779 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63787 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63793 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63794 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63812 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63830 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63837 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63846 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63865 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63868 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:63870 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63871 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63874 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63876 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63877 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63879 CLOSING
TCP 192.168.1.65:80 87.194.182.226:63922 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63932 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:63938 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:63957 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64001 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64006 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64011 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64013 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64016 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64021 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64036 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64042 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64070 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64071 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64078 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64094 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64126 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64134 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64147 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64149 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64160 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64162 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64164 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64166 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64171 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64181 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64193 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64195 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64196 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64216 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64220 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64224 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64277 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64318 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64319 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64321 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64369 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64372 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64375 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64379 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64444 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64446 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64453 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64466 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64480 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64481 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64482 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64496 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64500 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64504 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64509 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64549 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64591 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:64593 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64608 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64646 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64649 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64651 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64678 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64705 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64707 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64713 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64729 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64744 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64756 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64782 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64792 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64845 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64860 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64866 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64871 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64890 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64892 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64894 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64905 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64910 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64912 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64914 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64918 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64932 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:64934 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:64972 CLOSING
TCP 192.168.1.65:80 87.194.182.226:64973 CLOSING
TCP 192.168.1.65:80 87.194.182.226:65005 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:65055 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65098 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65154 ESTABLISHED
TCP 192.168.1.65:80 87.194.182.226:65169 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65280 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:65290 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:65320 FIN_WAIT_1
TCP 192.168.1.65:80 87.194.182.226:65323 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65325 CLOSING
TCP 192.168.1.65:80 87.194.182.226:65327 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65329 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65341 CLOSING
TCP 192.168.1.65:80 87.194.182.226:65357 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65368 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65416 LAST_ACK
TCP 192.168.1.65:80 87.194.182.226:65421 CLOSING
TCP 192.168.1.65:80 87.194.182.226:65468 LAST_ACK
TCP 192.168.1.65:1079 72.5.124.55:80 CLOSE_WAIT
TCP 192.168.1.65:1081 212.113.163.19:80 ESTABLISHED
TCP 192.168.1.65:4010 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4011 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4012 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4014 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4015 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4016 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4017 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4018 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4019 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4021 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4022 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4023 192.168.1.1:80 TIME_WAIT
TCP 192.168.1.65:4024 192.168.1.1:80 ESTABLISHED
TCP 192.168.1.65:5900 86.28.206.93:55531 ESTABLISHED
TCP 192.168.1.65:7200 81.103.165.168:50620 ESTABLISHED
TCP 192.168.1.65:7200 81.129.253.173:51281 ESTABLISHED
TCP 192.168.1.65:7200 82.29.17.51:8284 ESTABLISHED
TCP 192.168.1.65:7200 86.164.190.54:4244 ESTABLISHED
TCP 192.168.1.65:7200 87.55.61.31:51062 ESTABLISHED
TCP 192.168.1.65:7200 92.23.4.12:1114 ESTABLISHED
TCP 192.168.1.65:7200 92.237.124.183:49922 ESTABLISHED
 
solvent

solvent

LOMCN Veteran
Veteran
Jul 24, 2006
457
0
43
On The Sun
i ent sayin u did or didnt type it, im just saying it can easly be done, so maybe a print screen to secure to other ppl its real ?
 
kyndigs

kyndigs

LOMCN Developer
Developer
Feb 19, 2009
1,126
117
190
Reading, UK
solvent said:
i ent sayin u did or didnt type it, im just saying it can easly be done, so maybe a print screen to secure others its real ?
Click to expand...

Its hard enough to get on and copy this log atm, nevermind a print screen lol. Plus the one with lifcos ip was a week ago the one now is proxied.

Ill try get a print scrn of current one.
 
Far

Far

tinmymouthpl0x
Staff member
Administrator
May 19, 2003
20,683
34
3,288
520
believing tai over anyone is a bad choice to make.

i dont believe this for a second. like everyone keeps saying. what would be the motive behind it?

its obvious people on this forum report back here when their server has been dos'd, so why do it from his own ip, or even at all?
 
kyndigs

kyndigs

LOMCN Developer
Developer
Feb 19, 2009
1,126
117
190
Reading, UK
Ca
Farphit said:
believing tai over anyone is a bad choice to make.

i dont believe this for a second. like everyone keeps saying. what would be the motive behind it?

its obvious people on this forum report back here when their server has been dos'd, so why do it from his own ip, or even at all?
Click to expand...

Cause hes not as smart as he portrays...?

I am just stating what I found, i have nothing against lifco so i would have no reason to set him up...
 
kyndigs

kyndigs

LOMCN Developer
Developer
Feb 19, 2009
1,126
117
190
Reading, UK
SmavidDavid said:
name rings a bell, wernt u some nub off dragon?
Click to expand...

About as much of a nub as ben was... regardless of how i played dragon server which was a long time ago, doesnt reflect this situation, I dont know lifco so id have no reason to lie about this.

And sorry WHO ARE YOU?
 
transporter

transporter

LOMCN Veteran
Veteran
Jul 12, 2008
608
8
105
Darlington
solvent said:
i ent sayin u did or didnt type it, im just saying it can easly be done, so maybe a print screen to secure to other ppl its real ?
Click to expand...

Your a retard tbh, i know Lifco is a dodgy little man. He once hosted EvilMir server and said we could have his dedicated host for a year, we trusted him and sent him the files, he hosted it for a day and stole the files.

I believe he is definatley capable of doing a dos attack, he is just that type of person.
 
SmavidDavid

SmavidDavid

Playing Legend of Mir 5
Legendary
Jun 13, 2006
4,215
635
290
Worthing is depressing.
kyndigs said:
About as much of a nub as ben was... regardless of how i played dragon server which was a long time ago, doesnt reflect this situation, I dont know lifco so id have no reason to lie about this.

And sorry WHO ARE YOU?
Click to expand...

Says it in my name really....


And seriously, i still cant belive any of this bull crap.

1) post was made by a childish twit, who when he gets banned runs back under a new name.

2) All your proof could be typed... if you can highlight and copy paste.. whats so hard about "prnt screen"

3) WHY would lifco do it? Did you do something against he kindly asked you not too? Did you steal something? Surley hes not sad enough to do it for the fun of it.. Properly doesn't help Johny thinks its being done because servers soo "epic".

But wasn't it being ping'ed the other day by Andy/John?? You claimed it was them, again NO solid proof??!?! Again Tai.. you were the one once again stirring the **** up...
 
kyndigs

kyndigs

LOMCN Developer
Developer
Feb 19, 2009
1,126
117
190
Reading, UK
SmavidDavid said:
Says it in my name really....


And seriously, i still cant belive any of this bull crap.

1) post was made by a childish twit, who when he gets banned runs back under a new name.

2) All your proof could be typed... if you can highlight and copy paste.. whats so hard about "prnt screen"

3) WHY would lifco do it? Did you do something against he kindly asked you not too? Did you steal something? Surley hes not sad enough to do it for the fun of it.. Properly doesn't help Johny thinks its being done because servers soo "epic".

But wasn't it being ping'ed the other day by Andy/John?? You claimed it was them, again NO solid proof??!?! Again Tai.. you were the one once again stirring the **** up...
Click to expand...

1 - Screenshots cant be faked? lol

2 - Again, how the **** do i know why lifco did it, i logged onto server and saw his ip doing it, do you even read the other posts?

3 - I have a fulltime job, i have better things to do that type a ****ing log up to set someone up i dont even know.

4 - Lifcos bail out reaction says it all.

So 'smaviddavid' define for us all what you consider solid proof, a screenshot? lol...
 
Status
Not open for further replies.
Top Bottom