- Anzeige -

FLOODING flooding attack from WAN

In diesem Forum geht es um alle Störungen im Kabelnetz von Unitymedia, egal ob analoges TV und Radio, digitales TV und Radio, Internet oder Telefonie.
Wichtig:
  • Kunden aus Hessen und Nordrhein-Westfalen können über die Rufnummer 0221 / 466 191 00 Hilfe bei allen Problemen in Anspruch nehmen.
  • Kunden aus Baden-Württemberg können über die Rufnummer 0711 / 54 888 150 Hilfe bei allen Problemen in Anspruch nehmen.

Re: FLOODING flooding attack from WAN

Beitragvon Grothesk » 21.11.2010, 21:36

Code: Alles auswählen
Jan 1 00:00:22 Block WAN PING is enabled.

Mach den 'BLock' mal aus.
Grothesk
Kabelkopfstation
 
Beiträge: 4830
Registriert: 13.01.2008, 17:00
Wohnort: Köln-Bayenthal

Re: FLOODING flooding attack from WAN

Beitragvon cradleofdsl » 24.11.2010, 19:04

Also nach dem erfolgreichen update, ist das problem nach wie vor da. Aber nun ist es weniger das Flooding Ping sonder das Discover.

Ich denke um es genauer zu sagen das es wohl vorher auch schon das problem war um der aussage von " oxygen" recht zu geben.

Ich habe meine sister gebeten die genauen zeiten aufzuschreiben in den sie aus dem netz fliegen und es passt zu genau den rot markierten zeilen. Bin nu wieder bei null, hab versucht mit google etwas zu finden aber erfolglos. Habt ihr vielleicht noch eine idee? Tausend dank schonmal für alle tips die ihr mir bis jetzt gegeben habt.

Hier das Protokoll :
Zeit Benachrichtigung
Nov 24 15:16:57 DHCP: Server receive REQUEST from 00:18:de:73:0c:5a.
Nov 24 15:16:53 DHCP: Server sending ACK to 192.168.0.101. (Lease time = 86400)
Nov 24 15:16:53 DHCP: Server receive REQUEST from 00:18:de:73:0c:5a.
Nov 24 15:16:05 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 24 14:48:33 DHCP: Server sending ACK to 192.168.0.100. (Lease time = 86400)
Nov 24 14:48:33 DHCP: Server receive REQUEST from 00:1f:cf:52:7a:12.
Nov 24 14:48:33 DHCP: Server sending OFFER of 192.168.0.100.
Nov 24 14:48:33 DHCP: Server receive DISCOVER from 00:1f:cf:52:7a:12.
Nov 24 14:46:04 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 24 14:16:04 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Zeit Benachrichtigung
Nov 24 13:58:43 DHCP: Server sending ACK to 192.168.0.100. (Lease time = 86400)
Nov 24 13:58:43 DHCP: Server receive REQUEST from 00:1f:cf:52:7a:12.
Nov 24 13:58:43 DHCP: Server sending OFFER of 192.168.0.100.
Nov 24 13:58:43 DHCP: Server receive DISCOVER from 00:1f:cf:52:7a:12.
Nov 24 13:46:03 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 24 13:45:05 Drop PING request from WAN (ip:202.103.179.25).
Nov 24 13:43:51 DHCP: Server sending ACK to 192.168.0.100. (Lease time = 86400)
Nov 24 13:43:51 DHCP: Server receive REQUEST from 00:1f:cf:52:7a:12.
Nov 24 13:16:03 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 24 12:46:03 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.

Zeit Benachrichtigung
Nov 23 18:30:31 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 23 18:18:51 Drop PING request from WAN (ip:218.202.154.174).
Nov 23 18:18:36 DHCP: Server sending ACK to 192.168.0.100. (Lease time = 86400)
Nov 23 18:18:36 DHCP: Server receive REQUEST from 00:1f:cf:52:7a:12.
Nov 23 18:00:31 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 23 17:38:16 DHCP: Server sending ACK to 192.168.0.100. (Lease time = 86400)
Nov 23 17:38:16 DHCP: Server receive REQUEST from 00:1f:cf:52:7a:12.
Nov 23 17:30:31 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 23 17:25:37 DHCP: Server sending ACK to 192.168.0.101. (Lease time = 86400)
Nov 23 17:25:37 DHCP: Server receive REQUEST from 00:18:de:73:0c:5a.

Zeit Benachrichtigung
Nov 23 17:25:34 DHCP: Server sending ACK to 192.168.0.101. (Lease time = 86400)
Nov 23 17:25:34 DHCP: Server receive REQUEST from 00:18:de:73:0c:5a.
Nov 23 17:09:45 DHCP: Server sending ACK to 192.168.0.100. (Lease time = 86400)
Nov 23 17:09:45 DHCP: Server receive REQUEST from 00:1f:cf:52:7a:12.
Nov 23 17:09:45 DHCP: Server sending OFFER of 192.168.0.100.
Nov 23 17:09:45 DHCP: Server receive DISCOVER from 00:1f:cf:52:7a:12.
Nov 23 17:00:31 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 23 16:30:30 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 23 16:00:31 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 23 15:30:30 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Zeit Benachrichtigung
Nov 22 19:31:11 DHCP: Server sending ACK to 192.168.0.102. (Lease time = 86400)
Nov 22 19:31:11 DHCP: Server receive REQUEST from 00:25:a0:05:5a:c4.
Nov 22 19:31:11 DHCP: Server sending OFFER of 192.168.0.102.
Nov 22 19:31:11 DHCP: Server receive DISCOVER from 00:25:a0:05:5a:c4.
Nov 22 19:05:43 DHCP: Client receive ACK from 80.69.97.244, IP=95.222.74.153, Lease time=3600.
Nov 22 18:58:44 DHCP: Server sending ACK to 192.168.0.100. (Lease time = 86400)
Nov 22 18:58:44 DHCP: Server receive REQUEST from 00:1f:cf:52:7a:12.
Nov 22 18:58:44 DHCP: Server sending OFFER of 192.168.0.100.
Nov 22 18:58:44 DHCP: Server receive DISCOVER from 00:1f:cf:52:7a:12. Nov 22 18:51:31 DHCP: Server sending ACK to 192.168.0.101. (Lease time = 86400)


Ein Flooding Ping konnte ich nicht mehr in dem Protokoll finden.
Unter den Menschen
gibt es viel mehr Kopien
als ORIGINALE.
cradleofdsl
Kabelneuling
 
Beiträge: 6
Registriert: 21.11.2010, 09:17
Wohnort: HSK

Vorherige

Zurück zu Störungen im Kabelnetz von Unitymedia

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 13 Gäste