Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[FurryNutz]

You could if you wanted too. Set the systemlog to email you on any notifications to see if any WAN IP addresses show up. IF the logs show attempted WAN side IP addresses, maybe then you can set a rule to block that IP address then.

I've never seen or had any issues from the WAN side on any of my D-Link routers. Been safe and secure using router default settings and configuring SSID and PWs. I do keep FW up to date unless I'm testing something out. 

[Gattsu]

Any inbound traffic from the WAN side are blocked by default. The only way in is through remote management if enabled, but that is protected with a password.

The other way they can get in, is through the LAN ports but that secured in your house. Just make sure the doors and windows are locked. =)

The third way is wireless but it is already hidden and protected with WPA2 Authentication.

So far no known vulnerabilities with COVR system.

[02ebz06]

You could if you wanted too. Set the systemlog to email you on any notifications to see if any WAN IP addresses show up. IF the logs show attempted WAN side IP addresses, maybe then you can set a rule to block that IP address then.

I've never seen or had any issues from the WAN side on any of my D-Link routers. Been safe and secure using router default settings and configuring SSID and PWs. I do keep FW up to date unless I'm testing something out. 

Right now, I have it going to my Syslog server.  Guess I could write a script to scan it.

Speaking of firmware...

Router says
Current Firmware Version:    1.00, Fri 02 Jun 2017
Current Firmware Date:      2017-06-02 05:20:00

Web site (and in another thread here, says latest is 1.00B19 / 1.00B11 for Ext) with a date of Aug 17, 2017
Since firmware dates are different, I told the router to check for new firmware.
Said I was running the latest.

So, is it newer or not is the question...

=====================================================================================================================================================================

Any inbound traffic from the WAN side are blocked by default. The only way in is through remote management if enabled, but that is protected with a password.

The other way they can get in, is through the LAN ports but that secured in your house. Just make sure the doors and windows are locked. =)

The third way is wireless but it is already hidden and protected with WPA2 Authentication.

So far no known vulnerabilities with COVR system.

Good to know, thanks

[FurryNutz]

You can manually download the latest from the web site in case it hasn't been posted to the update server...

[GreenBay42]

It should be the same firmware (shipping). 

You can see the exact version on the router - 192.168.0.1/version.txt or dlinkrouter.local./version.txt

[02ebz06]

I get "Authetication Fail!" when I try that.

[GreenBay42]

Oh really? They might have removed that. Let me find out quick.

[GreenBay42]

Looks like you have to log in first. Log in normal and they just do the covr.local./version.txt or ip as in the previous message.

[02ebz06]

covr.local./version.txt    gave me the Authentication fail message but http://192.168.0.1/version.txt  worked.
Doesn't show the EXT version though. Guess you would have to log in there and do same.

Version
Firmware External Version : V1.00
Firmware Internal Version : V1.00b19
Date : 02, Jun, 2017


Thanks, good info to have handy.

[GreenBay42]

The firmware on the support site is the same. The date on the website is when it was posted on the website.

[02ebz06]

support.d-link.com shows the August date.

[GreenBay42]

correct. That is when it got posted to the support site.  If you look at the release notes it usually has the firmware date.

[FurryNutz]

http://forums.dlink.com/index.php?topic=72533.0