D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: MoonRock on January 19, 2011, 07:08:57 PM
-
I've been using the web filter with no problem with my A3/1.33NA router until I upgraded to 1.35 last week. After the upgrade, i did a hard reset and re-entered the websites manually from scratch to the DENY list. I didn't even reuse the saved config file. And now the router no longer blocks any of the websites in the webfilter page even when i selected the ALLOW option. Please help.
-
You have to set up an Access Control Policy to use the webfilter you set up, and that can also include a schedule unless you use the 24hr/all-day choice....
-
I have. As i said previously, I've been using this feature with no problem until i updated to 1.35NA last week.
-
If you made and activated at least one valid policy like was suggested about the only thing that could be the problem is the format you entered the "websites" to be filtered in.
Do NOT enter URL's that you want to block. Only the key words, for instance:
Google-analytics
Goggle
redirect
free
bargain
adult
click
advertise
spy
promotion
tracker
traffic
adserve
-
Thanks. I will give it a try tonight. But that was not how i entered the website names prior to 1.35. I've always used the full url names minus the "http://" in the past and that worked.
In 1.31 (or 1.33?) you do have to uncheck the securepost option in order for the filter to work properly. I updated to 1.35 (skipping 1.34) thinking removing only the SecurePost by dlink wouldn't break what was working before.
-
I tried entering just the keywords and that didn't help either. Is there anyone here with webfilter working with the latest 1.35 firmware?
-
I'm experiencing the same exact symptom.
The website filter was working at the stock firmware on my A4 hardware rev of DIR-655; I upgraded to 1.35NA firmware and after the firmware update I had restored my settings which I backed up prior to the firmware update.
I'm discussing w/dlink tech support now. Will post back any update.
-
After some troubleshooting; no love. Only option given was to process an RMA on the device.
-
Webfilter works just fine on 1.35NA here. You must have had a profound failure somewhere.
Only other possibility that I can think of is that your browser is using a proxy that is bypassing the filter. That is possible, but rare. Clear your DNS cache and shut down your router, computer and modem for a while and bring them up forcing them to grab new settings.
I assume you eliminated a corrupt firmware image by using a fresh download and reflashing.
-
No proxy here, just cable modem --> DIR-655. The flash update to 1.35NA went through flawlessly the first time around but I'm willing to give it another go.
The only thing I can think is that it didn't like restoring the backup of the settings from when the router was at v1.21 that I restored after updating to 1.35NA (although all the other settings seem to be working fine, port forwards, etc).
The other thing I will mention is that the "Apply Advanced Port Filters" option works fine but the "Apply Web Filter" has no effect.
-
FYI-my "rules" specify by IP, since my IP's never change. For the sake that my filter is working, as a diagnostic tool, set yours by IP also.
Check your software firewall and browser advanced settings to make sure there is no baloney proxy route set somewhere.
-
I also specify mine by IP since all of them are reserved by the router. Just wondering if you have the Relay DNS enabled? Mine is not.
-
I'll be in all day. Got the Flu.
I do keep my advanced DNS checked. There are times when I uncheck it, and my filter still works fine. I have found that my best performance is with DNS checked and the IP of the router specified as the "gateway." Works without that also though.
Changing these settings has not tricked the filter at all for me.
-
Did you mean the "Enable DNS Relay" under Network Setting or the "Advanced DNS Service" under Internet Configuration? Both of these are under the Setup tab. I have both unchecked for now.
-
I have both checked. I get my best results that way.
-
Enable DNS Realy needs to ON for the webfilters to work.
-
Yep. After enabling the DNS Relay everything works now. Thanks.
-
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 --
-
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?
-
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.
-
The DLink folks haven't been around here much lately.
-
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).