Ping issues

[evo17paul]

Hi all,
Prior to the latest firmware upgrade if I ran a portscan using ShieldsUp on www.grc.com the application returned stealth as I have no port forwarding setup and the unit was not set to reply to pings.

Now the superhub has been upgraded to latest R25 firmware the unit is failing the test even with all the services turned on, and its failing because its responding to pings.

Can anyone help me in turning off ping response please?

Thanks

Paul

[Neo-Tech]

Go to your SuperHub settings page (http://192.168.1.1, username: admin; password: changeme; unless you've changed it.)

Click on Advanced Settings > DMZ Host > Untick Respond to WAN Ping.

[evo17paul]

Thanks for the reply Neo-Tech
Unfortunately this is already unticked / turned off as it was previously before superhub got upgraded.

[Neo-Tech]

Tick it, click apply, reboot the SuperHub, login again and untick it, apply, and reboot.

Unfortunately, the SuperHub's firmware is still pretty mediocre.

[evo17paul]

I think mediocre is very polite :)
Unfortunately tried your suggestion and still no luck :mad:

[Neo-Tech]

Haha ;)

Hmm, it's probably another bug on the SuperDud. Try resetting the settings to factory and see if it makes any difference.

[evo17paul]

Thanks again Neo-Tech.

Was pondering resetting to factory defaults, do you know if it resets the password back to a factory default or is the shipped password the default?

Paul

[Neo-Tech]

Should be the standard changeme password, if not, use the one on the Dud ;)

[evo17paul]

Now this is weird.
By shoving a pin in the reset hole, have reset back to defaults.... good at least that works !!

Turned off, left a bit, turned back on
Reconfigured bits on the superhub for my own configuration
Do another port scan with grc.com shieldsup, now reveals SSH, Telnet, HTTP and HTTPS being close, whereas before these were stealth

And still the damn thing replies to pings, even though I unticked the Respond to ping on WAN port

How the hell, could NetGear release this pile of crap !

[Chrysalis]

R25 is worse than R20 I did try to warn people here.

[Hiddendeath]

aye stay away from R25, this release needs to be shot and put down for good.

[Neo-Tech]

Although the beta firmwares were great IMO.

They released R25 without even giving it to us testers first, says it all really.

[Chrysalis]

well we got it but what for? 2 days maybe?

R24 lasted about a week, then there was a gap, then R25 came out with disabled ssh an official change, then very quickly it was made live.

[Mick Fisher]

well we got it but what for? 2 days maybe?

R24 lasted about a week, then there was a gap, then R25 came out with disabled ssh an official change, then very quickly it was made live.
So reading between the lines, R25's main purpose is to disable SSH and to hell that the firmware introduces even more bugs. :rolleyes:

[Chrysalis]

the changelog's between R24 and R25 only had ssh as an extra change, although R24 had a couple of other listed changes over R20.

However is evident in the gui there is other under the hood changes that were not listed.

R24 seemed fine, I didnt notice anything better or worse on it, R25 even tho only apparently a minor update suddenly had multiple issues.

[Mick Fisher]

I find that after yet another spontaneous reboot I have R25 now. :(

So far I haven't noticed any problems but it's early days, I haven't DL'ed anything yet :erm: