Print

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

[Desapointed]

Hello

I just bought a Dir-636L for 2 reasons:
1) I need to set some access control to limit the internet time for the kids
2) I liked the idea of the USB storage

None of these feature work properly.
Let's start with the access control to match the topic.

I want to block all access to the internet for the kids computer and other ipods during the night.
I created a schedule from 22:00 to midnight and another from midnight to 7:00.
In access control I just follow the instructions and created a policy where I listed the kids devices and block all access during these 2 schedules.
Well, it does not work... the internet for these devices is still working after 22:00...
I checked that the time is right and it is.

The only access control I managed to get is "always".... which I don't want.

I installed the latest software: 1.04, still does not work.

It's a bit sad that a company making router for so many year cannot make an interface more "familly guy" friendly and a router that work. It's just so bad and the instruction are just so unhelpful.

I even thought that I was doing the contrary and I had to schedule when I don't want the "block all access" so I created other schedules that are the opposite: from 7:00 to 22:00 but it does not stop the internet either.
And of course I enable the policy.

Can anybody help me not throwing this router in the garbage where it belongs.
That's my third day trying to make this work.

The good news is that I kept the package so I can return that thing.

Thanks
 

[FurryNutz]

I set the 10pm-12am rule up for my phone and another schedule rule for 12am-7am for my Laptop. I used 2 different schedules.
I then went to Access Control and used the name of the 1st scheduled rule for the policy which was listed. I then input the IP address for the phone and set to Block ALL and saved the setting. I did this for the 2nd schedule policy rule for laptop.

Once both policy's were in place, I saved settings and rebooted. I checked the current access on each device and still have access. I presume that 10pm I should loose access on the phone and 12am I should loose access on the LT and regain access on the phone at 12am.

I'll check this tonite and see what happens.

[FurryNutz]

Any status on this? 

[network1027]

Hi  

I've got the DIR-626L. It's not the same firmware it seems, but should be close.
There is indeed a bug, and a solution.
The bug is in the SCHEDULES engine.
The bug : the schedules seems to use THE GMT TIME ( sometimes +12h).

1 solution :

In Schedules, use the GMT time, not your local time. If it is still failing, add 12 hours to your timings.

I mean : Do your daylight saving time setup in the TIME submenu, if needed.
Then, for the Schedules timer, do it MINUS the GMT difference.

Ex : You're GMT+1 and want to block traffic from 22:00 to midnight :
22h/00h   ---)    22-1/00-1    --)    21h/23h

if it doesn't work, add 12h :

21:00-23:00    ---)   9:00-11:00

This is confusing, but should work OK.


Network1027

Technical details for the community, if some other people want to try :

Real Local Time       GMT Setting               Daylight Saving                   Working timer

15h-16h                  +1                                ( on )                              2h-3h
18h-19h                  +4                                ( on )                              14h-15h
11h-12h                  -3                                ( on )                               2h-3h

14h-15h                  +1                                 off                                  14h-15h
14h-15h                  +0                                ( on )                               14h-15h


Maybe someother people can try this, to confirm a bug, or comment the conclusions ?

Network1027

[FurryNutz]

Please us know your results. I did a quick test of 6pm-6:30Pm for one device and 6:30pm-6:45pm for a different device all set up to block and the actual time frame was 6:20-6:25 when I started all this. Block ALL was used and both devices were still able to see and use the internet during the time frames set. I need to go back and verify set up however seemed the configuration was good. I've got D-Link looking at this as well.

The 836L thru 626L models have the similar code base.

[network1027]

Please us know your results. I did a quick test of 6pm-6:30Pm for one device and 6:30pm-6:45pm for a different device all set up to block and the actual time frame was 6:20-6:25 when I started all this. Block ALL was used and both devices were still able to see and use the internet during the time frames set. I need to go back and verify set up however seemed the configuration was good. I've got D-Link looking at this as well.

The 836L thru 626L models have the similar code base.

Hi 

I rechecked, the problem is definitively in the schedule software.
I'm not a native english speaker, so maybe I don't explain clearly enough :

I've redone 12 different tests this morning, and my theory works 100%. I managed to block web
access whenever I wanted too. The formula :

Use [GMT time]+[your local daylight saving]
or
[GMT time]+[your local daylight saving]+12h

I don't manage to find a predictable pattern, about this 12h skew. So it is a try and error to find the working formula.

I've done tests either using the Access Control submenu, or using the IPv6 Firewall. Same problem.

This being said, this is very ennoying, as the schedule engine drives both the Access Control and the IPv6 firewall rules. ( and the IPv4 firewall too I guess ). They really need to fix this 

[FurryNutz]

FYI, D-Link has reviewed this and has found the problem. Please be patient while they get it fixed and released into the next FW update.

Thank you.

[Desapointed]

Hello FurryNutz and network1027

I set the time to GMT and did all my schedules according to this time and it seems to work.
I haven't got the need of the +12h.
Thanks for your help.

We'll see if this works as expected on next release...

[FurryNutz]

Thanks for posting and sharing your info. Please be patient while we wait for the fix.

Keep us posted.