• Unfortunately, we have experienced significant hard drive damage that requires urgent maintenance and rebuilding. The forum will be a state of read only until we install our new drives and rebuild all the configurations needed. Please follow our Facebook page for updates, we will be back up shortly! (The forum could go offline at any given time due to the nature of the failed drives whilst awaiting the upgrades.) When you see an Incapsula error, you know we are in the process of migration.

about EP3.3 Service-side security settings

Newbie Spellweaver
Joined
Feb 7, 2011
Messages
29
Reaction score
0
sorry ,Theme repeated。


:$:The normal operation of the service side, but an attacker to connect to the server, the monster disappears. Please help me, thank you.

61.152.154.39 Is the IP of the attacker, Is the IP of the attacker, less than a second.
====================================================================
04-02 16:07:32|Socket Connect SocketIndex[181] PeerIP[ 61.152.154.39] Port[63532]
04-02 16:07:32| [Notify] Close all UDP Socket for NPCServer!!
04-02 16:07:32|Socket Closed Client( 5.177.170.121:6043) SocketType(6) |SockIdx( 0)| MaxWriteBufCounts[ 1] ==> reason 16384[0X004000], deletedPacketCount(0)
04-02 16:07:32|Socket Closed Client( 5.177.170.121:6045) SocketType(6) |SockIdx( 1)| MaxWriteBufCounts[ 1] ==> reason 16384[0X004000], deletedPacketCount(0)
................................

04-02 16:07:32| UDP Opened for NPC_Server_0(MapIndex[1001] IP[ 5.177.170.121], Port[6043])
04-02 16:07:32| UDP Opened for NPC_Server_1(MapIndex[1002] IP[ 5.177.170.121], Port[6045])
...............................

04-02 16:07:32| [Notify] Open all UDP Socket for NPCServer!! Count(163)
04-02 16:07:32|Socket Closed Client( 61.152.154.39:63532) SocketType(6) |SockIdx( 181)| MaxWriteBufCounts[ 1] ==> reason 6[0X000006], deletedPacketCount(0)
04-02 16:07:32| [Notify] Close all UDP Socket for NPCServer!!
04-02 16:07:32|Socket Closed Client( 5.177.170.121:6043) SocketType(9) |SockIdx( 0)| MaxWriteBufCounts[ 0] ==> reason 16384[0X004000], deletedPacketCount(0)
04-02 16:07:32|Socket Closed Client( 5.177.170.121:6045) SocketType(9) |SockIdx( 1)| MaxWriteBufCounts[ 0] ==> reason 16384[0X004000], deletedPacketCount(0)

====================================================================
 
Retired (Goddamn idiots)
Joined
Dec 3, 2003
Messages
391
Reaction score
483
1. One post is enough to express the fact that you have no idea.
2. Just because an IP address shows, it does not mean it's an attacker.
3. In the case of it being the attacker, an IP address is absolutely useless, in most cases that person will use an ordinary proxy to convey such an attack.
4. You're just a paranoid imbecile.
 
Upvote 0
Newbie Spellweaver
Joined
Feb 7, 2011
Messages
29
Reaction score
0
Language communication is difficult I said little, you are apparently not affected by this attack, I don't expect you to recognize the importance of recording.
 
Upvote 0
Experienced Elementalist
Joined
Nov 30, 2008
Messages
271
Reaction score
0
WOW.. Clearly you didn't read what he said. So if you start seeing 24.79.78.161 in your logs it means I must be an attacker too!


(Did I just say my IP out loud?)
 
Upvote 0
Newbie Spellweaver
Joined
Feb 7, 2011
Messages
29
Reaction score
0
Why do not you take a look at the system record, this is an unusual connection.
 
Upvote 0
Back
Top