| Line 24: |
Line 24: |
| | [[Image:Network wan none protocol rut850.PNG]] | | [[Image:Network wan none protocol rut850.PNG]] |
| | | | |
| − | {| class="wikitable"
| + | <table class="nd-mantable"> |
| − | |+
| + | <tr> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
| + | <th>field name</th> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
| + | <th>value</th> |
| − | ! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
| + | <th>description</th> |
| − | |-
| + | </tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Protocol
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''
| + | <td>Protocol</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The protocol used by the WAN interface
| + | <td>Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''</td> |
| − | |-
| + | <td>The protocol used by the WAN interface</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IPv4 address
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Your router’s address on the WAN network
| + | <td>IPv4 address</td> |
| − | |-
| + | <td>ip; Default: " "</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IPv4 netmask
| + | <td>Your router’s address on the WAN network</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: '''255.255.255.0'''
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Netmask defines how "large" a network is
| + | <tr> |
| − | |-
| + | <td>IPv4 netmask</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IPv4 gateway
| + | <td>ip; Default: '''255.255.255.0'''</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <td>Netmask defines how "large" a network is</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The address where the router will send all the outgoing traffic
| + | </tr> |
| − | |-
| + | <tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IPv4 broadcast
| + | <td>IPv4 gateway</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <td>ip; Default: " "</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers
| + | <td>The address where the router will send all the outgoing traffic</td> |
| − | |-
| + | </tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Use custom DNS servers
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <td>IPv4 broadcast</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | When the router needs to resolve a hostname (“www.google.com”, “www.cnn.com”, etc.) to an IP address, it will forward all the DNS requests to the gateway. By entering custom DNS servers the router will take care of the host name resolution. You can enter multiple DNS servers to provide redundancy in case one of the servers fails
| + | <td>ip; Default: " "</td> |
| − | |-
| + | <td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td> |
| − | |}
| + | </tr> |
| | + | <tr> |
| | + | <td>Use custom DNS servers</td> |
| | + | <td>ip; Default: " "</td> |
| | + | <td>When the router needs to resolve a hostname (“www.google.com”, “www.cnn.com”, etc.) to an IP address, it will forward all the DNS requests to the gateway. By entering custom DNS servers the router will take care of the host name resolution. You can enter multiple DNS servers to provide redundancy in case one of the servers fails</td> |
| | + | </tr> |
| | + | </table> |
| | | | |
| | ====Advanced==== | | ====Advanced==== |
| Line 62: |
Line 68: |
| | [[Image:Network wan static advanced.PNG]] | | [[Image:Network wan static advanced.PNG]] |
| | | | |
| − | {| class="wikitable"
| + | <table class="nd-mantable"> |
| − | |+
| + | <tr> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
| + | <th>field name</th> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
| + | <th>value</th> |
| − | ! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
| + | <th>description</th> |
| − | |-
| + | </tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Disable NAT
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| + | <td>Disable NAT</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Toggles Network Address Translation (NAT) on or off for the selected network interface
| + | <td>yes {{!}} no; Default: '''no'''</td> |
| − | |-
| + | <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Override MAC address
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | mac; Default: '''router's mac'''
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your router). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer
| + | <td>Override MAC address</td> |
| − | |-
| + | <td>mac; Default: '''router's mac'''</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Override MTU
| + | <td>Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your router). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | integer [0..1500]; Default: '''1500'''
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet
| + | <tr> |
| − | |-
| + | <td>Override MTU</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Use gateway metric
| + | <td>integer [0..1500]; Default: '''1500'''</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | integer; Default: '''0'''
| + | <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority
| + | </tr> |
| − | |-
| + | <tr> |
| − | |}
| + | <td>Use gateway metric</td> |
| | + | <td>integer; Default: '''0'''</td> |
| | + | <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority</td> |
| | + | </tr> |
| | + | </table> |
| | | | |
| | ===DHCP=== | | ===DHCP=== |
| Line 94: |
Line 104: |
| | [[Image:Network wan dhcp general.PNG]] | | [[Image:Network wan dhcp general.PNG]] |
| | | | |
| − | {| class="wikitable"
| + | <table class="nd-mantable"> |
| − | |+
| + | <tr> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
| + | <th>field name</th> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
| + | <th>value</th> |
| − | ! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
| + | <th>description</th> |
| − | |-
| + | </tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Protocol
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''
| + | <td>Protocol</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The protocol used by the WAN interface
| + | <td>Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''</td> |
| − | |-
| + | <td>The protocol used by the WAN interface</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Hostname to send when requesting DHCP
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip {{!}} hostname; Default: '''router's hostname'''
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Host name to which the DHCP request will be sent to
| + | <td>Hostname to send when requesting DHCP</td> |
| − | |-
| + | <td>ip {{!}} hostname; Default: '''router's hostname'''</td> |
| − | |}
| + | <td>Host name to which the DHCP request will be sent to</td> |
| | + | </tr> |
| | + | </table> |
| | | | |
| | ====Advanced==== | | ====Advanced==== |
| Line 116: |
Line 128: |
| | [[Image:Network wan dhcp advanced.PNG]] | | [[Image:Network wan dhcp advanced.PNG]] |
| | | | |
| − | {| class="wikitable"
| + | <table class="nd-mantable"> |
| − | |+
| + | <tr> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
| + | <th>field name</th> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
| + | <th>value</th> |
| − | ! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
| + | <th>description</th> |
| − | |-
| + | </tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Disable NAT
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| + | <td>Disable NAT</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Toggles Network Address Translation (NAT) on or off for the selected network interface
| + | <td>yes {{!}} no; Default: '''no'''</td> |
| − | |-
| + | <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Use broadcast flag
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Required for certain ISPs (Internet Service Providers), e.g. Charter with DOCSIS 3
| + | <td>Use broadcast flag</td> |
| − | |-
| + | <td>yes {{!}} no; Default: '''no''' </td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Use default gateway
| + | <td>Required for certain ISPs (Internet Service Providers), e.g. Charter with DOCSIS 3</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''yes'''
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Uses the default gateway obtained through DHCP. If left unchecked, no default route is configured
| + | <tr> |
| − | |-
| + | <td>Use default gateway</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Use DNS servers advertised by peer
| + | <td>yes {{!}} no; Default: '''yes'''</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| + | <td>Uses the default gateway obtained through DHCP. If left unchecked, no default route is configured</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Uses DNS servers obtained from DHCP. If left unchecked, the advertised DNS server addresses are ignored
| + | </tr> |
| − | |-
| + | <tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Use custom DNS servers
| + | <td>Use DNS servers advertised by peer</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <td>yes {{!}} no; Default: '''no'''</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Lets you chose your own preferred DNS servers. This field only becomes visible if '''Use DNS servers advertised by peer''' field is unchecked
| + | <td>Uses DNS servers obtained from DHCP. If left unchecked, the advertised DNS server addresses are ignored</td> |
| − | |-
| + | </tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Use gateway metric
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <td>Use custom DNS servers</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority
| + | <td>ip; Default: " "</td> |
| − | |-
| + | <td>Lets you chose your own preferred DNS servers. This field only becomes visible if '''Use DNS servers advertised by peer''' field is unchecked</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Client ID to send when requesting DHCP
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | string; Default: " "
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Client ID which will be sent when requesting a DHCP lease
| + | <td>Use gateway metric</td> |
| − | |-
| + | <td>ip; Default: " "</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Vendor class to send when requesting DHCP
| + | <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority </td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | string; Default: " "
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Vendor class which will be sent when requesting a DHCP lease
| + | <tr> |
| − | |-
| + | <td>Client ID to send when requesting DHCP</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Override MAC address
| + | <td>string; Default: " "</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | mac; Default: '''router's mac'''
| + | <td>Client ID which will be sent when requesting a DHCP lease</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your router). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer
| + | </tr> |
| − | |-
| + | <tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Override MTU
| + | <td>Vendor class to send when requesting DHCP</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | integer [0..1500]; Default: '''1500'''
| + | <td>string; Default: " "</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet
| + | <td>Vendor class which will be sent when requesting a DHCP lease</td> |
| − | |-
| + | </tr> |
| − | |}
| + | <tr> |
| | + | <td>Override MAC address</td> |
| | + | <td>mac; Default: '''router's mac'''</td> |
| | + | <td>Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your router). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer</td> |
| | + | </tr> |
| | + | <tr> |
| | + | <td>Override MTU</td> |
| | + | <td>nteger [0..1500]; Default: '''1500'''</td> |
| | + | <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet</td> |
| | + | </tr> |
| | + | </table> |
| | | | |
| | ==IP Aliases== | | ==IP Aliases== |
| Line 172: |
Line 194: |
| | [[Image:Network lan ipaliases.PNG]] | | [[Image:Network lan ipaliases.PNG]] |
| | | | |
| − | {| class="wikitable"
| + | <table class="nd-mantable"> |
| − | |+
| + | <tr> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
| + | <th>field name</th> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
| + | <th>value</th> |
| − | ! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
| + | <th>description</th> |
| − | |-
| + | </tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IP address
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <td>IP address</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | An alternate IP address used to reach the router by a device(s) that resides in the router's LAN but has a different subnet
| + | <td>ip; Default: " "</td> |
| − | |-
| + | <td>An alternate IP address used to reach the router by a device(s) that resides in the router's LAN but has a different subnet</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Netmask
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: '''255.255.255.0'''
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Netmask defines how "large" a network is
| + | <td>Netmask</td> |
| − | |-
| + | <td>ip; Default: '''255.255.255.0'''</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Gateway
| + | <td>Netmask defines how "large" a network is</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | A gateway is a network node that connects two networks using different protocols together
| + | <tr> |
| − | |-
| + | <td>Gateway</td> |
| − | |}
| + | <td>ip; Default: " "</td> |
| | + | <td>A gateway is a network node that connects two networks using different protocols together</td> |
| | + | </tr> |
| | + | </table> |
| | | | |
| | As you can see, the configuration is very similar to the static protocol; in the example above an IP address with a 99th subnet is defined. In this case, if some device has an IP in the 99th subnet (e.g., 192.168.99.xxx) and the subnet’s gateway metric is “higher” and the device is trying to reach the internet it will reroute it’s traffic not to the gateway that is defined in common configurations but through the one that is specified in IP aliases. | | As you can see, the configuration is very similar to the static protocol; in the example above an IP address with a 99th subnet is defined. In this case, if some device has an IP in the 99th subnet (e.g., 192.168.99.xxx) and the subnet’s gateway metric is “higher” and the device is trying to reach the internet it will reroute it’s traffic not to the gateway that is defined in common configurations but through the one that is specified in IP aliases. |
| Line 200: |
Line 225: |
| | [[Image:Network lan ipaliases advanced.PNG]] | | [[Image:Network lan ipaliases advanced.PNG]] |
| | | | |
| − | {| class="wikitable"
| + | <table class="nd-mantable"> |
| − | |+
| + | <tr> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
| + | <th>field name</th> |
| − | ! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
| + | <th>value</th> |
| − | ! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
| + | <th>description</th> |
| − | |-
| + | </tr> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IP Broadcast
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <td>IP Broadcast</td> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers
| + | <td>ip; Default: " "</td> |
| − | |-
| + | <td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td> |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | DNS
| + | </tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| + | <tr> |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | A separate DNS server to be used by the IP Alias address
| + | <td>DNS</td> |
| − | |-
| + | <td>ip; Default: " "</td> |
| − | |}
| + | <td>A separate DNS server to be used by the IP Alias address</td> |
| | + | </tr> |
| | + | </table> |
| | | | |
| | ==Backup Configuration== | | ==Backup Configuration== |
| Line 222: |
Line 249: |
| | [[Image:Network wan backup configuration.PNG]] | | [[Image:Network wan backup configuration.PNG]] |
| | | | |
| − | {| class="wikitable"
| + | <table class="nd-mantable"> |
| − | |+
| + | <tr> |
| − | ! style="width: 250px; background: black; color: white;" | Field name
| + | <th>field name</th> |
| − | ! style="width: 250px; background: black; color: white;" | Value
| + | <th>value</th> |
| − | ! style="width: 1200px; background: black; color: white;" | Description
| + | <th>description</th> |
| − | |-
| + | </tr> |
| − | ! style="text-align: left; vertical-align: top;" | Health monitor interval
| + | <tr> |
| − | | style="text-align: left; vertical-align: top;" | Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec. {{!}} ; Default: "10 sec."
| + | <td>Health monitor interval</td> |
| − | | style="text-align: left; vertical-align: top;" | The interval at which health checks are performed
| + | <td>Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; Default: '''10 sec.'''</td> |
| − | |-
| + | <td>The interval at which health checks are performed</td> |
| − | ! style="text-align: left; vertical-align: top;" | Health monitor ICMP host(s)
| + | </tr> |
| − | | style="text-align: left; vertical-align: top;" | ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; Default: "8.8.4.4"
| + | <tr> |
| − | | style="text-align: left; vertical-align: top;" | Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4)
| + | <td>Health monitor ICMP host(s)</td> |
| − | |-
| + | <td>ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; Default: '''8.8.4.4'''</td> |
| − | ! style="text-align: left; vertical-align: top;" | Health monitor ICMP timeout
| + | <td>Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4)</td> |
| − | | style="text-align: left; vertical-align: top;" | 1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec. {{!}}; Default: "3 sec."
| + | </tr> |
| − | | style="text-align: left; vertical-align: top;" | The frequency at which ICMP requests are to be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes)
| + | <tr> |
| − | |-
| + | <td>Health monitor ICMP timeout</td> |
| − | ! style="text-align: left; vertical-align: top;" | Attempts before failover
| + | <td>1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; Default: '''3 sec.'''</td> |
| − | | style="text-align: left; vertical-align: top;" | 1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20 {{!}}; Default: "3"
| + | <td>The frequency at which ICMP requests are to be sent. It is advised to set a higher value if your connection has high latency or high ji</td> |
| − | | style="text-align: left; vertical-align: top;" | The number of failed ping attempts after which the connection is to be declared as “down”
| + | </tr> |
| − | |-
| + | <tr> |
| − | ! style="text-align: left; vertical-align: top;" | Attempts before recovery
| + | <td>Attempts before failover</td> |
| − | | style="text-align: left; vertical-align: top;" | 1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20 {{!}}; Default: "3"
| + | <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; Default: '''3'''</td> |
| − | | style="text-align: left; vertical-align: top;" | The number of successful ping attempts after which the connection is to be declared as “up”
| + | <td>The number of failed ping attempts after which the connection is to be declared as “'''down'''” </td> |
| − | |-
| + | </tr> |
| − | |}
| + | <tr> |
| | + | <td>Attempts before recovery</td> |
| | + | <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; Default: '''3'''</td> |
| | + | <td>The number of successful ping attempts after which the connection is to be declared as “'''up'''”</td> |
| | + | </tr> |
| | + | </table> |
| | | | |
| | The majority of the options consist of timing and other important parameters that help determine the health of your primary connection. Regular health checks are constantly performed in the form of ICMP packets (Pings) on your primary connection. When the connections state starts to change (READY->NOT READY and vice versa) a necessary amount of failed or passed health checks has to be reached before the state changes completely. This delay is instituted so as to mitigate “spikes” in connection availability, but it also extends the time before the backup link can be brought up or down. | | The majority of the options consist of timing and other important parameters that help determine the health of your primary connection. Regular health checks are constantly performed in the form of ICMP packets (Pings) on your primary connection. When the connections state starts to change (READY->NOT READY and vice versa) a necessary amount of failed or passed health checks has to be reached before the state changes completely. This delay is instituted so as to mitigate “spikes” in connection availability, but it also extends the time before the backup link can be brought up or down. |
| | + | |
| | + | [[Category:RUT850 Network section]] |
