Jump to content
  • EN

Template:Networking rutos manual interfaces: Difference between revisions

← Older editNewer edit →
VisualWikitext
No edit summary
No edit summary
Line 300: Line 300:
<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:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_static_v2.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_static.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 324: Line 324:
     </tr>
     </tr>
     <tr>
     <tr>
         <td>IP4table</td>
         <td>Use broadcast flag</td>
         <td>integer [0..99999999]; default: <b>none</b></td>
        <td>off | on; default: <b>off</b></td>
         <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
        <td>Required for certain ISPs. For example, Charter with DOCSIS 3.</td>
    </tr>
    <tr>
        <td>Use default gateway</td>
        <td>off | on; default: <b>on</b></td>
        <td>When checked, creates a default route for the interface.</td>
    </tr>
    <tr>
        <td>Use gateway metric</td>
         <td>integer; default: <b>3</b></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>
        <td>Use custom DNS servers</td>
        <td>off | on; default: <b>on</b></td>
        <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
    </tr>
    <tr>
        <td>Client ID to send when requesting DHCP</td>
        <td>string; default: <b>none</b></td>
         <td>Client ID which will be sent when requesting a DHCP lease.</td>
    </tr>
    <tr>
        <td>Vendor Class to send when requesting DHCP</td>
        <td>string; default: <b>none</b></td>
        <td>Vendor class which will be sent when requesting a DHCP lease.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 339: Line 364:
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Use gateway metric</td>
         <td>IP4table</td>
         <td>integer; default: <b>3</b></td>
         <td>integer [0..99999999]; 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>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
     </tr>
     </tr>
    <tr>
<!--<tr>
         <td>IPv6 assignment length</td>
         <td>IPv6 assignment length</td>
         <td>integer [0..64] | <span style="color: #1550bf; font-weight: bold;">Disabled</span>; default: <b>Disabled</b></td>
         <td>integer [0..64] | <span style="color: #1550bf; font-weight: bold;">Disabled</span>; default: <b>Disabled</b></td>
Line 373: Line 398:
         <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>


Retrieved from "https://wiki.teltonika-networks.com/view/Template:Networking_rutos_manual_interfaces"