SuperHub - Do you really need to disable firewall?

harveyadam · 24-02-2011, 06:53

Hello. I've followed advice on this forum regarding the SuperHub and speed / ping issues. Sure enough disabling IP Flood detection AND the Firewall cured my pingtest problem (going from grade F to grade A), however, reverting to Firewall enabled I saw no difference - still 31mb/s down, 3mb/s up and Grade A on the ping test. So why bother disabling the firewall?

Peter_ · 24-02-2011, 07:31

If it works leave alone.

jb66 · 24-02-2011, 09:10

When I have ip flood protection on I can't browse while using torrents and web pages take ages to load all other firewall features don't make a difference to me.

Kymmy · 24-02-2011, 09:13

IP Flood protection should only effect traffic that generates lots of connections from the same source (like P2P, some games)

StevenJohnson · 24-02-2011, 13:15

Doesn't make any difference to what I disable or enable, still get crappy results from wireless...

Once again VM make a mess of what was once a trouble free broadband service. When they got their money grabbing hands on Blueyonder it was all down hill, now they get their hands on a Netgear device and mess that up!!

Peil · 24-02-2011, 13:17

Flood detection killed my connection, I could barely get onto the router itself to amend the settings when it was turned on and opening an external webpage timed out 4 out of 5 times.

Peter_ · 24-02-2011, 13:32

Quote:

Originally Posted by Peil

Flood detection killed my connection, I could barely get onto the router itself to amend the settings when it was turned on and opening an external webpage timed out 4 out of 5 times.

If you cannot access the Superhub then simply pinhole resetting will regain your access.

qasdfdsaq · 24-02-2011, 15:51

Quote:

Originally Posted by Kymmy

IP Flood protection should only effect traffic that generates lots of connections from the same source (like P2P, some games)

I believe actually IP flood detection only affects traffic that doesn't generate any connections, i.e. connectionless traffic. It seems to either then overload itself, or drop all traffic from said IP rather than just the connectionless traffic it detects as a "flood".

Kymmy · 24-02-2011, 15:53

Not really IP flood detection then

I wonder who names these sort of things

qasdfdsaq · 24-02-2011, 16:19

Well it is still IP flood detection, it's just connectionless IP traffic that seems to trigger it the most. Connectionless UDP and ICMP traffic is still IP. It may also protect against TCP/IP SYN floods, which in fact trying to make too many connections but those connections won't actually exist - though in practice an actual SYN flood is quite rare. The connectionless stuff is what seems to trigger it in most cases though.

Chrysalis · 24-02-2011, 17:17

to fix the known packetloss issues only flood detection needs to be ruened off, I also disable the firewall out of personal preference as I am not a fan of SPI firewalls. Not to mention I think the superhub issues are linked to resource saturation issues, so using SPI wont help that.

AndyCalling · 25-02-2011, 12:12

I have flood detection off, firewall off and port scan detection disabled as well and I still get a failed ping test with 100% packet loss. The router doesn't seem to get packet loss in any other usage situations though.

Mick Fisher · 25-02-2011, 15:06

I get a @Unable to run packet loss test@ on my wired desktop although my wireless laptop runs the test OK and gets an 'A' rating.

I spent some time trying to find out why and fix the issue but gave up in the end.

I also cannot play movie trailers from IMDB on both machines. The Laptop did play them when it was 'out of the box' but somewhere along the line the ability was lost.

I suspect some security measure I have taken is at the bottom of all this but I can't find it.

Sometimes minor issues like these are just not worth the time spent trying to fix them.