Quote:
Originally Posted by qasdfdsaq
Not quite true.
The Superhub works fine for most average customers out of the box.
Flood protection really only affects large numbers of stateless packets, i.e. where somebody is pinging your connection from outside. This isn't typical use, and really only affects pingtest.net and similar tests, it has virtually no effect on actual internet usage. Most internet activity is TCP, which is unaffected by flood protection, you don't need to disable flood protection to get a useable net connection. You only need to disable it for test sites that send a hundred pings to your modem per second.
|
However for some reason IP Flood also detects LAN side flooding????????????
Description Count Last Occurence Target Source
Illegal TCP header 1 Sun Dec 12 04:44:54 2010 192.168.0.2:0 24.128.136.198:0
LAN-side UDP Flood 1 Sun Dec 12 04:44:58 2010 92.124.19.123:45578 192.168.0.2:13459
Illegal TCP header 1 Sun Dec 12 04:45:01 2010 192.168.0.2:0 24.128.136.198:0
LAN-side UDP Flood 3 Sun Dec 12 04:45:06 2010 194.168.8.100:53 192.168.0.2:56370
Illegal TCP header 1 Sun Dec 12 04:45:07 2010 192.168.0.2:0 24.128.136.198:0
LAN-side UDP Flood 1 Sun Dec 12 04:45:12 2010 206.48.228.157:29122 192.168.0.2:13459
Illegal TCP header 3 Sun Dec 12 04:45:26 2010 192.168.0.2:0 24.128.136.198:0
LAN-side UDP Flood 8 Sun Dec 12 04:46:09 2010 194.168.4.100:53 192.168.0.2:50398
SYN Flood 1 Sun Dec 12 04:48:50 2010 192.168.0.2:13459 67.168.3.56:54577
Illegal TCP header 4 Sun Dec 12 04:58:08 2010 192.168.0.2:0 79.254.133.128:0
LAN-side UDP Flood 3 Sun Dec 12 04:58:47 2010 94.242.135.59:18575 192.168.0.2:13459
Illegal TCP header 1 Sun Dec 12 04:58:49 2010 192.168.0.2:0 79.254.133.128:0
LAN-side UDP Flood 5 Sun Dec 12 04:59:00 2010 71.72.82.14:54591 192.168.0.2:13459
Illegal TCP header 1 Sun Dec 12 04:59:04 2010 192.168.0.2:0 79.254.133.128:0
LAN-side UDP Flood 5 Sun Dec 12 05:00:05 2010 224.0.0.252:5355 192.168.0.2:62422
Illegal TCP header 14 Sun Dec 12 05:13:15 2010 192.168.0.2:0 87.14.229.225:0
LAN-side UDP Flood 20 Sun Dec 12 05:14:35 2010 70.239.249.207:53020 192.168.0.2:13459
Illegal TCP header 78 Sun Dec 12 05:23:12 2010 192.168.0.2:0 24.29.68.168:0
SYN Flood 1 Sun Dec 12 05:25:15 2010 192.168.0.2:13459 67.63.96.230:40241
Illegal TCP header 2 Sun Dec 12 05:26:01 2010 192.168.0.2:0 212.183.88.81:0
LAN-side UDP Flood 25 Sun Dec 12 05:29:01 2010 111.254.121.200:17625 192.168.0.2:13459
Illegal TCP header 1 Sun Dec 12 05:29:42 2010 192.168.0.2:0 110.174.192.78:0
SYN Flood 1 Sun Dec 12 05:30:12 2010 192.168.0.2:13459 83.87.90.84:3604
LAN-side UDP Flood 7 Sun Dec 12 05:30:34 2010 121.54.22.249:16846 192.168.0.2:13459
Illegal TCP header 1 Sun Dec 12 05:30:35 2010 192.168.0.2:0 212.183.88.81:0
LAN-side UDP Flood 2 Sun Dec 12 05:30:38 2010 124.150.101.151:57344 192.168.0.2:13459
Illegal TCP header 1 Sun Dec 12 05:30:38 2010 192.168.0.2:0 212.183.88.81:0
LAN-side UDP Flood 46 Sun Dec 12 05:34:26 2010 95.211.88.51:80 192.168.0.2:13459
Teardrop or derivative 36 Sun Dec 12 05:37:24 2010 192.168.0.255:137 192.168.0.3:137
LAN-side UDP Flood 285 Mon Dec 13 19:28:06 2010 87.19.104.98:45950 192.168.0.2:13459
Why? I don't know and look for an answer. The above is from someone elses Superhub.