Talk:Access Restrictions

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 14:05, 9 July 2006 (edit) (Talk)

← Previous diff
Revision as of 19:27, 11 July 2006 (edit) (undo)
Atzekalle (Talk | contribs)
m (Reverted)
Next diff →
Line 28: Line 28:
Thanks, Thanks,
Jack Hambabo, Dec. 6, 2005 Jack Hambabo, Dec. 6, 2005

Revision as of 19:27, 11 July 2006

I just wanted to mention the bugs #48 and #355 (today is Dec. 5, 2005) but they'll probably be solved soon. (logging doesn't work when L7-blocking was activated)

And I think an explanation of the "P2P" "L7" "UDP" "TCP" "UDP+TCP" differences would be great. As I understand it, UDP and TCP blocks everything. L7 is a layer 7 - i.e. application layer-blocker that analyzes the packages to see whether it's for example filesharing stuff. But I don't know what "P2P" is for. I also don't know, whether or how one can create own L7 filters.

And I find this "Policies are processed in order. This is an important item to remember when creating Deny policies." sentence confusing. I woudl have expected that "processed in order" would mean, that a rule in the 2nd slot can "override" a rule in the 1st slot.

This help seems not to refer to the current version. In the current version the "profile name" is called "policy name" and there is no reference to the "Policy type" which can be either "Internet Access" or "Inbound Traffic"

It seems to me that the most important thing about the access restriction is the filtering. Who would not allow any internet while specific times? I think that therefore it would be apropriate to mention, that one uses a "Allow everything, everywhen"-policy and adds restrictions for that. And I'm unsure whether one then has to add a deny-policy at the end. Could someone tell me whether this is a must?

Thanks, Jack Hambabo, Dec. 5, 2005

Once a again I find this "high" and "low" confusing, as I first thought that "1" would be high, as it is high on the list.

And I wanted to mention the bugtracker item 388, as it states that in version 16th Nov and 3rd Dec access restrictions are broken. And even more if it isn't the configuration is so complicated that at least two didn't manage to set it up. So especially in this case a good documentation would be needed.

Thanks, Jack Hambabo, Dec. 6, 2005