| Line 1: |
Line 1: |
| − | {{Template: Networking_rutos_manual_fw_disclosure | + | {{Template: Networking_device_manual_fw_disclosure |
| − | | fw_version ={{Template: Networking_rutos_manual_latest_fw | + | | series = {{{series}}} |
| | + | | name = {{{name}}} |
| | + | | fw_version ={{Template: Networking_device_manual_latest_fw |
| | | series = {{{series}}} | | | series = {{{series}}} |
| | | name = {{{name}}} | | | name = {{{name}}} |
| | }} | | }} |
| | }} | | }} |
| − | {{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} LAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}} | + | {{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} LAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}} |
| − | {{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} LAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}} | + | {{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} LAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}} |
| | ==Summary== | | ==Summary== |
| | | | |
| Line 12: |
Line 14: |
| | | | |
| | This manual page provides an overview of the LAN windows in {{{name}}} devices. | | This manual page provides an overview of the LAN windows in {{{name}}} devices. |
| | + | |
| | + | {{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer |
| | + | | series = {{{series}}} |
| | + | }} |
| | | | |
| | ==LAN== | | ==LAN== |
| Line 18: |
Line 24: |
| | | | |
| | [[File:Networking_rutos_manual_lan_settings_v3.png|border|class=tlt-border]] | | [[File:Networking_rutos_manual_lan_settings_v3.png|border|class=tlt-border]] |
| | + | |
| | + | If you hover mouse over the question mark [[File:Networking_rutos_manual_wan_question_mark.png]] global IPv6 prefix assignment addresses will be displayed. |
| | + | |
| | + | [[File:Networking_rutos_manual_lan_question_mark_info.png|border|class=tlt-border]] |
| | | | |
| | The <b>Add New Instance</b> 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. | | The <b>Add New Instance</b> 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. |
| Line 86: |
Line 96: |
| | <tr> | | <tr> |
| | <td>IPv6 assignment length</td> | | <td>IPv6 assignment length</td> |
| − | <td>integer [0..60]; default: <b>60</b></td> | + | <td>Disabled | 64 | Custom - integer [0..6]; default: <b>60</b></td> |
| | <td>Assign a part of given length of every public IPv6-prefix to this interface.</td> | | <td>Assign a part of given length of every public IPv6-prefix to this interface.</td> |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
| | <td>IPv6 assignment hint</td> | | <td>IPv6 assignment hint</td> |
| − | <td>64 | Disabled | Custom - a hexadecimal string of symbols: a-f, A-F and 0-9 is accepted; default: <b>none</b></td> | + | <td>A hexadecimal string of symbols: a-f, A-F and 0-9 is accepted; default: <b>none</b></td> |
| | <td>Assign prefix parts using this hexadecimal subprefix ID for this interface.</td> | | <td>Assign prefix parts using this hexadecimal subprefix ID for this interface.</td> |
| | </tr> | | </tr> |
| Line 186: |
Line 196: |
| | </tr> | | </tr> |
| | </table> | | </table> |
| − | ===DHCP server configuration===
| |
| − | ----
| |
| − | A <b>DHCP</b> (<b>Dynamic Host Configuration Protocol</b>) 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.
| |
| − |
| |
| − | [[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]]
| |
| − |
| |
| − | <i>To make the DHCP Server section visible, <b>set interface protocol to Static</b>.</i>
| |
| − |
| |
| − | ====General setup====
| |
| − | The <b>General Setup</b> section is used to set up the main operating parameters of the DHCP server.
| |
| − |
| |
| − | [[File:Networking_rutos_manual_lan_configuration_dhcp_server_general_setup.png|border|class=tlt-border]]
| |
| − |
| |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>Field</th>
| |
| − | <th>Value</th>
| |
| − | <th>Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable DHCP</td>
| |
| − | <td>Enable | Disable | Relay<span class="asterisk">*</span>; default: <b>Enable</b></td>
| |
| − | <td>Turns the DHCP server on or off or enables DHCP relay<span class="asterisk">*</span>.<br>If DHCP Relay<span class="asterisk">*</span> 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.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Start IP</td>
| |
| − | <td>integer [1..255]; default: <b>100</b></td>
| |
| − | <td>The DHCP server's IP address range start value.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>End IP</td>
| |
| − | <td>integer [1..255]; default: <b>254</b></td>
| |
| − | <td>End IP, i.e., the last possible IP in the selected range for the DHCP server.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <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>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>
| |
| − | <td>Units</td>
| |
| − | <td>Hours | Minutes | Seconds; default: <b>Hours</b></td>
| |
| − | <td>Lease time measurement units.</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | ====Advanced settings====
| |
| − | Refer to the table below for information on the <b>Advanced Settings</b> section.
| |
| − |
| |
| − | [[File:Networking_rutos_manual_lan_configuration_dhcp_server_advanced_settings.png|border|class=tlt-border]]
| |
| − |
| |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>Field</th>
| |
| − | <th>Value</th>
| |
| − | <th>Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Dynamic DHCP</td>
| |
| − | <td>off | on; default: <b>on</b></td>
| |
| − | <td>Enables dynamic allocation of client addresses. If this is disabled, only clients that have static IP leases will be served.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Force</td>
| |
| − | <td>off | on; default: <b>off</b></td>
| |
| − | <td>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.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>IPv4-Netmask</td>
| |
| − | <td>netmask; default: <b>none</b></td>
| |
| − | <td>Sends a different netmask than the LAN netmask to DHCP clients.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Custom DHCP Options</td>
| |
| − | <td>-(interactive button)</td>
| |
| − | <td>Custom DHCP options are number and value pairs used to configure advanced DHCP functionality. It does not configure DHCP ipv6!</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Force DHCP options</td>
| |
| − | <td>off | on; default: <b>off</b></td>
| |
| − | <td>If enabled, DHCP options will be sent even if it's not requested.</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | ====DHCP Server: IPv6 Settings====
| |
| − | ----
| |
| − | Refer to the table below for information on the <b>IPv6 Settings</b> section.
| |
| − |
| |
| − | [[File:Networking_rutos_manual_lan_configuration_dhcp_server_ipv6_settings.png|border|class=tlt-border]]
| |
| − |
| |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>Field</th>
| |
| − | <th>Value</th>
| |
| − | <th>Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Router Advertisement Service</td>
| |
| − | <td>Disabled | Relay mode | Server mode | Hybrid mode; default: <b>Disabled</b></td>
| |
| − | <td>Specifies whether router advertisements should be enabled (server mode), relayed or disabled. </td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>DHCPv6 Service</td>
| |
| − | <td>Disabled | Relay mode | Server mode | Hybrid mode; default: <b>Disabled</b></td>
| |
| − | <td>Specifies whether DHCPv6 server should be enabled (server), relayed (relay) or disabled (disabled).</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>NDP Proxy</td>
| |
| − | <td>Disabled | Relay mode | Hybrid mode; default: <b>Disabled</b></td>
| |
| − | <td>Specifies whether NDP should be relayed or disabled.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Announced DNS server</td>
| |
| − | <td>ip; default: <b>none</b></td>
| |
| − | <td>Supplements DHCP-assigned DNS server entries with ones specified in this field.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Announced DNS domains</td>
| |
| − | <td>ip; default: <b>none</b></td>
| |
| − | <td>DNS domain handed out to DHCP clients.</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − |
| |
| − | <span class="asterisk">*</span> When an interface is set to act as a DHCP Relay, it redirects all received DHCP request messages to another specified DHCP server:
| |
| − |
| |
| − | [[File:Networking_rutx_manual_lan_static_dhcp_server_relay_scheme_v2.png]]
| |
| | | | |
| | [[Category:{{{name}}} Network section]] | | [[Category:{{{name}}} Network section]] |