Template:Networking rutos manual lan: Difference between revisions
no edit summary
No edit summary |
Gytispieze (talk | contribs) No edit summary |
||
Line 54: | Line 54: | ||
<td>netmask; default: <b>255.255.255.0</b></td> | <td>netmask; default: <b>255.255.255.0</b></td> | ||
<td>The IPv4 netmask of this interface. A <b>[[What is a Netmask?|netmask]]</b> 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.</td> | <td>The IPv4 netmask of this interface. A <b>[[What is a Netmask?|netmask]]</b> 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.</td> | ||
</tr> | |||
<tr> | |||
<td>IPv4 gateway</td> | |||
<td>ip4; default: none</td> | |||
<td>The IPv4 gateway address used by this interface. An interface's default gateway is the default address through which all outgoing traffic is directed.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 59: | Line 64: | ||
<td>ip4; default: <b>none</b></td> | <td>ip4; default: <b>none</b></td> | ||
<td>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 <i>/tmp/resolv.conf.auto</i> file.</td> | <td>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 <i>/tmp/resolv.conf.auto</i> file.</td> | ||
</tr> | </tr> | ||
{{#ifeq:{{{LAN_to_WAN}}}| 1 | | {{#ifeq:{{{LAN_to_WAN}}}| 1 | | ||
Line 83: | Line 72: | ||
</tr> | </tr> | ||
|}} | |}} | ||
</table> | </table> | ||
Line 132: | Line 111: | ||
<tr> | <tr> | ||
<td>Lease time</td> | <td>Lease time</td> | ||
<td>integer [ | <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.</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> | ||
<td>Units</td> | <td>Units</td> | ||
<td>Hours | Minutes; default: <b>Hours</b></td> | <td>Hours | Minutes | Seconds; default: <b>Hours</b></td> | ||
<td>Lease time measurement units.</td> | <td>Lease time measurement units.</td> | ||
</tr> | </tr> |