Network Safety Scan

[system]

So I ran the Network Safety Scan and it tells me my router is infected (it’s an Netcomm NF4V) so I go through the motions change the SSID and user name / Password blah blah but it still tells me that the router can be hacked because it can be logged into with user/user which I go and do just to see WTF it was on about turns out I can but it also turns out you can’t do a damn thing via this way in except see the info on connection speed, run the Basic connection setup (useless without my ISP’s User name / password) you can also run a limited set of diagnostics and update the firmware (which doesn’t work because manual updating of the Firm Ware has been fully disabled it’s pushed via my ISP only)

[bob3160]

@aaron551 post:1

So I ran the Network Safety Scan and it tells me my router is infected (it’s an Netcomm NF4V) so I go through the motions change the SSID and user name / Password blah blah but it still tells me that the router can be hacked because it can be logged into with user/user which I go and do just to see WTF it was on about turns out I can but it also turns out you can’t do a damn thing via this way in except see the info on connection speed, run the Basic connection setup (useless without my ISP’s User name / password) you can also run a limited set of diagnostics and update the firmware (which doesn’t work because manual updating of the Firm Ware has been fully disabled it’s pushed via my ISP only)

Welcome to the forum.

Is there a question ???

[system]

There are really four areas you need to be concerned with (other than opening up ports & DMZ zones, etc. WITHIN your router) that you can button up without Avast.

1. Change default Admin and User passwords…use strong PW which means Upper Case Letter, special character, number, and letters. If you have ability for “graphical authentication” enable that too.
2. Turn off any FTP and/or remote (ie. web) access ability.
3. Make sure security PW for Wifi is enabled and something stronger than WEP…good example is WPA-Personal (WPA2).
   This will give you better protection and also Wireless N ability
4. Last option if is after you hook all computers/devices up to the Wifi and they login automatically you can go back and turn off SSID…the “broadcast” of your Wifi…it is still there just not visible. Many of the routers have a Guest Wifi and you can turn on this SSID because it is usually blocked from any access to router functions or rest of internal network…just a “bridge” to the internet.

[system]

@thekochs post:3

There are really four areas you need to be concerned with (other than opening up ports & DMZ zones, etc. WITHIN your router) that you can button up without Avast.

1. Change default Admin and User passwords…use strong PW which means Upper Case Letter, special character, number, and letters. If you have ability for “graphical authentication” enable that too.
2. Turn off any FTP and/or remote (ie. web) access ability.
3. Make sure security PW for Wifi is enabled and something stronger than WEP…good example is WPA-Personal (WPA2).
   This will give you better protection and also Wireless N ability
4. Last option if is after you hook all computers/devices up to the Wifi and they login automatically you can go back and turn off SSID…the “broadcast” of your Wifi…it is still there just not visible. Many of the routers have a Guest Wifi and you can turn on this SSID because it is usually blocked from any access to router functions or rest of internal network…just a “bridge” to the internet.

Hi thekochs yes I already do all that, Avast also tries to tell me the my router is infected simply because I choose to use OpenDNS’s 208.67.220.220 and 208.67.222.222 for my DNS servers in order to try and get me hooked into using their Avasts “Secure DNS” I wish Avast would stop telling porkies like this as there is nothing wrong in my setup

[Cast]

You sure its set up right? I have opendns set up as my dns service as well and avast doesnt detect anything wrong with my network.

[1234ava]

I use OpenDns too, no problem with Avast NSS so far, but I set the OpenDns dns in network tcp/iP4 properties in Windows, not in my router.

[bob3160]

@ aaron551
I’v e been using openDNS redirect on my router for several years. No warnings from Avast.

http://www.screencast-o-matic.com/screenshots/u/Lh/1429970360376-30515.png

Looks like you’ve reversed the order of the settings.

http://www.screencast-o-matic.com/screenshots/u/Lh/1429970573155-50283.png