Jump to content

Template:Networking rutos manual dhcp: Difference between revisions

No edit summary
No edit summary
(11 intermediate revisions by 2 users not shown)
Line 15: Line 15:


This manual page provides an overview of DHCP page in {{{name}}} devices.
This manual page provides an overview of DHCP page in {{{name}}} devices.
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = {{{series}}}
}}


==Static Leases==
==Static Leases==
Line 29: Line 25:
The Static Lease list is empty by default. To add a new Static Lease click the 'Add' button.
The Static Lease list is empty by default. To add a new Static Lease click the 'Add' button.


[[File:Networking_rutos_manual_dhcp_static_leases_add_button.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_dhcp_static_leases_add_button_v1.png|border|class=tlt-border]]


Appears static lease, which should look similar to this:
Appears static lease, which should look similar to this:


[[File:Networking_rutos_manual_dhcp_static_leases.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_dhcp_static_leases_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 44: Line 40:
       <td>MAC</td>
       <td>MAC</td>
       <td>mac; default: <b>none</b></td>
       <td>mac; default: <b>none</b></td>
       <td>MAC address of a device that will connect to this network interface.</td>
       <td>MAC address of a device that will connect to this network interface. Possible variants: MAC address: 01:23:45:56:78:9a, Wildcard: 01:23:45:56:*:*</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 52: Line 48:
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Description</td>
     <td>Hostname</td>
        <td>string; default: <b>none</b></td>
        <td>Name of static lease.</td>
    </tr>
</table>
 
Additionally there is a IPv6 tab for IPv6 static leases.
 
[[File:Networking rutos manual dhcp static leases ipv6 v1.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>DUID</td>
      <td>DUID; default: <b>none</b></td>
      <td>DHCP unique identifier is used by DHCPv6 to identify device. Similar to MAC that is used by DHCPv4.</td>
    </tr>
    <tr>
    <td>Host ID</td>
        <td>ipv6; default: <b>none</b></td>
        <td>Used to define IPv6 address that will be statically leased. To get it from the IPv6 address remove the IPv6 prefix and all semicolons.</td>
    </tr>
    <tr>
    <td>Hostname</td>
         <td>string; default: <b>none</b></td>
         <td>string; default: <b>none</b></td>
         <td>Name of static lease.</td>
         <td>Name of static lease.</td>
Line 61: Line 84:


==DHCP server configuration==
==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.
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.


Line 70: Line 93:
To edit lan interface DHCPv4 settings click the 'Edit' button.
To edit lan interface DHCPv4 settings click the 'Edit' button.


[[File:Networking_rutos_manual_dhcpv4_server.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_dhcpv4_server_v1.png|border|class=tlt-border]]
 
The information button shows the number of dynamic and static leases:
 
[[File:Networking_rutos_manual_dhcpv4_server_general_setup_info.png|border|class=tlt-border]]


====DHCPv4 general setup====
====DHCPv4 general setup====
Line 108: Line 135:
     <tr>
     <tr>
         <td><span style="color:red">Lease time</span></td>
         <td><span style="color:red">Lease time</span></td>
         <td>integer [1..999999]; default: <b>12</b>integer [2..999999]<span class="asterisk">*</span>integer [120..999999]<span class="asterisk">**</span></td>
         <td>integer [1..999999] | infinite<span class="asterisk">*</span>; default: <b>12</b>integer [2..999999]<span class="asterisk">**</span>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).The minimal amount of time that can be specified is 2 minutes.<br><span class="asterisk">*</span>Infinite option DHCP address will never expire.<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>
         <td><span style="color:blue">DHCP server</span></td>
         <td><span style="color:blue">DHCP server</span></td>
         <td>ip; default: <b>none</b></td>
         <td>ip; default: <b>none</b></td>
         <td>LSpecifies DHCP server's IP address, which directs any requests into server.</td>
         <td>Specifies DHCP server's IP address, which directs any requests into server.</td>
     </tr>
     </tr>
</table>
</table>
Line 157: Line 184:
Custom DHCP options are number and value pairs used to configure advanced DHCP functionality. It does not configure DHCP ipv6!. The <b>DHCP options</b> modal is used to 'Add', 'Delete', 'Save' multiple options.
Custom DHCP options are number and value pairs used to configure advanced DHCP functionality. It does not configure DHCP ipv6!. The <b>DHCP options</b> modal is used to 'Add', 'Delete', 'Save' multiple options.


[[File:Networking_rutos_manual_dhcpv4_server_advanced_settings_dhcp_options.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_dhcpv4_server_advanced_settings_dhcp_options_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 259: Line 286:


<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:
<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:
<b>Note:</b> devices with EG060K-EA modem module support DHCP Relay over mobile connection.


[[File:Networking_rutx_manual_lan_static_dhcp_server_relay_scheme_v2.png]]
[[File:Networking_rutx_manual_lan_static_dhcp_server_relay_scheme_v2.png]]


[[Category:{{{name}}} Network section]]
[[Category:{{{name}}} Network section]]