Changes

no edit summary
Line 1: Line 1:  
{{Template: Networking_rutos_manual_fw_disclosure
 
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.07.00
+
| fw_version = {{{series}}}{{#ifeq:{{{name}}}|RUT241|M|}}_R_00.07.01
 
| series    = {{{series}}}
 
| series    = {{{series}}}
 
}}
 
}}
Line 28: Line 28:  
The <b>Groups</b> section lists available user groups of which there are three:
 
The <b>Groups</b> section lists available user groups of which there are three:
   −
[[File:Networking_rutos_users_groups.png|border|class=tlt-border]]
+
[[File:Networking_rutos_users_groups_v1.png|border|class=tlt-border]]
 
----
 
----
 
<ul>
 
<ul>
Line 73: Line 73:  
A group's parameters can be set in its <b>Group Settings</b> page. To access the Groups Settings page, click the 'Edit' button next to the group's name. Below is an example of the Group Settings section:
 
A group's parameters can be set in its <b>Group Settings</b> page. To access the Groups Settings page, click the 'Edit' button next to the group's name. Below is an example of the Group Settings section:
   −
[[File:Networking_rutos_users_groups_group_settings.png|border|class=tlt-border]]
+
[[File:Networking_rutos_users_groups_group_settings_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 83: Line 83:  
     <tr>
 
     <tr>
 
       <td>Write action</td>
 
       <td>Write action</td>
       <td>Allow | Deny; default: <b>Deny</b></td>
+
       <td>Allow | Deny; default: <b>Allow</b></td>
 
       <td>Specifies whether to allow or deny write actions for users in the group. Write actions consist of changing configurations and performing certain actions (such as clicking buttons).<br>This field directly correlates with the "Write access" field below it, because the selected write action will apply to pages specified in that field.</td>
 
       <td>Specifies whether to allow or deny write actions for users in the group. Write actions consist of changing configurations and performing certain actions (such as clicking buttons).<br>This field directly correlates with the "Write access" field below it, because the selected write action will apply to pages specified in that field.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Write access</td>
 
       <td>Write access</td>
       <td>path(s) to page(s); default: <b>*</b></td>
+
       <td>path(s) to page(s); default: <b>
 +
            <ul>
 +
                <li><b>system/multiusers/change_password</b></li>
 +
            </ul>
 +
        </b></td>
 
       <td>Path(s) to the page(s) to which the selected "Write action" will be applied. Click the plus symbol to add multiple entries.</td>
 
       <td>Path(s) to the page(s) to which the selected "Write action" will be applied. Click the plus symbol to add multiple entries.</td>
 
     </tr>
 
     </tr>
Line 100: Line 104:  
         <td>path(s) to page(s); default: <b>
 
         <td>path(s) to page(s); default: <b>
 
             <ul>
 
             <ul>
                 <li><b>admin/services/mobile_utilities/sms/send</b></li>
+
                 <li><b>services/mobile_utilities/sms/send</b></li>
                 <li><b>admin/system/multiusers/*</b></li>
+
                 <li><b>services/packages</b></li>
                 <li><b>admin/system/flashops/*</b></li>
+
                <li><b>system/multiusers/</b></li>
                 <li><b>admin/system/backup</b></li>
+
                 <li><b>system/flashops/</b></li>
                 <li><b>admin/system/admin/access_control</b></li>
+
                 <li><b>system/backup</b></li>
                 <li><b>admin/services/cli</b></li>
+
                 <li><b>system/admin/access_control</b></li>
                 <li><b>admin/system/uscripts</b></li>
+
                 <li><b>system/cli</b></li>
                 <li><b>admin/services/packages/upload</b></li>
+
                 <li><b>system/uscripts</b></li>
                 <li><b>admin/network/*</b></li>
+
                 <li><b>system/wizard</b></li>
                 {{#ifeq:{{{wifi}}}|1|<li><b>admin/services/hotspot/general/userscripts</b></li>}}
+
                <li><b>services/packages/upload</b></li>
 +
                 <li><b>network/</b></li>
 +
                 {{#ifeq:{{{wifi}}}|1|<li><b>services/hotspot/general/userscripts</b></li>}}
 
             </ul>
 
             </ul>
 
         </td>
 
         </td>
Line 120: Line 126:  
The easiest way to master the syntax is to navigate to page that you want to generate a path for and the copy the path from the URL of that page.
 
The easiest way to master the syntax is to navigate to page that you want to generate a path for and the copy the path from the URL of that page.
   −
For example, to specify the path to the Services VPN page, navigate to the page, copy the page's URL address <b>starting from the word "admin"</b> and paste it into one of the access fields:
+
For example, to specify the path to the Network Mobile page, navigate to the page, copy the page's URL address <b>starting from the symbol "#"</b> and paste it into one of the access fields:
   −
[[File:Networking_rutos_users_groups_example_url_bar.png]]
+
[[File:Networking_rutos_users_groups_example_url_bar_v1.png]]
 
----
 
----
 
However, the VPN window contains links to many different types of VPN pages. If you want to specify only one of them, you can do it as well. For example, to to specify the path to the IPsec page, <b>add "/ipsec" to the path string</b>:
 
However, the VPN window contains links to many different types of VPN pages. If you want to specify only one of them, you can do it as well. For example, to to specify the path to the IPsec page, <b>add "/ipsec" to the path string</b>:
   −
  admin/services/vpn<b>/ipsec</b>
+
  services/vpn<b>/ipsec</b>
 
----
 
----
 
An <b>asterisk (*)</b> in the path string means that the every page from that point on is included in that path. For example, to generate a path that includes pages in the Services menu tab:
 
An <b>asterisk (*)</b> in the path string means that the every page from that point on is included in that path. For example, to generate a path that includes pages in the Services menu tab:
   −
  admin/services/<b>*</b>
+
  services/<b>*</b>
    
Or to simply include everything in the entire WebUI (<b>if this path is combined with <i>Read action: Deny</i>, users from that group will not be able to login to the WebUI</b>):
 
Or to simply include everything in the entire WebUI (<b>if this path is combined with <i>Read action: Deny</i>, users from that group will not be able to login to the WebUI</b>):

Navigation menu