Changes

→‎DHCP Server: General Setup: updated DHCP server information and pictures.
Line 276: Line 276:  
=====Mode: Passthrough=====
 
=====Mode: Passthrough=====
 
----
 
----
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_mobile_passthrough_mode_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_mobile_passthrough_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 294: Line 294:  
             </ul>
 
             </ul>
 
         </td>
 
         </td>
 +
    <tr>
 +
    <td>Subnet selection</td>
 +
        <td>Auto {{!}} P2P; default: <b>Auto</b></td>
 +
        <td>Subnet selection method.</td>
 +
    </tr>
 
     <tr>
 
     <tr>
 
     <td>PDP Type</td>
 
     <td>PDP Type</td>
Line 360: Line 365:  
=====Mode: Bridge=====
 
=====Mode: Bridge=====
 
----
 
----
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_mobile_bridge_mode.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_mobile_bridge_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 370: Line 375:  
     <tr>
 
     <tr>
 
       <td>Mode</td>
 
       <td>Mode</td>
       <td>NAT <nowiki>|</nowiki> Bridge <nowiki>|</nowiki> Passthrough; default: <b>NAT</b></td>
+
       <td>NAT {{!}} Bridge {{!}} Passthrough; default: <b>NAT</b></td>
 
       <td>Mobile connection operating mode.
 
       <td>Mobile connection operating mode.
 
             <ul>
 
             <ul>
Line 378: Line 383:  
             </ul>
 
             </ul>
 
         </td>
 
         </td>
 +
    <tr>
 +
    <td>Subnet selection</td>
 +
        <td>Auto {{!}} P2P; default: <b>Auto</b></td>
 +
        <td>Subnet selection method.</td>
 +
    </tr>
 
     <tr>
 
     <tr>
 
     <td>PDP Type</td>
 
     <td>PDP Type</td>
 
         <td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: <b>IPv4</b></td>
 
         <td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: <b>IPv4</b></td>
 
         <td>Specifies what of address will be requested from the operator.</td>
 
         <td>Specifies what of address will be requested from the operator.</td>
    </tr>
   
     </tr>{{#ifeq: {{{dualsim}}} | 1 | {{#ifeq: {{{dualmodem}}} | 1 ||
 
     </tr>{{#ifeq: {{{dualsim}}} | 1 | {{#ifeq: {{{dualmodem}}} | 1 ||
 
     <tr>
 
     <tr>
Line 738: Line 747:  
<b>Advanced Settings</b> information for <i>Mobile</i> protocol is provided in the table below.
 
<b>Advanced Settings</b> information for <i>Mobile</i> protocol is provided in the table below.
   −
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v4.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v5.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 760: Line 769:  
         <td>ip4; default: <b>none</b></td>
 
         <td>ip4; default: <b>none</b></td>
 
         <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
 
         <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
     </tr>{{#ifeq:{{{dualsim}}}|1|
+
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Use gateway metric</td>
 
         <td>Use gateway metric</td>
 
         <td>integer; default: <b>none</b></td>
 
         <td>integer; default: <b>none</b></td>
 
         <td>A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).</td>
 
         <td>A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).</td>
     </tr>|}}
+
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Override MTU</td>
 
         <td>Override MTU</td>
Line 777: Line 786:  
     </tr>
 
     </tr>
 
</table>|}}
 
</table>|}}
 +
 
===Physical Settings===
 
===Physical Settings===
 
----
 
----
Line 849: Line 859:  
The <b>General Setup</b> section is used to set up the main operating parameters of the DHCP server.
 
The <b>General Setup</b> section is used to set up the main operating parameters of the DHCP server.
   −
[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_general_setup_lan_{{{lan}}}.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_general_setup_lan_{{{lan}}}_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 863: Line 873:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Start</td>
+
         <td>Start IP</td>
         <td>integer [1..255]; default: <b>100</b></td>
+
         <td>ip4; default: <b>{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.100|#default=192.168.1.100}}</b></td>
         <td>The starting IP address value. e.g., if your device’s LAN IP is 192.168.1.1 and your subnet mask is 255.255.255.0 that means that in your network a valid IP address has to be in the range of [192.168.1.0..192.168.1.254] (192.168.1.255 is a special unavailable address). If the Start value is set to 100 then the DHCP server will only lease out addresses starting from 192.168.1.<b>100</b>.</td>
+
         <td>The starting IP address of the DHCP server IP address range. E.g., if your device’s LAN IP is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.1|#default=192.168.1.1}} and your subnet mask is 255.255.255.0 that means that in your network a valid IP address has to be in the range of [{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.0|#default=192.168.1.0}}..{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.254|#default=192.168.1.254}}] ({{#switch:{{{series}}}|TRB1|TRB5=192.168.2.255|#default=192.168.1.255}} is a special unavailable address). If the subnet of your LAN IP address changes, this value needs to be changed accordingly.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Limit</td>
+
         <td>End IP</td>
         <td>integer [1..255]; default: <b>150</b></td>
+
         <td>ip4; default: <b>{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.249|#default=192.168.1.249}}</b></td>
         <td>How many addresses the DHCP server can lease out. Continuing from the example above: if the start address is 192.168.1.100 and the server can lease out 150 addresses, available addresses will be from 192.168.1.<b>100</b> to 192.168.1.<b>249</b> (<i>100 + 150 – 1 = 249</i>; this is because the first address is inclusive).</td>
+
         <td>The ending IP address of the DHCP server IP address range. Continuing from the example above: if the start address is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.<b>100</b>|#default=192.168.1.<b>100</b>}} and the end address is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.<b>249</b>|#default=192.168.1.<b>249</b>}}, available addresses will be distributed from that range. If the subnet of your LAN IP address changes, this value needs to be changed accordingly.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Lease time</td>
 
         <td>Lease time</td>
         <td>integer [1..999999]; default: <b>12</b></br>integer [2..999999]<span class="asterisk">*</span></br>integer [120..999999]<span class="asterisk">**</span></td>
+
         <td>integer [1..999999]; default: <b>12</b><br>integer [2..999999]<span class="asterisk">*</span><br>integer [120..999999]<span class="asterisk">**</span></td>
         <td>A DHCP lease will expire after the amount of time specified in this field and the device that was using the lease will have to request a new one. However, if the device stays connected, its lease will be renewed after half of the specified amount of time passes (e.g., if lease time is 12 hours, then every 6 hours the device will ask the DHCP server to renew its lease).<br>The minimal amount of time that can be specified is 2 minutes.</br><span class="asterisk">*</span>If selected Units is Minutes.</br><span class="asterisk">**</span>If selected Units is seconds.</td>
+
         <td>A DHCP lease will expire after the amount of time specified in this field and the device that was using the lease will have to request a new one. However, if the device stays connected, its lease will be renewed after half of the specified amount of time passes (e.g., if lease time is 12 hours, then every 6 hours the device will ask the DHCP server to renew its lease).<br>The minimal amount of time that can be specified is 2 minutes.<br><span class="asterisk">*</span>If selected Units is Minutes.<br><span class="asterisk">**</span>If selected Units is seconds.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 1,083: Line 1,093:  
<i>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to Mobile</b>.</i>
 
<i>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to Mobile</b>.</i>
   −
[[File:Networking_rutos_manual_interfaces_interface_configuration_mobile_mobile_data_limit.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_mobile_mobile_data_limit_v2.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 1,124: Line 1,134:  
         <td>phone number; default: <b>none</b></td>
 
         <td>phone number; default: <b>none</b></td>
 
         <td>Recipient's phone numbers.</td>
 
         <td>Recipient's phone numbers.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Data limit clear due</td>
 +
        <td><b>none</b></td>
 +
        <td>Display the date of the next automatic data limit clear.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>

Navigation menu