Talk:Access Restrictions
From DD-WRT Wiki
Revision as of 13:21, 5 December 2005 (edit) 81.173.254.249 (Talk) ← Previous diff |
Revision as of 13:25, 5 December 2005 (edit) (undo) 81.173.254.249 (Talk) Next diff → |
||
Line 8: | Line 8: | ||
But I don't know what "P2P" is for. | But I don't know what "P2P" is for. | ||
I also don't know, whether or how one can create own L7 filters. | 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. | ||
Thanks, | Thanks, | ||
Jack Hambabo, Dec. 5, 2005 | Jack Hambabo, Dec. 5, 2005 |
Revision as of 13:25, 5 December 2005
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.
Thanks,
Jack Hambabo, Dec. 5, 2005