• May 14, 2025, 03:12:28 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 [2]

Author Topic: Webfilter fails after updating to 1.35NA  (Read 13922 times)

davevt31

  • Level 9 Member
  • ****
  • Posts: 1601
Re: Webfilter fails after updating to 1.35NA
« Reply #15 on: January 21, 2011, 09:21:52 AM »

Enable DNS Realy needs to ON for the webfilters to work.
Logged

MoonRock

  • Level 1 Member
  • *
  • Posts: 10
Re: Webfilter fails after updating to 1.35NA
« Reply #16 on: January 21, 2011, 02:50:25 PM »

Yep. After enabling the DNS Relay everything works now. Thanks.
Logged

tcr49

  • Level 1 Member
  • *
  • Posts: 10
Re: Webfilter fails after updating to 1.35NA
« Reply #17 on: January 22, 2011, 06:51:27 PM »

Interesting, so moonrock, you had Enable DNS relay "DISABLED" and when it was in that state the webfilters failed for you but simply enabling the dns relay setting made the webfilters work again?

By chance what settings do you have in the following:

SETUP>NETWORK SETTINGS>ROUTER SETTINGS>ENABLE DNS RELAY (checkbox)
SETUP>INTERNET>DYNAMIC IP (DHCP) INTERNET CONNECTION TYPE>PRIMARY DNS SERVER
SETUP>INTERNET>DYNAMIC IP (DHCP) INTERNET CONNECTION TYPE>SECONDARY DNS SERVER

On mine I have the ENABLE DNS RELAY checked but the webfilters are still failing AND I have specified OpenDNS' dns servers in the PRIMARY and SECONDARY DNS server fields (208.67.222.222 and 208.67.222.22).

Let me try disabling and re-enabling the ENABLE DNS RELAY setting to see if it has any effect.

Do you think there is any chance manually configuring the DNS primary and secondary instead of letting the router pick up the dns server from my isp is throwing this webfilter for a loop?

--With kind regards --
Logged

tcr49

  • Level 1 Member
  • *
  • Posts: 10
Re: Webfilter fails after updating to 1.35NA
« Reply #18 on: January 22, 2011, 07:08:38 PM »

Still no workie. Regardless of whether enable dns relay is enabled or not, same result, webfilters don't work w/1.35NA.

Here is something interesting. I read that securespot was REMOVED from v1.35NA firmware. If this is true, then "why" do I find this in my v1.35NA DIR-655 rev A4 router log:

[INFO]   Sat Jan 22 21:01:21 2011   Initiating securespot services.
[INFO]   Sat Jan 22 21:01:21 2011   Allocating securespot services.


As they say, WTH?

Can anyone else confirm that a DIR-655 A4 w/1.35NA firmware has these log entries show up during a reboot of the router?
Logged

tcr49

  • Level 1 Member
  • *
  • Posts: 10
Re: Webfilter fails after updating to 1.35NA
« Reply #19 on: January 22, 2011, 09:13:49 PM »

FIXED IT!

I reset the DIR-655 back to factory settings. Then re-flashed firmware 1.35NA. Then DID NOT restore my settings backup from when the router was running firmware v1.21. Then re-created all the config from scratch, including adding in the webfilters.

After this, the webfilter feature works fine again!

D-Link support: You may want to make note and add to your questions posed to customers experiencing this issue whether they took a backup of the settings and restored them after the firmware update. Since the manual If they did, and they are experiencing the issue where the webfilter does not work, you may be able to avoid an RMA by simply having them reset back to factory settings then re-flashing the latest firmware.
Logged

davevt31

  • Level 9 Member
  • ****
  • Posts: 1601
Re: Webfilter fails after updating to 1.35NA
« Reply #20 on: January 22, 2011, 10:56:13 PM »

The DLink folks haven't been around here much lately.
Logged

mickeyfinn

  • Level 1 Member
  • *
  • Posts: 12
Re: Webfilter fails after updating to 1.35NA
« Reply #21 on: January 28, 2011, 05:57:16 AM »

Just FYI, the consensus on these forums seems to be that restoring setting between two different iterations of the firmware is not recommended, and usually causes major problems (i.e. 1.3x to 1.3x fine, 1.2x to 1.2x fine, 1.2x to 1.3x not recommended).
Logged
Pages: 1 [2]