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
access_restrictions [2023/07/02 01:52] – Removed extraneous blank lines techie007access_restrictions [2023/10/26 17:20] (current) – [Scripting Access Restrictions] -format 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>+ 
 + \\ 
 + 
 +<code -> 
 +nvram get rrule0 
 +</code>
  
 \\ \\
  
 The returned string might look something like this: The returned string might look something like this:
-<code ->1|540|1140|62|||block-site.com$|0|New Rule 1</code>+ 
 + \\ 
 + 
 +<code -> 
 +1|540|1140|62|||block-site.com$|0|New Rule 1 
 +</code>
  
 \\ \\
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.+ \\
  
-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 //Everyday// option, the value would have been 127.+For multiple days, simply add together the corresponding numbers for each day. 
 + 
 +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 //Everyday// option, the value would have been 127.
  
 **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 68:
   * A "2" will block Flash.   * A "2" will block Flash.
   * A "4" will block Java.   * A "4" will block Java.
 +
 + \\
  
 **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 120:
 If you have JFFS enabled in FreshTomato, you can copy the script under the jffs directory and schedule it to run as a cron job, if you wish. If you have JFFS enabled in FreshTomato, you can copy the script under the jffs directory and schedule it to run as a cron job, if you wish.
  
 + \\
 +
 + \\
  
  
Line 108: Line 128:
  
 [[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.1688259126.txt.gz · Last modified: 2023/07/02 01:52 by techie007