| Line 613: |
Line 613: |
| | ====Advanced Settings: DHCP==== | | ====Advanced Settings: DHCP==== |
| | ---- | | ---- |
| − | <b>Advanced Settings</b> information for <i>DHCP</i> protocol is provided in the table below. | + | <b>Advanced Settings</b> information for <b>DHCP</b> protocol is provided in the table below. |
| | | | |
| | [[File:Networking_rutos_manual_wan_configuration_advanced_settings_dhcp.png|border|class=tlt-border]] | | [[File:Networking_rutos_manual_wan_configuration_advanced_settings_dhcp.png|border|class=tlt-border]] |
| Line 681: |
Line 681: |
| | ====Advanced Settings: DHCPv6==== | | ====Advanced Settings: DHCPv6==== |
| | ---- | | ---- |
| − | <b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below. | + | <b>Advanced Settings</b> information for <b>DHCPv6</b> protocol is provided in the table below. |
| | | | |
| | [[File:Networking_rutos_manual_wan_configuration_advanced_settings_dhcpv6.png|border|class=tlt-border]] | | [[File:Networking_rutos_manual_wan_configuration_advanced_settings_dhcpv6.png|border|class=tlt-border]] |
| Line 739: |
Line 739: |
| | ====Advanced Settings: PPPoE==== | | ====Advanced Settings: PPPoE==== |
| | ---- | | ---- |
| − | <b>Advanced Settings</b> information for <i>PPPoE</i> protocol is provided in the table below. | + | <b>Advanced Settings</b> information for <b>PPPoE</b> protocol is provided in the table below. |
| | | | |
| | [[File:Networking_rutos_manual_wan_configuration_advanced_settings_pppoe.png|border|class=tlt-border]] | | [[File:Networking_rutos_manual_wan_configuration_advanced_settings_pppoe.png|border|class=tlt-border]] |
| Line 811: |
Line 811: |
| | </tr> | | </tr> |
| | </table> | | </table> |
| − | {{#ifeq: {{{mobile}}} | 1 |
| + | |
| | ====Advanced Settings: Mobile==== | | ====Advanced Settings: Mobile==== |
| | ---- | | ---- |
| − | <b>Advanced Settings</b> information for <i>Mobile</i> protocol is provided in the table below. | + | <b>Advanced Settings</b> information for <b>Mobile</b> protocol is provided in the table below. |
| | | | |
| | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v5.png|border|class=tlt-border]] | | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v5.png|border|class=tlt-border]] |
| Line 849: |
Line 849: |
| | <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td> | | <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td> |
| | </tr> | | </tr> |
| − | </table>|}} | + | </table> |
| | | | |
| | ===Physical Settings=== | | ===Physical Settings=== |
| Line 896: |
Line 896: |
| | </table> | | </table> |
| | | | |
| − | ====Advanced Settings: DHCP==== | + | ===Mobile Data Limit=== |
| | ---- | | ---- |
| − | <b>Advanced Settings</b> information for <i>DHCP</i> protocol is provided in the table below. | + | The <b>Mobile Data Limit</b> section provides you with the possibility to set data usage limits for your mobile network interfaces and data usage warnings via SMS message in order to protect yourself from unwanted data charges. |
| − | | |
| − | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_dhcp_v4.png|border|class=tlt-border]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>Field</th>
| |
| − | <th>Value</th>
| |
| − | <th>Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use built-in IPv6 management</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
| |
| − | <td>Specifies whether to enable prefix delegation.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Force link</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
| |
| − | <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use broadcast flag</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
| |
| − | <td>Required for certain ISPs. For example, Charter with DOCSIS 3.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use default gateway</td>
| |
| − | <td>off <nowiki>|</nowiki> 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>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>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use custom DNS servers</td>
| |
| − | <td>ip4; default: <b>none</b></td>
| |
| − | <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </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>
| |
| − | <td>Override MAC address</td>
| |
| − | <td>mac; default: <b>none</b></td>
| |
| − | <td>When set, uses a user-defined MAC address for the interface instead of the default one.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Override MTU</td>
| |
| − | <td>integer [1..9200]; default: <b>none</b></td>
| |
| − | <td>Changes the interfaces allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.<br>
| |
| − | <ul>
| |
| − | <li>'''Note:''' Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
| |
| − | <li>'''Note:''' Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
| |
| − | </ul></td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>IP4table</td>
| |
| − | <td>integer [0..99999999]; default: <b>none</b></td>
| |
| − | <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
| |
| − | </tr>
| |
| − | </table>
| |
| | | | |
| − | ====Advanced Settings: DHCPv6====
| + | <i>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to Mobile</b>.</i> |
| − | ----
| |
| − | <b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below. | |
| | | | |
| − | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_dhcpv6_v4.png|border|class=tlt-border]] | + | [[File:Networking_rutos_manual_interfaces_interface_configuration_mobile_mobile_data_limit_v2.png|border|class=tlt-border]] |
| | | | |
| | <table class="nd-mantable"> | | <table class="nd-mantable"> |
| | <tr> | | <tr> |
| | <th>Field</th> | | <th>Field</th> |
| − | <th>Value</th>
| + | <th>Value</th> |
| − | <th>Description</th>
| + | <th>Description</th> |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
| − | <td>Use built in IPv6-management</td>
| + | <td>Enable data connection limit</td> |
| − | <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Specifies whether to enable prefix delegation.</td>
| + | <td>Turns mobile data limitations on or off.</td> |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
| − | <td>Force link</td>
| + | <td>Data limit<span class="asterisk">*</span> (MB)</td> |
| − | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
| + | <td>integer; default: <b>1000</b></td> |
| − | <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
| + | <td>The amount of data that is allowed to be downloaded over the specified period of time. When the limit is reached, the device will no longer be able to establish a data connection until the period is over or the data limit is reset.</td> |
| − | </tr>
| |
| | <tr> | | <tr> |
| − | <td>Use default gateway</td>
| + | <td>Period</td> |
| − | <td>off <nowiki>|</nowiki> on; default: <b>on</b></td> | + | <td>Month <nowiki>|</nowiki> Week <nowiki>|</nowiki> Day; default: <b>Day</b></td> |
| − | <td>When checked, creates a default route for the interface.</td> | + | <td>Data limit period after which the data counter is reset on the specified <i>Start day</i>.</td> |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
| − | <td>Use custom DNS servers</td>
| + | <td>Start day <nowiki>|</nowiki> Start hour</td> |
| − | <td>ip4; default: <b>none</b></td> | + | <td>day [1..31] <nowiki>|</nowiki> day [Monday..Sunday] {{!}} hour [1..24]; default: <b>hour 0</b></td> |
| − | <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
| + | <td>Specifies when the period of counting data usage should begin. After the period is over, the limit is reset and the count begins over again.</td> |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
| − | <td>Custom delegated IPv6-prefix</span></td>
| + | <td>Enable SMS warning</td> |
| − | <td>ip6 prefix; default: <b>none</b></td>
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Uses an (additional) user-provided IPv6 prefix for distribution to clients.</td>
| + | <td>Turns SMS warning on or off. When turned on and configured, sends an SMS message to a specified number after the SIM card uses a specified amount of data.</td> |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
| − | <td>Client ID to send when requesting DHCP</td>
| + | <td>Data limit* (MB)</td> |
| − | <td>string; default: <b>none</b></td>
| + | <td>integer; default: <b>none</b></td> |
| − | <td>Client ID which will be sent when requesting a DHCP lease.</td>
| + | <td>The received data limit before sending an SMS warning. After reaching using the the amount of data specified in this field, the router will send an SMS warning message to the specified phone number.</td> |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
| − | <td>Override MAC address</td>
| + | <td>Phone number</td> |
| − | <td>mac; default: <b>none</b></td> | + | <td>phone number; default: <b>none</b></td> |
| − | <td>When set, uses a user-defined MAC address for the interface instead of the default one.</td> | + | <td>Recipient's phone numbers.</td> |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
| − | <td>Override MTU</td>
| + | <td>Data limit clear due</td> |
| − | <td>integer [1..9200]; default: <b>none</b></td>
| + | <td><b>none</b></td> |
| − | <td>Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.<br>
| + | <td>Display the date of the next automatic data limit clear.</td> |
| − | <ul>
| |
| − | <li>'''Note:''' Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
| |
| − | <li>'''Note:''' Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
| |
| − | </ul></td>
| |
| − | <tr>
| |
| − | <tr>
| |
| − | <td>IP4table</td>
| |
| − | <td>integer [0..99999999]; default: <b>none</b></td>
| |
| − | <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | | |
| − | ====Advanced Settings: PPPoE====
| |
| − | ----
| |
| − | <b>Advanced Settings</b> information for <i>PPPoE</i> protocol is provided in the table below.
| |
| − | | |
| − | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_pppoe_v5.png|border|class=tlt-border]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>Field</th>
| |
| − | <th>Value</th>
| |
| − | <th>Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use built-in IPv6 management</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
| |
| − | <td>Specifies whether to enable prefix delegation.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Force link</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
| |
| − | <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Obtain IPv6 address</td>
| |
| − | <td>Automatic <nowiki>|</nowiki> Disabled | Manual; default: <b>Automatic</b></td>
| |
| − | <td>Defines behaviour for obtaining an IPv6 address.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use default gateway</td>
| |
| − | <td>off <nowiki>|</nowiki> 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>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>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use custom DNS servers</td>
| |
| − | <td>ip4; default: <b>none</b></td>
| |
| − | <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>VLAN tag value</td>
| |
| − | <td>integer [0..7]; default: <b>none</b></td>
| |
| − | <td>VLAN tag value.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>VLAN priority</td>
| |
| − | <td>integer [0..4095]; default: <b>none</b></td>
| |
| − | <td>VLAN priority.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>LCP echo failure threshold</td>
| |
| − | <td>integer; default: <b>none</b></td>
| |
| − | <td>Presumes peer to be dead after given amount of LCP echo failures. Leave it at 0 to ignore failures.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>LCP echo interval</td>
| |
| − | <td>integer; default: <b>none</b></td>
| |
| − | <td>Sends LCP echo requests at the given interval in seconds. This function is only effective in conjunction with failure threshold.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Host-Uniq tag content</td>
| |
| − | <td>raw hex-encoded bytes; default: <b>none</b></td> | |
| − | <td>Leave empty unless your ISP require this.</td> | |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Inactivity timeout</td>
| |
| − | <td>mac; default: <b>none</b></td>
| |
| − | <td>Close inactive connection after the given amount of seconds. Leave it at 0 to persist connection.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Override MTU</td>
| |
| − | <td>integer [1..1500]; default: <b>none</b></td>
| |
| − | <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>IP4table</td>
| |
| − | <td>integer [0..99999999]; default: <b>none</b></td>
| |
| − | <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | {{#ifeq: {{{mobile}}} | 1 |
| |
| − | ====Advanced Settings: Mobile====
| |
| − | ----
| |
| − | <b>Advanced Settings</b> information for <i>Mobile</i> protocol is provided in the table below.
| |
| − | | |
| − | [[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v5.png|border|class=tlt-border]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>Field</th>
| |
| − | <th>Value</th>
| |
| − | <th>Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use built in IPv6-management</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
| |
| − | <td>Specifies whether to enable prefix delegation.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Force link</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
| |
| − | <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use custom DNS servers</td>
| |
| − | <td>ip4; default: <b>none</b></td>
| |
| − | <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Use gateway metric</td>
| |
| − | <td>integer; 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>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Override MTU</td>
| |
| − | <td>integer [1..9200]; default: <b>none</b></td>
| |
| − | <td>Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>IP4table</td>
| |
| − | <td>integer [0..99999999]; default: <b>none</b></td>
| |
| − | <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
| |
| − | </tr>
| |
| − | </table>|}}
| |
| − | | |
| − | ===Physical Settings===
| |
| − | ----
| |
| − | The <b>Physical Settings</b> section is used to create associations with physical interfaces and bridge network interfaces.
| |
| − | | |
| − | [[File:Networking_rutos_manual_interfaces_interface_configuration_physical_settings_v2.png|border|class=tlt-border]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>Field</th>
| |
| − | <th>Value</th>
| |
| − | <th>Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Bridge interfaces</td>
| |
| − | <td>off <nowiki>|</nowiki> <span style="color: #1550bf; font-weight: bold;">on</span>; default: <b>on</b></td>
| |
| − | <td>Bridges physical interfaces specified in this configuration.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable STP</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
| |
| − | <td>Turns the use of Spanning Tree Protocol (STP) for this interface on or off.<br><b>Note:</b> this field becomes visible when 'Bridge interfaces' is set to <i>on</i>.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable IGMP</td>
| |
| − | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
| |
| − | <td>Enabless IGMP snooping on this bridge.<br><b>Note:</b> this field becomes visible when 'Bridge interfaces' is set to <i>on</i> and 'Protocol' is set to <i>PPPoE</i>.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Interface</td>
| |
| − | <td>network interface(s); default: <b>none</b></td>
| |
| − | <td>Ties this network interface to physical device interfaces such as Ethernet {{#ifeq:{{{wifi}}}|1| or WiFi radios|}}.</td>
| |
| − | </tr>{{#ifeq: {{{name}}}| RUTXR1 |
| |
| − | <tr>
| |
| − | <td>Port priority</td>
| |
| − | <td>Ethernet<nowiki>|</nowiki>SFP default: <b>SFP</b></td>
| |
| − | <td>Port priority option allows to change physical port priority (SFP or Ethernet). This option is uniform between all eth1 interfaces.<br><b>Note:</b> this field becomes visible when 'Interface' is set to <i>eth1</i>.</td>
| |
| − | </tr>|}}
| |
| − | </table>
| |
| − | | |
| − | ===Firewall Settings===
| |
| − | ----
| |
| − | The <b>Firewall Settings</b> section is used to specify to which firewall zone if any this interface belongs. Assigning an interface to a zone may provide easier configuration of firewall rules. For example, instead of configuring separate rules for each WAN interface, you can add all WAN interfaces into a single firewall zone and make the rule apply to that zone instead.
| |
| − | | |
| − | More firewall zone settings can be configured from the Network → Firewall → General Settings → [[{{{name}}}_Firewall#Zones|Zones]] section.
| |
| − | | |
| − | [[File:Networking_rutos_manual_interfaces_interface_configuration_firewall_settings.png|border|class=tlt-border]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>Field</th>
| |
| − | <th>Value</th>
| |
| − | <th>Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Create / Assign firewall-zone</td>
| |
| − | <td>firewall zone; default: <b>none</b></td>
| |
| − | <td>Assigns this interface to the specified firewall zone.</td>
| |
| | </tr> | | </tr> |
| | </table> | | </table> |
| | | | |
| | + | <font size="-1"><i><span class="asterisk">*</span>Your carrier's data usage accounting may differ. Teltonika is not liable should any accounting discrepancies occur.</i></font> |
| | | | |
| | [[Category:{{{name}}} Network section]] | | [[Category:{{{name}}} Network section]] |
