I know there's a "bug" where LAN side packets are also picked up by the flood protection, but again this still only affects stateless packets and is a rare occurrence, most LAN traffic, like internet traffic is still stateful TCP which is ignored by the flood protection. Still *most* of the feedback on this forum about the Superhub is positive so clearly it still works for most people out of the box.
Barring any other "bugs" with the flood protection, speedtest.net traffic would be completely ignored by it so flood protection should have nothing to do with your speedtest problems.
Quote:
Originally Posted by jb66
You obviously don't have a hub, I couldn't browse and use torrents at the same time with it enabled. Even the Internet on it's own ground to a halt with it on
|
Do you use uTorrent by any chance? uTorrent recently (in the last year or so) implemented a new UDP based protocol (uTP) that is on by default. Like I said, the flood protection is easily triggered by stateless packets (i.e. UDP) so if you're torrenting with UDP, then this is why you have problems.
Most internet traffic (95%) is not UDP and would not trigger flood protection. Not to say it's particularly useful or well implemented, but to be honest it's still way too easy to DoS someone with an ICMP flood attack these days. You don't even have to use a DDoS.
As for the firewall, I've already made my opinions on NAT router firewalls clear many times - they're pointless and unsuccessful gimmicks that shouldn't be there in the first place, on any device. The Superhub's firewall is really no worse than your average crappy consumer router firewall.