User Tools
access_restrictions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| access_restrictions [2023/07/02 01:52] – Removed extraneous blank lines techie007 | access_restrictions [2023/10/26 17:20] – [Scripting Access Restrictions] -formatting hogwild | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Access Restriction rules are coded as strings separated by pipe ( | ) symbols. These are stored in NVRAM as variables named //rrule0//, //rrule1//, //rrule2// and so on. | Access Restriction rules are coded as strings separated by pipe ( | ) symbols. These are stored in NVRAM as variables named //rrule0//, //rrule1//, //rrule2// and so on. | ||
| + | |||
| + | \\ | ||
| To see what's in the first rule, we can issue the following command at a FreshTomato shell prompt: | To see what's in the first rule, we can issue the following command at a FreshTomato shell prompt: | ||
| - | <code ->nvram get rrule0</ | + | |
| + | \\ | ||
| + | |||
| + | <code -> | ||
| + | nvram get rrule0 | ||
| + | </ | ||
| \\ | \\ | ||
| The returned string might look something like this: | The returned string might look something like this: | ||
| - | <code -> | + | |
| + | \\ | ||
| + | |||
| + | <code -> | ||
| + | 1|540|1140|62|||block-site.com$|0|New Rule 1 | ||
| + | </ | ||
| \\ | \\ | ||
| Line 28: | Line 40: | ||
| It is coded in binary: | It is coded in binary: | ||
| + | |||
| * 1 = Sunday | * 1 = Sunday | ||
| * 2 = Monday | * 2 = Monday | ||
| Line 34: | Line 47: | ||
| * 16 = Thursday | * 16 = Thursday | ||
| * 32 = Friday | * 32 = Friday | ||
| - | * 64 = Sunday | + | * 64 = Saturday |
| - | For multiple days, add the corresponding numbers for each day. | + | For multiple days, simply |
| - | In the above example, the fourth field is 62, which is equal to 2 + 4 + 8 + 16 + 32 . This means the rule should be active on Mon, Tue, Wed., Thu., and Fri. That is, only on weekdays. If you had checked the // | + | In the above example, the fourth field is 62, which is equal to 2 + 4 + 8 + 16 + 32 . This means the rule should be active on Mon, Tue, Wed, Thu, and Fri. That is, only on weekdays. If you had checked the // |
| **Field 5:** shows the IP or MAC Address range on your network for which the rule should be applied. | **Field 5:** shows the IP or MAC Address range on your network for which the rule should be applied. | ||
| Line 53: | Line 66: | ||
| * A " | * A " | ||
| * A " | * A " | ||
| + | |||
| + | \\ | ||
| **Field 9:** stores the name that you gave to the rule being edited. | **Field 9:** stores the name that you gave to the rule being edited. | ||
| Line 103: | Line 118: | ||
| If you have JFFS enabled in FreshTomato, | If you have JFFS enabled in FreshTomato, | ||
| + | \\ | ||
| + | |||
| + | \\ | ||
| Line 108: | Line 126: | ||
| [[http:// | [[http:// | ||
| + | |||
| + | |||
access_restrictions.txt · Last modified: 2023/10/26 17:20 by hogwild
Page Tools
