[03:38:48] Incoming connection: 190.209.1.59:4663 [03:38:49] Incoming connection: 190.209.1.59:4919 [03:38:49] Incoming connection: 190.209.1.59:5175 [03:38:49] Incoming connection: 190.209.1.59:5431 [03:38:49] Incoming connection: 190.209.1.59:5687 [03:38:49] Incoming connection: 190.209.1.59:5943 [03:38:49] Incoming connection: 190.209.1.59:6199 [03:38:49] Incoming connection: 190.209.1.59:6455 [03:38:49] Incoming connection: 190.209.1.59:6711 [03:38:49] Incoming connection: 190.209.1.59:6967 [03:38:49] Incoming connection: 190.209.1.59:7223 [03:38:49] Blocking 190.209.1.59 due to a 'server full' attack (1)
[03:40:58] Incoming connection: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764 [03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764
[03:40:58] Packet was modified, sent by id: 3, ip: 190.209.1.59:4764
Es un ataque,deberias poner un Maxips(como el que viene con el paquete de samp server) ,y como eh leido en este foro,los ataques no solo depende de tu codigo,si no de tu host,tambien lei que podrias bloquear ip de china o rusia o de esos paises,donde suelen usar proxys e ip falsas los "hackers"(que la mayoria usan programas descargados de ******* y son niсos sin nada que hacer)
Para bloquear ips de paises,podrias usar GetPlayerIp,y buscar en ****** como comienzan las ip de esos paises. https://sampwiki.blast.hk/wiki/GetPlayerIp Tambien creo que con el callback OnIcomingConnection y una funcion puedes bloquear ips. https://sampwiki.blast.hk/wiki/BlockIpAddress https://sampwiki.blast.hk/wiki/OnIncomingConnection |
Lo que no me cabe es por que el servidor ha bloqueado el ataque automaticamente, la ip es de Chile, me preguntaba si se podнa hacer algo a lo legal.
http://www.elhacker.net/geolocalizac...t=190.209.1.59 La ip por lo que he recopilado es de la empresa Telmex (actual Movistar). El host (VPS) no da problemas, ha aguantado bastantes cosas, mas bien muchas. |