Site Tools


access_restrictions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
access_restrictions [2023/07/02 16:23] – [Scripting Access Restrictions] -formatting hogwildaccess_restrictions [2023/07/03 18:31] – oops, didn't get it all the first time techie007
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:
Line 45: Line 47:
   * 16 = Thursday   * 16 = Thursday
   * 32 = Friday   * 32 = Friday
-  * 64 = Sunday+  * 64 = Saturday
  
 For multiple days, simply add together the corresponding numbers for each day. For multiple days, simply add together the corresponding numbers for each day.
Line 117: Line 119:
  
  \\  \\
- 
  
 ===== Credits ===== ===== Credits =====
  
 [[http://web.archive.org/web/20160321090715/http://infinilogix.com/wordpress/network-programming/routers/how-to-control-access-restriction-rules-in-tomato-by-a-shell-script|Credit: Justin from "infinilogix.com" - original page which is now only accessible via archive.org]] [[http://web.archive.org/web/20160321090715/http://infinilogix.com/wordpress/network-programming/routers/how-to-control-access-restriction-rules-in-tomato-by-a-shell-script|Credit: Justin from "infinilogix.com" - original page which is now only accessible via archive.org]]
 +
 +
access_restrictions.txt · Last modified: 2023/10/26 17:20 by hogwild