Difference between revisions of "Template:Networking rutos manual interfaces"
Gytispieze (talk | contribs) m (Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}") |
|||
(50 intermediate revisions by 11 users not shown) | |||
Line 1: | Line 1: | ||
− | {{Template: | + | {{Template:Networking_rutos_manual_fw_disclosure |
− | | | + | | fw_version = {{{series}}}_R_00.02.05 |
− | + | | series = {{{series}}} | |
− | |||
− | |||
− | |||
− | |||
}} | }} | ||
Line 22: | Line 18: | ||
The <b>Network Interfaces</b> section displays interfaces currently existing on this device. | The <b>Network Interfaces</b> section displays interfaces currently existing on this device. | ||
− | + | [[File:Networking_rutos_manual_interfaces_network_interfaces_lan_{{{lan}}}_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}.png|border|class=tlt-border]] | |
− | [[File:Networking_rutos_manual_interfaces_network_interfaces_lan_{{{lan}}}_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired} | ||
− | |||
==Add Interface== | ==Add Interface== | ||
Line 50: | Line 44: | ||
<th width="14%" style="text-align: center;">DHCPv6</th> | <th width="14%" style="text-align: center;">DHCPv6</th> | ||
<th width="14%" style="text-align: center;">PPPoE</th> | <th width="14%" style="text-align: center;">PPPoE</th> | ||
− | + | <th width="14%" style="text-align: center;">Mobile</th> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 58: | Line 52: | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
− | + | <td></td> | |
</tr> | </tr> | ||
{{#ifeq: {{{wired}}} | 1 | {{#ifeq: {{{wired}}} | 1 | ||
Line 67: | Line 61: | ||
<td>[[File:Blue_check_mark.png|center|15px]]</td> | <td>[[File:Blue_check_mark.png|center|15px]]</td> | ||
<td>[[File:Blue_check_mark.png|center|15px]]</td> | <td>[[File:Blue_check_mark.png|center|15px]]</td> | ||
− | + | <td></td> | |
</tr> | </tr> | ||
| | | | ||
Line 86: | Line 80: | ||
To begin configuring an interface, click the 'Edit' button on the right side of the interface: | To begin configuring an interface, click the 'Edit' button on the right side of the interface: | ||
− | [[File:Networking_rutos_manual_interfaces_network_interfaces_edit_button_lan_{{{lan} | + | [[File:Networking_rutos_manual_interfaces_network_interfaces_edit_button_lan_{{{lan}}}.png]] |
===General Setup=== | ===General Setup=== | ||
Line 106: | Line 100: | ||
<tr> | <tr> | ||
<td>IPv4 address</td> | <td>IPv4 address</td> | ||
− | <td>ip4; default[for LAN]: <b> | + | <td>ip4; default[for LAN]: <b>192.168.1.1</b></td> |
<td>The IPv4 address interface of this interface. An IP address identifies a device on a network and allows it to communicate with other devices.</td> | <td>The IPv4 address interface of this interface. An IP address identifies a device on a network and allows it to communicate with other devices.</td> | ||
</tr> | </tr> | ||
Line 212: | Line 206: | ||
The <b>Mobile</b> protocol is used to set up an interface which can establish a mobile WAN connection. | The <b>Mobile</b> protocol is used to set up an interface which can establish a mobile WAN connection. | ||
− | |||
− | |||
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] | [[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] | ||
Line 228: | Line 220: | ||
<ul> | <ul> | ||
<li><b>NAT</b> - the mobile connection uses NAT (network address translation).</li> | <li><b>NAT</b> - the mobile connection uses NAT (network address translation).</li> | ||
− | <li><b>Bridge</b> - bridges the LTE data connection with LAN. The device assigns its WAN IP address to another device (first connected to LAN or specified with MAC address). Using Bridge mode will disable most of the device’s capabilities.</li> | + | <li><span style="color: red;"><b>Bridge</b></span> - bridges the LTE data connection with LAN. The device assigns its WAN IP address to another device (first connected to LAN or specified with MAC address). Using Bridge mode will disable most of the device’s capabilities.</li> |
− | <li><b>Passthrough</b> - in this mode the {{{name}}} shares its WAN IP to a single LAN device (first connected to LAN or specified with MAC address). The LAN device will get WAN IP of {{{name}}} instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.</li> | + | <li><span style="color: cornflowerblue;"><b>Passthrough</b></span> - in this mode the {{{name}}} shares its WAN IP to a single LAN device (first connected to LAN or specified with MAC address). The LAN device will get WAN IP of {{{name}}} instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.</li> |
</ul> | </ul> | ||
</td> | </td> | ||
+ | </tr>{{#ifeq: {{{dualsim}}} | 1 | | ||
<tr> | <tr> | ||
<td>PDP Type</td> | <td>PDP Type</td> | ||
Line 237: | Line 230: | ||
<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> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
<td>SIM</td> | <td>SIM</td> | ||
<td>SIM1 <nowiki>|</nowiki> SIM2; default: <b>SIM1</b></td> | <td>SIM1 <nowiki>|</nowiki> SIM2; default: <b>SIM1</b></td> | ||
<td>Selects which SIM slot will be used for this interface.</td> | <td>Selects which SIM slot will be used for this interface.</td> | ||
− | </tr> | + | </tr>|}}{{#ifeq: {{{dualmodem}}} | 1 | |
<tr> | <tr> | ||
<td>Modem</td> | <td>Modem</td> | ||
Line 432: | Line 267: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>MAC Address</td> | + | <td><span style="color: red;">Bridge</span> <nowiki>|</nowiki> <span style="color: cornflowerblue;">Passthrough</span>: MAC Address</td> |
<td>mac; default: <b>none</b></td> | <td>mac; default: <b>none</b></td> | ||
<td>Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge or Passthrough mode.<br><b>Note:</b> this field only becomes visible when using Bridge or Passthrough mode.</td> | <td>Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge or Passthrough mode.<br><b>Note:</b> this field only becomes visible when using Bridge or Passthrough mode.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|}} | |}} | ||
Line 462: | Line 282: | ||
<b>Advanced Settings</b> information for <b>Static</b> protocol is provided in the table below. | <b>Advanced Settings</b> information for <b>Static</b> protocol is provided in the table below. | ||
− | [[File: | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_static.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 469: | Line 289: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Bring up on boot</td> | ||
+ | <td>off | on; default: <b>on</b></td> | ||
+ | <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 479: | Line 304: | ||
<td>off | on; default: <b>on</b></td> | <td>off | on; default: <b>on</b></td> | ||
<td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td> | <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 493: | Line 313: | ||
<td>Override MTU</td> | <td>Override MTU</td> | ||
<td>integer [1..9200]; default: <b>none</b></td> | <td>integer [1..9200]; default: <b>none</b></td> | ||
− | <td>Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction. | + | <td>Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td> |
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Use gateway metric</td> |
− | <td>integer | + | <td>integer; default: <b>none</b></td> |
− | <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> | |
<td>IPv6 assignment length</td> | <td>IPv6 assignment length</td> | ||
− | <td> | + | <td><span style="color: red;">integer [0..64]</span> | Disabled; default: <b>Disabled</b></td> |
<td>Delegates a prefix of given length to the interface.</td> | <td>Delegates a prefix of given length to the interface.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td | + | <td>IPv6 address</td> |
<td>ip6; default: <b>none</b></td> | <td>ip6; default: <b>none</b></td> | ||
<td>The interface's IPv6 address. An IP address identifies a device on a network and allows it to communicate with other devices.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i></td> | <td>The interface's IPv6 address. An IP address identifies a device on a network and allows it to communicate with other devices.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td><span style="color: | + | <td><span style="color: red;">IPv6 gateway</span></td> |
<td>ip6; default: <b>none</b></td> | <td>ip6; default: <b>none</b></td> | ||
<td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td> | <td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td | + | <td>IPv6 routed prefix</td> |
<td>ip6; default: <b>none</b></td> | <td>ip6; default: <b>none</b></td> | ||
<td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td> | <td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>IPv6 assignment hint</td> | + | <td><span style="color: red;">IPv6 assignment hint</span></td> |
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
− | <td> | + | <td>The subprefix-ID that should be delegated as hexadecimal number.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 535: | Line 350: | ||
<td>When an IPv6 prefix (like 'a:b:c:d::') is received from a delegating server, use a suffix (like '::1') to form an IPv6 address ('a:b:c:d::1') for the interface. Leave empty to generate a random suffix.</td> | <td>When an IPv6 prefix (like 'a:b:c:d::') is received from a delegating server, use a suffix (like '::1') to form an IPv6 address ('a:b:c:d::1') for the interface. Leave empty to generate a random suffix.</td> | ||
</tr> | </tr> | ||
− | |||
</table> | </table> | ||
Line 542: | Line 356: | ||
<b>Advanced Settings</b> information for <i>DHCP</i> protocol is provided in the table below. | <b>Advanced Settings</b> information for <i>DHCP</i> protocol is provided in the table below. | ||
− | [[File: | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_dhcp.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 549: | Line 363: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Bring up on boot</td> | ||
+ | <td>off | on; default: <b>on</b></td> | ||
+ | <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 569: | Line 388: | ||
<td>off | on; default: <b>on</b></td> | <td>off | on; default: <b>on</b></td> | ||
<td>When checked, creates a default route for the interface.</td> | <td>When checked, creates a default route for the interface.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Use DNS servers advertised by peer</td> | ||
+ | <td><span style="color: red;">off</span> | on; default: <b>on</b></td> | ||
+ | <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td><span style="color: red;">Use custom DNS servers</span></td> | ||
+ | <td>off | on; default: <b>on</b></td> | ||
+ | <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 574: | Line 403: | ||
<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> | ||
Line 598: | Line 422: | ||
<td>Override MTU</td> | <td>Override MTU</td> | ||
<td>integer [1..9200]; default: <b>none</b></td> | <td>integer [1..9200]; default: <b>none</b></td> | ||
− | <td>Changes the interfaces allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction | + | <td>Changes the interfaces allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 615: | Line 430: | ||
<b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below. | <b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below. | ||
− | [[File: | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_dhcpv6.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 622: | Line 437: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Bring up on boot</td> | ||
+ | <td>off | on; default: <b>on</b></td> | ||
+ | <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 639: | Line 459: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>Use custom DNS servers</td> | + | <td>Use DNS servers advertised by peer</td> |
− | <td> | + | <td><span style="color: red;">off</span> | on; default: <b>on</b></td> |
− | <td>Specifies | + | <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td> |
+ | </tr> | ||
+ | <tr> | ||
+ | <td><span style="color: red;">Use custom DNS servers</span></td> | ||
+ | <td>off | on; default: <b>on</b></td> | ||
+ | <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 661: | Line 486: | ||
<td>Override MTU</td> | <td>Override MTU</td> | ||
<td>integer [1..9200]; default: <b>none</b></td> | <td>integer [1..9200]; default: <b>none</b></td> | ||
− | <td>Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction. | + | <td>Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td> |
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</table> | </table> | ||
Line 678: | Line 494: | ||
<b>Advanced Settings</b> information for <i>PPPoE</i> protocol is provided in the table below. | <b>Advanced Settings</b> information for <i>PPPoE</i> protocol is provided in the table below. | ||
− | [[File: | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_pppoe.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 685: | Line 501: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Bring up on boot</td> | ||
+ | <td>off | on; default: <b>on</b></td> | ||
+ | <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 712: | Line 533: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>Use | + | <td>Use DNS servers advertised by peer</td> |
− | <td> | + | <td><span style="color: red;">off</span> | on; default: <b>on</b></td> |
− | <td>Specifies | + | <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color: red;">Use custom DNS servers</span></td> |
− | <td> | + | <td>off | on; default: <b>on</b></td> |
− | <td> | + | <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td> |
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 750: | Line 566: | ||
<td>integer [1..1500]; default: <b>none</b></td> | <td>integer [1..1500]; default: <b>none</b></td> | ||
<td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet.</td> | <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 762: | Line 573: | ||
<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}}} | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 769: | Line 580: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Bring up on boot</td> | ||
+ | <td>off <nowiki>|</nowiki> on; default: <b>on</b></td> | ||
+ | <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 781: | Line 597: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>Use custom DNS servers</td> | + | <td>Use DNS servers advertised by peer</td> |
− | <td> | + | <td><span style="color: red;">off</span> <nowiki>|</nowiki> on; default: <b>on</b></td> |
− | <td>Specifies | + | <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td> |
+ | </tr> | ||
+ | <tr> | ||
+ | <td><span style="color: red;">Use custom DNS servers</span></td> | ||
+ | <td>off <nowiki>|</nowiki> on; default: <b>on</b></td> | ||
+ | <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 794: | Line 615: | ||
<td>integer [1..9200]; default: <b>none</b></td> | <td>integer [1..9200]; default: <b>none</b></td> | ||
<td>Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td> | <td>Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table>|}} | </table>|}} | ||
− | |||
===Physical Settings=== | ===Physical Settings=== | ||
---- | ---- | ||
The <b>Physical Settings</b> section is used to create associations with physical interfaces and bridge network interfaces. | The <b>Physical Settings</b> section is used to create associations with physical interfaces and bridge network interfaces. | ||
− | [[File: | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_physical_settings.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 816: | Line 631: | ||
<tr> | <tr> | ||
<td>Bridge interfaces</td> | <td>Bridge interfaces</td> | ||
− | <td>off | <span style="color: | + | <td>off | <span style="color: red;">on</span>; default: <b>off</b></td> |
<td>Bridges physical interfaces specified in this configuration.</td> | <td>Bridges physical interfaces specified in this configuration.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color: red;">Enable STP</span></td> |
− | |||
− | |||
− | |||
− | |||
− | |||
<td>off | on; default: <b>off</b></td> | <td>off | on; default: <b>off</b></td> | ||
− | <td> | + | <td>Turns the use of Spanning Tree Protocol (STP) for this interface on or off.<br><b>Note:</b> this field becomes visible when 'Bridge interfaces' is set to <i>on</i></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 868: | Line 678: | ||
[[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]] | [[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]] | ||
− | < | + | <u>In order to view the DHCP server configuration, the interface <b>protocol must be set to <i>Static</i></b></i>.</u> |
====DHCP Server: General Setup==== | ====DHCP Server: General Setup==== | ||
Line 874: | Line 684: | ||
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}}} | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_general_setup_lan_{{{lan}}}.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 888: | Line 698: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>Start | + | <td>Start</td> |
− | <td> | + | <td>integer [1..255]; default: <b>100</b></td> |
− | <td>The starting IP address | + | <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> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Limit</td> |
− | <td> | + | <td>integer [1..255]; default: <b>150</b></td> |
− | <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> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Lease time</td> | <td>Lease time</td> | ||
− | <td>integer [ | + | <td>integer [2..999999]m/h; default: <b>12h</b></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 | + | <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.</td> |
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 917: | Line 722: | ||
Refer to the table below for information on the <b>Advanced Settings</b> section. | Refer to the table below for information on the <b>Advanced Settings</b> section. | ||
− | [[File: | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_advanced_settings.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 944: | Line 749: | ||
<td>dhcp options; default: <b>none</b></td> | <td>dhcp options; default: <b>none</b></td> | ||
<td>Additional options to be added to the DHCP server. For example with '26,1470' or 'option:mtu, 1470' you can assign an MTU value per DHCP. You can find more information on DHCP Options [https://technet.microsoft.com/en-us/library/cc958941.aspx here].</td> | <td>Additional options to be added to the DHCP server. For example with '26,1470' or 'option:mtu, 1470' you can assign an MTU value per DHCP. You can find more information on DHCP Options [https://technet.microsoft.com/en-us/library/cc958941.aspx here].</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 1,005: | Line 805: | ||
<b>Static IP leases</b> are used to reserve specific IP addresses for specific devices by binding them to their MAC address. This is useful when you have a stationary device connected to your network that you need to reach frequently, e.g., printer, IP phone, etc. | <b>Static IP leases</b> are used to reserve specific IP addresses for specific devices by binding them to their MAC address. This is useful when you have a stationary device connected to your network that you need to reach frequently, e.g., printer, IP phone, etc. | ||
− | This section displays static IP leases currently existing on this device. | + | This section displays static IP leases currently existing on this device. <u>In order to view the Static Lease section, the interface <b>protocol must be set to <i>Static</i></b></i>.</u> |
− | |||
− | < | ||
---- | ---- | ||
The Static Lease list is empty by default. To add a new Static Lease look to the Add Lease section; enter a custom name for the lease and click the 'Add' button. | The Static Lease list is empty by default. To add a new Static Lease look to the Add Lease section; enter a custom name for the lease and click the 'Add' button. | ||
Line 1,043: | Line 841: | ||
---- | ---- | ||
The <b>Relay Configuration</b> section is used to relay and dynamically redirect incoming connections to a target host. Its main purpose is extending the wireless network. For example, when the device is in Wireless Station (client) mode, it can be used to bridge WAN and LAN interfaces to create a larger wireless network.<br>You can find a detailed usage example <b>[[Relayd|here]]</b>. | The <b>Relay Configuration</b> section is used to relay and dynamically redirect incoming connections to a target host. Its main purpose is extending the wireless network. For example, when the device is in Wireless Station (client) mode, it can be used to bridge WAN and LAN interfaces to create a larger wireless network.<br>You can find a detailed usage example <b>[[Relayd|here]]</b>. | ||
− | |||
− | |||
− | |||
− | |||
− | + | <u>In order to view the Relay Configuration section, the interface <b>protocol must be set to <i>Static</i></b></i>.</u> | |
− | |||
[[File:Networking_rutos_manual_interfaces_interface_configuration_relay_configuration.png|border|class=tlt-border]] | [[File:Networking_rutos_manual_interfaces_interface_configuration_relay_configuration.png|border|class=tlt-border]] | ||
Line 1,070: | Line 863: | ||
</tr> | </tr> | ||
</table>|}} | </table>|}} | ||
− | + | {{#ifeq: {{{mobile}}} | 1 | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
===Mobile Data Limit=== | ===Mobile Data Limit=== | ||
---- | ---- | ||
The <b>Mobile Data Limit</b> section provides you with the possibility to set data usage limits for your mobile network interfaces and data usage warnings via SMS message in order to protect yourself from unwanted data charges. | The <b>Mobile Data Limit</b> section provides you with the possibility to set data usage limits for your mobile network interfaces and data usage warnings via SMS message in order to protect yourself from unwanted data charges. | ||
− | < | + | <u>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to <i>Mobile</i></b></i>.</u> |
− | [[File: | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_mobile_mobile_data_limit.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 1,149: | Line 911: | ||
<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> | ||
</table> | </table> | ||
− | <font size="-1" | + | <font size="-1"><span class="asterisk">*</span>Your carrier's data usage accounting may differ. Teltonika is not liable should any accounting discrepancies occur.</font>|}} |
[[Category:{{{name}}} Network section]] | [[Category:{{{name}}} Network section]] |
Revision as of 07:23, 16 September 2020
Template:Networking rutos manual fw disclosure
Summary
The Interfaces page is used to to set up network interfaces.
This manual page provides an overview of the Interfaces page in {{{name}}} devices.
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.
Network Interfaces
The Network Interfaces section displays interfaces currently existing on this device.
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_{{{lan}}}_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}.png|border|class=tlt-border]]
Add Interface
The Add Interface section is used to create additional network interfaces. To create a new interface, simply enter a custom name for it and click the 'Add' button.
Interface configuration
This section provides information on network interface configuration. There are {{{no_of_if}}} main types of interfaces on the device:
- Ethernet LAN
Different types of interfaces can be configured under different protocols:
Static | DHCP | DHCPv6 | PPPoE | Mobile | |
---|---|---|---|---|---|
Ethernet LAN |
To begin configuring an interface, click the 'Edit' button on the right side of the interface:
[[File:Networking_rutos_manual_interfaces_network_interfaces_edit_button_lan_{{{lan}}}.png]]
General Setup
The General Setup section is used to configure the protocol of an interface and all the different parameters that go along with each protocol. If None protocol is chosen, all other interface settings will be ignored. The following sections are different for each protocol.
General Setup: Static
The static protocol uses a predefined manual configuration instead of obtaining parameters automatically via a DHCP lease.
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_static_ip_lan_{{{lan}}}.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
IPv4 address | ip4; default[for LAN]: 192.168.1.1 | The IPv4 address interface of this interface. An IP address identifies a device on a network and allows it to communicate with other devices. |
IPv4 netmask | netmask; default[for LAN]: 255.255.255.0 | The IPv4 netmask of this interface. A netmask is used to define how "large" a network is by specifying which part of the IP address denotes the network and which part denotes a device. |
IPv4 gateway | ip4; default: none | The IPv4 gateway address used by this interface. An interface's default gateway is the default address through which all outgoing traffic is directed. |
IPv4 broadcast | ip4; default: none | The IPv4 broadcast address used by this interface. IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers. |
DNS servers | ip4; default: none | DNS server addresses that this interface will use. If left empty, DNS servers are assigned automatically. To see what DNS servers are currently used, you can check the contents of the /tmp/resolv.conf.auto file. |
General Setup: DHCP
The DHCP protocol is used to set up an interface which obtains its configuration parameters automatically via a DHCP lease.
Field | Value | Description |
---|---|---|
Hostname to send when requesting DHCP | string; default: none | A hostname for this interface used to identify this machine on the DHCP server. |
General Setup: DHCPv6
The DHCPv6 protocol is used to set up an IPv6 interface which obtains its configuration parameters automatically via a DHCP lease.
Field | Value | Description |
---|---|---|
Request IPv6-address | try | force | disabled; default: try | Defines the behaviour for requesting an address. |
Request IPv6-prefix of length | integer [0..64] | Automatic | disabled ; default: Automatic | Defines how this will request a IPv6 ULA-Prefix length. If set to 'disabled' the interface will obtain a single IPv6 address without a subnet for routing. |
General Setup: PPPoE
The PPPoE protocol is used to set up a PPP (Point-to-Point Protocol) connection over the Ethernet port.
Field | Value | Description |
---|---|---|
PAP/CHAP username | string; default: none | Username used in PAP/CHAP authentication. |
PAP/CHAP password | string; default: none | Password used in PAP/CHAP authentication. |
Access Concentrator | string; default: none | The Access Concentrator to connect to. ISPs used Access Concentrators to route their PPPoE connections. Usually, the settings are received automatically, however in some cases it is required to specify the name for an Access Concentrator. Leave empty to detect Access Concentrators automatically. |
Service name | string; default: none | The Service Name to connect to. Leave empty to detect Service name automatically. |
Advanced Settings
The Advanced Settings section is used to set up some of the more specific and less frequently used interface parameters. This section is different for each protocol.
Advanced Settings: Static
Advanced Settings information for Static protocol is provided in the table below.
Field | Value | Description |
---|---|---|
Bring up on boot | off | on; default: on | Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot. |
Use built in IPv6-management | off | on; default: on | Specifies whether to enable prefix delegation. |
Force link | off | on; default: on | Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active. |
Override MAC address | mac; default: none | When set, uses a user-defined MAC address for the interface instead of the default one. |
Override MTU | integer [1..9200]; default: none | Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction. |
Use gateway metric | integer; default: none | A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority). |
IPv6 assignment length | integer [0..64] | Disabled; default: Disabled | Delegates a prefix of given length to the interface. |
IPv6 address | ip6; default: none | The interface's IPv6 address. An IP address identifies a device on a network and allows it to communicate with other devices. Note: this field only becomes visible when IPv6 assignment length is set to disabled |
IPv6 gateway | ip6; default: none | IPv6 prefix routed here for use on other interfaces. Note: this field only becomes visible when IPv6 assignment length is set to disabled. |
IPv6 routed prefix | ip6; default: none | IPv6 prefix routed here for use on other interfaces. Note: this field only becomes visible when IPv6 assignment length is set to disabled. |
IPv6 assignment hint | string; default: none | The subprefix-ID that should be delegated as hexadecimal number. |
IPv6 suffix | ip6 suffix; default: none | When an IPv6 prefix (like 'a:b:c:d::') is received from a delegating server, use a suffix (like '::1') to form an IPv6 address ('a:b:c:d::1') for the interface. Leave empty to generate a random suffix. |
Advanced Settings: DHCP
Advanced Settings information for DHCP protocol is provided in the table below.
Field | Value | Description |
---|---|---|
Bring up on boot | off | on; default: on | Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot. |
Use built-in IPv6 management | off | on; default: on | Specifies whether to enable prefix delegation. |
Force link | off | on; default: off | Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active. |
Use broadcast flag | off | on; default: off | Required for certain ISPs. For example, Charter with DOCSIS 3. |
Use default gateway | off | on; default: on | When checked, creates a default route for the interface. |
Use DNS servers advertised by peer | off | on; default: on | Specifies whether to use DNS servers obtained automatically or specified manually. |
Use custom DNS servers | off | on; default: on | Specifies whether to use DNS servers obtained automatically or specified manually. Note: this field only becomes visible when Use DNS servers advertised by peer is set to off |
Use gateway metric | integer; default: none | A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority). |
Client ID to send when requesting DHCP | string; default: none | Client ID which will be sent when requesting a DHCP lease. |
Vendor Class to send when requesting DHCP | string; default: none | Vendor class which will be sent when requesting a DHCP lease. |
Override MAC address | mac; default: none | When set, uses a user-defined MAC address for the interface instead of the default one. |
Override MTU | integer [1..9200]; default: none | Changes the interfaces allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction. |
Advanced Settings: DHCPv6
Advanced Settings information for DHCPv6 protocol is provided in the table below.
Field | Value | Description |
---|---|---|
Bring up on boot | off | on; default: on | Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot. |
Use built in IPv6-management | off | on; default: on | Specifies whether to enable prefix delegation. |
Force link | off | on; default: off | Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active. |
Use default gateway | off | on; default: on | When checked, creates a default route for the interface. |
Use DNS servers advertised by peer | off | on; default: on | Specifies whether to use DNS servers obtained automatically or specified manually. |
Use custom DNS servers | off | on; default: on | Specifies whether to use DNS servers obtained automatically or specified manually. Note: this field only becomes visible when Use DNS servers advertised by peer is set to off |
Custom delegated IPv6-prefix | ip6 prefix; default: none | Uses an (additional) user-provided IPv6 prefix for distribution to clients. |
Client ID to send when requesting DHCP | string; default: none | Client ID which will be sent when requesting a DHCP lease. |
Override MAC address | mac; default: none | When set, uses a user-defined MAC address for the interface instead of the default one. |
Override MTU | integer [1..9200]; default: none | Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction. |
Advanced Settings: PPPoE
Advanced Settings information for PPPoE protocol is provided in the table below.
Field | Value | Description |
---|---|---|
Bring up on boot | off | on; default: on | Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot. |
Use built-in IPv6 management | off | on; default: on | Specifies whether to enable prefix delegation. |
Force link | off | on; default: off | Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active. |
Obtain IPv6 address | Automatic | Disabled | Manual; default: Automatic | Defines behaviour for obtaining an IPv6 address. |
Use default gateway | off | on; default: on | When checked, creates a default route for the interface. |
Use gateway metric | integer; default: none | A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority). |
Use DNS servers advertised by peer | off | on; default: on | Specifies whether to use DNS servers obtained automatically or specified manually. |
Use custom DNS servers | off | on; default: on | Specifies whether to use DNS servers obtained automatically or specified manually. Note: this field only becomes visible when Use DNS servers advertised by peer is set to off |
LCP echo failure threshold | integer; default: none | Presumes peer to be dead after given amount of LCP echo failures. Leave it at 0 to ignore failures. |
LCP echo interval | integer; default: none | Sends LCP echo requests at the given interval in seconds. This function is only effective in conjunction with failure threshold. |
Host-Uniq tag content | raw hex-encoded bytes; default: none | Leave empty unless your ISP require this. |
Inactivity timeout | mac; default: none | Close inactive connection after the given amount of seconds. Leave it at 0 to persist connection. |
Override MTU | integer [1..1500]; default: none | Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet. |
Physical Settings
The Physical Settings section is used to create associations with physical interfaces and bridge network interfaces.
Field | Value | Description |
---|---|---|
Bridge interfaces | off | on; default: off | Bridges physical interfaces specified in this configuration. |
Enable STP | off | on; default: off | Turns the use of Spanning Tree Protocol (STP) for this interface on or off. Note: this field becomes visible when 'Bridge interfaces' is set to on |
Interface | network interface(s); default: none | Ties this network interface to physical device interfaces such as Ethernet . |
Firewall Settings
The Firewall Settings section is used to specify to which firewall zone if any this interface belongs. Assigning an interface to a zone may provide easier configuration of firewall rules. For example, instead of configuring separate rules for each WAN interface, you can add all WAN interfaces into a single firewall zone and make the rule apply to that zone instead.
More firewall zone settings can be configured from the Network → Firewall → General Settings → [[{{{name}}}_Firewall#Zones|Zones]] section.
Field | Value | Description |
---|---|---|
Create / Assign firewall-zone | firewall zone; default: none | Assigns this interface to the specified firewall zone. |
DHCP Server
A DHCP (Dynamic Host Configuration Protocol) server is a service that can automatically configure the TCP/IP settings of any device that requests such a service. If you connect a device that has been configured to obtain an IP address automatically, the DHCP server will lease out an IP address from the available IP pool and the device will be able to communicate within the private network.
In order to view the DHCP server configuration, the interface protocol must be set to Static.
DHCP Server: General Setup
The General Setup 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]]
Field | Value | Description |
---|---|---|
Enable DHCP | Enable | Disable | DHCP Relay*; default: Enable | Turns the DHCP server on or off or enables DHCP relay*. If DHCP Relay* is selected, you will be prompted to enter an IP address of another DHCP server in your LAN. In this case, whenever a new machine connects to this device, it will redirect any DHCP requests to the specified DHCP Server. |
Start | integer [1..255]; default: 100 | 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.100. |
Limit | integer [1..255]; default: 150 | 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.100 to 192.168.1.249 (100 + 150 – 1 = 249; this is because the first address is inclusive). |
Lease time | integer [2..999999]m/h; default: 12h | 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). The minimal amount of time that can be specified is 2 minutes. |
* When an interface is set to act as a DHCP Relay, it redirects all received DHCP request messages to another specified DHCP server:
DHCP Server: Advanced Settings
Refer to the table below for information on the Advanced Settings section.
Field | Value | Description |
---|---|---|
Dynamic DHCP | off | on; default: on | Enables dynamic allocation of client addresses. If this is disabled, only clients that have static IP leases will be served. |
Force | off | on; default: off | The DHCP force function ensures that the device will always start it’s DHCP server, even if there is another DHCP server already running in the its network. By default the device’s DHCP server will not start when it is connected to a network segment that already has a working DHCP server. |
IPv4 Netmask | netmask; default: none | Sends a different netmask than the LAN netmask to DHCP clients. |
DHCP Options | dhcp options; default: none | Additional options to be added to the DHCP server. For example with '26,1470' or 'option:mtu, 1470' you can assign an MTU value per DHCP. You can find more information on DHCP Options here. |
DHCP Server: IPv6 Settings
Refer to the table below for information on the IPv6 Settings section.
Field | Value | Description |
---|---|---|
Router Advertisement Service | Disabled | Relay mode | Server mode | Hybrid mode; default: Disabled | Specifies whether router advertisements should be enabled (server mode), relayed or disabled. |
DHCPv6 Service | Disabled | Relay mode | Server mode | Hybrid mode; default: Disabled | Specifies whether DHCPv6 server should be enabled (server), relayed (relay) or disabled (disabled). |
NDP Proxy | Disabled | Relay mode | Hybrid mode; default: Disabled | Specifies whether NDP should be relayed or disabled. |
DHCPv6 Mode | Stateless | Stateful-only | Stateless + stateful; default: Stateless + stateful | Router announcement (RA) mode. |
Always announce default router | off | on; default: off | Default router lifetime in the the router announcement (RA) message will be set if default route is present and a global IPv6 address or if default route is present but no global IPv6 address or neither of both conditions. |
Announced DNS server | ip; default: none | Supplements DHCP-assigned DNS server entries with ones specified in this field. |
Announced DNS domains | ip; default: none | DNS domain handed out to DHCP clients. |
Static Lease
Static IP leases are used to reserve specific IP addresses for specific devices by binding them to their MAC address. This is useful when you have a stationary device connected to your network that you need to reach frequently, e.g., printer, IP phone, etc.
This section displays static IP leases currently existing on this device. In order to view the Static Lease section, the interface protocol must be set to Static.
The Static Lease list is empty by default. To add a new Static Lease look to the Add Lease section; enter a custom name for the lease and click the 'Add' button.
You should be redirected to the Settings page for that lease, which should look similar to this:
Field | Value | Description |
---|---|---|
MAC address | mac; default: none | MAC address of a device that will connect to this network interface. |
IP address | ip; default: none | The IP address that will be reserved for the specified device. |
After you click 'Save & Apply' you will be redirected back to the Network Interfaces page. If you wish to modify the lease later, you can find in the Static Lease list. Simply click the 'Edit' button next to it in order to enter the Settings page for the Static Lease.
[[Category:{{{name}}} Network section]]