Changes

14,710 bytes added , 12:08, 24 October 2023

m

Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}"

Line 1: Line 1: −

+

{{Template: Networking_device_manual_fw_disclosure

−

{{Template:~~Networking_rutos_manual_fw_disclosure~~

+

| series = {{{series}}}

−

| ~~fw_version~~ = {{{series}}}~~_R_00.02.03~~

+

| name = {{{name}}}

−

| series = {{{series}}}

+

| fw_version ={{Template: Networking_device_manual_latest_fw

+

| series = {{{series}}}

+

| name = {{{name}}}

+

}}

Line 9: Line 12:

The Interfaces page is used to to set up network interfaces.

−

This manual page provides an overview of the ~~Users windows~~ in {{{name}}} devices.

+

This manual page provides an overview of the Interfaces page in {{{name}}} devices.

−

{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer}}

+

{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer

+

| series = {{{series}}}

+

}}

==Network Interfaces==

Line 17: Line 22:

The Network Interfaces section displays interfaces currently existing on this device.

−

{{#ifeq: {{{series}}} | ~~RUTX~~

+

{{#ifeq: {{{series}}} | TCR1 | [[File:Networking_rutos_manual_tcr1_interfaces_network_interfaces_v1.png|border|class=tlt-border]] |

−

| [[File:~~Networking_rutos_manual_interfaces_network_interfaces_modem_{{{modem}}}_v1~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_{{{lan}}}_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}_v1{{#ifeq:{{{series}}}|TRB5|_trb5|}}.png|border|class=tlt-border]]|}}

−

| [[File:~~Networking_~~{{lc:{{{series}}}}}~~_manual_interfaces_network_interfaces_v1~~.png|border|class=tlt-border]]

−

}}

==Add Interface==

Line 26: Line 29:

The Add Interface section is used to create additional network interfaces. To create a new interface, simply enter a custom name for it and click the 'Add' button.

−

[[File:~~Networking_rutos_manual_interfaces_add_interface_v1~~.png|border|class=tlt-border]]

+

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

==Interface configuration==

−

This section provides information on network interface configuration. There are {{{no_of_if}}} ~~major~~ types of interfaces on the device:

+

This section provides information on network interface configuration. There are {{{no_of_if}}} main types of interfaces on the device:

<ul>

<li>Ethernet LAN</li>

−

{{#ifeq: {{{~~eth~~}}} | 1

+

{{#ifeq: {{{wired}}} | 1 | <li>Ethernet WAN</li>|}}

−

|<li>Ethernet WAN</li>

+

{{#ifeq: {{{mobile}}} | 1 | <li>Mobile WAN</li>|}}

−

|~~</ul>~~

−

}}

−

{{#ifeq: {{{~~modem~~}}} | 1

−

|<li>Mobile WAN</li>

−

|~~</ul>~~

−

}}

</ul>

−

~~Each type utilizes generally utilizes these interface~~ protocols:

+

Different types of interfaces can be configured under different protocols:

<tr>

−

<th width="16%" style="text-align: center;">~~</th>~~

+

−

~~<th width="14%" style="text-align: center;">None~~</th>

<th width="14%" style="text-align: center;">Static</th>

<th width="14%" style="text-align: center;">DHCPv6</th>

<th width="14%" style="text-align: center;">PPPoE</th>

−

<th width="14%" style="text-align: center;">Mobile</th>

+

{{#ifeq:{{{mobile}}}|1|<th width="14%" style="text-align: center;">Mobile</th>|}}

</tr>

<tr>

<td style="text-align: left; font-weight: bold;">Ethernet LAN</td>

<td>[[File:Blue_check_mark.png|center|15px]]</td>

−

~~<td>[[File:Blue_check_mark.png|center|15px]]</td>~~

−

~~<td></td>~~

+

{{#ifeq:{{{mobile}}}|1|<td></td>|}}

</tr>

−

{{#ifeq: {{{~~eth~~}}} | 1

+

{{#ifeq: {{{wired}}} | 1

| <tr>

<td style="text-align: left; font-weight: bold;">Ethernet WAN</td>

−

~~<td></td>~~

<td>[[File:Blue_check_mark.png|center|15px]]</td>

−

+

{{#ifeq:{{{mobile}}}|1|<td></td>|}}

</tr>

|

}}

−

{{#ifeq: {{{~~modem~~}}} | 1

+

{{#ifeq: {{{mobile}}} | 1

| <tr>

<td style="text-align: left; font-weight: bold;">Mobile WAN</td>

−

~~<td></td>~~

Line 93: Line 86:

To begin configuring an interface, click the 'Edit' button on the right side of the interface:

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_begin_to_edit_v1~~.png]]

+

[[File:Networking_rutos_manual_interfaces_network_interfaces_edit_button_lan_{{{lan}}}{{#ifeq:{{{series}}}|TRB5|_trb5|}}.png]]

−

~~===Interfaces: if_name===~~

−

~~----~~

−

~~This section covers all parameters directly related to a network interface.~~

−

====General Setup====

+

===General Setup===

----

−

The General Setup section is used to configure the protocol and all the different parameters that go along with each protocol. ~~This section~~ is different for each protocol.

+

The General Setup section is used to configure the protocol of an interface and all the different parameters that go along with each protocol. If None protocol is chosen, all other interface settings will be ignored. The following sections are different for each protocol.

−

=====General Setup: Static=====

+

====General Setup: Static====

----

The static protocol uses a predefined manual configuration instead of obtaining parameters automatically via a DHCP lease.

−

~~{{#ifeq~~: {{{~~series~~}}} ~~| TRB14X~~

+

[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_static_ip_lan_{{{lan}}}.png|border|class=tlt-border]]

−

~~| [[File:Networking_trb14x_manual_interfaces_network_interfaces_lan_general_setup_static_ip_v1.png|border|class=tlt-border]]~~

−

~~| [[File:Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_static_ip_v1~~.png|border|class=tlt-border]]

−

}}

Line 120: Line 106:

<tr>

<td>IPv4 address</td>

−

<td>ip4; default[for LAN]: 192.168.1.1</td>

+

<td>ip4; default[for LAN]: {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.1|#default=192.168.1.1}}</td>

<td>The IPv4 address interface of this interface. An IP address identifies a device on a network and allows it to communicate with other devices.</td>

</tr>

Line 145: Line 131:

</table>

−

=====General Setup: DHCP=====

+

====General Setup: DHCP====

----

The DHCP protocol is used to set up an interface which obtains its configuration parameters automatically via a DHCP lease.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_dhcp_v1~~.png|border|class=tlt-border]]

+

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

Line 164: Line 150:

</table>

−

=====General Setup: DHCPv6=====

+

====General Setup: DHCPv6====

----

The DHCPv6 protocol is used to set up an IPv6 interface which obtains its configuration parameters automatically via a DHCP lease.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_dhcpv6_v1~~.png|border|class=tlt-border]]

+

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

Line 188: Line 174:

</table>

−

=====General Setup: PPPoE=====

+

====General Setup: PPPoE====

----

−

The PPPoE protocol is used to set up a PPP (Point-to-Point Protocol) connection over the Ethernet port{{#ifeq:{{{series}}}|~~RUTX|.~~| (in this case: an Ethernet connection simulated over the USB port)}}.

+

The PPPoE protocol is used to set up a PPP (Point-to-Point Protocol) connection over the Ethernet port{{#ifeq:{{{series}}}|TRB1| (in this case: an Ethernet connection simulated over the USB port)|}}.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_pppoe_v1~~.png|border|class=tlt-border]]

+

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

Line 221: Line 207:

</tr>

</table>

−

{{#ifeq: {{{~~modem~~}}} | 1 |

+

{{#ifeq: {{{mobile}}} | 1 |

−

=====General Setup: Mobile=====

+

====General Setup: Mobile====

----

The Mobile protocol is used to set up an interface which can establish a mobile WAN connection.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_mobile_v1~~.png|border|class=tlt-border]]

+

=====Mode: NAT=====

+

----

+

[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

+

<td>NAT <nowiki>|</nowiki> Bridge <nowiki>|</nowiki> Passthrough; default: NAT</td>

+

<td>Mobile connection operating mode.

+

<ul>

+

<li>NAT - the mobile connection uses NAT (network address translation).</li>

+

<li>Bridge - bridges the LTE data connection with LAN. The device assigns its WAN IP address to another device (first connected to LAN or specified with MAC address). Using Bridge mode will disable most of the device’s capabilities.</li>

+

<li>Passthrough - in this mode the {{{name}}} shares its WAN IP to a single LAN device (first connected to LAN or specified with MAC address). The LAN device will get WAN IP of {{{name}}} instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.</li>

+

</ul>

+

</td>

+

<tr>

+

+

<td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: IPv4</td>

+

<td>Specifies what of address will be requested from the operator.</td>

+

</tr>

+

</tr>{{#ifeq: {{{dualsim}}} | 1 | {{#ifeq: {{{dualmodem}}} | 1 ||

+

<tr>

+

+

<td>SIM1 <nowiki>|</nowiki> SIM2; default: SIM1</td>

+

<td>Selects which SIM slot will be used for this interface.</td>

+

</tr>}}|}}{{#ifeq: {{{dualmodem}}} | 1 |

+

<tr>

+

<td>Modem</td>

+

<td>Primary modem <nowiki>|</nowiki> Secondary modem; default: Primary modem</td>

+

<td>Selects which modem will be used for this interface.</td>

+

</tr>|}}

+

<tr>

+

+

<td>off <nowiki>|</nowiki> on; default: on</td>

+

<td>The Auto APN feature scans an internal Android APN database and selects an APN based on the SIM card's operator and country. If the first automatically selected APN doesn't work, it attempts to use the next existing APN from the database.

+

</td>

+

</tr>

+

<tr>

+

<td>APN / Custom APN</td>

+

<td>string; default: none</td>

+

<td>An Access Point Name (APN) is a gateway between a GSM, GPRS, 3G or 4G mobile network and another computer network. Depending on the contract, some operators may require you to use an APN just to complete the registration on a network. In other cases, APN is used to get special parameters from the operator (e.g., a [[Private_and_Public_IP_Addresses#Public_IP_address|public IP address]]) depending on the contract. An APN Network Identifier cannot start with any of the following strings:

+

<ul>

+

+

+

+

+

</ul>it cannot end in:

+

<ul>

+

+

</ul>and it cannot contain the asterisk symbol (*).

+

</td>

+

</tr>

+

<tr>

+

<td>Authentication Type</td>

+

<td>NONE <nowiki>|</nowiki> PAP <nowiki>|</nowiki> CHAP; default: NONE</td>

+

<td>Authentication method that your GSM carrier uses to authenticate new connections on its network. If you select PAP or CHAP, you will also be required to enter a username and password.</td>

+

</tr>

+

</table>

+

=====Mode: Passthrough=====

+

----

+

[[File:Networking_rutos_manual_interfaces_interface_configuration_general_mobile_passthrough_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]

Line 236: Line 288:

<tr>

−

<td>NAT <nowiki>|</nowiki> Bridge<~~span class="asterisk"~~>*</~~span~~>; default: NAT</td>

+

<td>NAT <nowiki>|</nowiki> Bridge <nowiki>|</nowiki> Passthrough; default: NAT</td>

<td>Mobile connection operating mode.

<ul>

<li>NAT - the mobile connection uses NAT (network address translation).</li>

−

<li~~>Bridge</b~~></span~~> - bridges the LTE data connection with LAN. ~~In this mode the~~ device ~~relay the~~ IP address ~~received from the ISP~~ to another ~~LAN~~ device (~~e.g., computer~~). Using Bridge mode will disable most of the device’s capabilities ~~and you will only be able~~ to ~~access your~~ device~~'s WebUI~~ with ~~a [[Setting_up_a_Static_IP_address_on_a_Windows_10_PC|static~~ IP ~~configuration]].</li>

+

<li>Bridge - bridges the LTE data connection with LAN. The device assigns its WAN IP address to another device (first connected to LAN or specified with MAC address). Using Bridge mode will disable most of the device’s capabilities.</li>

+

<li>Passthrough - in this mode the {{{name}}} shares its WAN IP to a single LAN device (first connected to LAN or specified with MAC address). The LAN device will get WAN IP of {{{name}}} instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.</li>

</ul>

</td>

+

<tr>

+

<td>Subnet selection</td>

+

<td>Auto {{!}} P2P; default: Auto</td>

+

<td>Subnet selection method.</td>

</tr>

−

~~{{#ifeq: {{{series}}} | TRB14X~~

+

<tr>

−

|

−

| <tr>

<td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: IPv4</td>

<td>Specifies what of address will be requested from the operator.</td>

</tr>

+

</tr>{{#ifeq: {{{dualsim}}} | 1 | {{#ifeq: {{{dualmodem}}} | 1 ||

<tr>

+

<td>SIM1 <nowiki>|</nowiki> SIM2; default: SIM1</td>

+

<td>Selects which SIM slot will be used for this interface.</td>

+

</tr>}}|}}{{#ifeq: {{{dualmodem}}} | 1 |

+

<tr>

+

<td>Modem</td>

+

<td>Primary modem <nowiki>|</nowiki> Secondary modem; default: Primary modem</td>

+

<td>Selects which modem will be used for this interface.</td>

+

</tr>|}}

+

<tr>

+

<td>off <nowiki>|</nowiki> on; default: on</td>

−

<td>The Auto APN feature scans an internal Android APN database and selects an APN based on the SIM card's operator and country. If the first automatically selected APN doesn't work, it attempts to use the next existing APN from the database.</td>

+

<td>The Auto APN feature scans an internal Android APN database and selects an APN based on the SIM card's operator and country. If the first automatically selected APN doesn't work, it attempts to use the next existing APN from the database.

−

</tr>}}

+

</td>

+

</tr>

+

<tr>

+

<td>APN / Custom APN</td>

+

<td>string; default: none</td>

+

<td>An Access Point Name (APN) is a gateway between a GSM, GPRS, 3G or 4G mobile network and another computer network. Depending on the contract, some operators may require you to use an APN just to complete the registration on a network. In other cases, APN is used to get special parameters from the operator (e.g., a [[Private_and_Public_IP_Addresses#Public_IP_address|public IP address]]) depending on the contract. An APN Network Identifier cannot start with any of the following strings:

+

<ul>

+

+

+

+

+

</ul>it cannot end in:

+

<ul>

+

+

</ul>and it cannot contain the asterisk symbol (*).

+

</td>

+

</tr>

+

<tr>

+

<td>Authentication Type</td>

+

<td>NONE <nowiki>|</nowiki> PAP <nowiki>|</nowiki> CHAP; default: NONE</td>

+

<td>Authentication method that your GSM carrier uses to authenticate new connections on its network. If you select PAP or CHAP, you will also be required to enter a username and password.</td>

+

</tr>

+

<tr>

+

<td>Disable DHCP</td>

+

<td>on <nowiki>|</nowiki> off; default: on</td>

+

<td>Disables dynamic allocation of client addresses when toggled off</td>

+

</tr>

+

<tr>

+

<td>Lease Time</td>

+

<td>integer; default: 1</td>

+

<td>Expiry time of leased address. The minimum value for hours is 1, the minimum value for minutes is 2 and the minimum value for seconds is 120</td>

+

</tr>

+

<tr>

+

<td>Units</td>

+

<td>Hours <nowiki>|</nowiki> Minutes <nowiki>|</nowiki> Second; default: Hours</td>

+

<td>Specifies the time measurement unit</td>

+

</tr>

+

<tr>

+

<td>MAC Address</td>

+

<td>mac; default: none</td>

+

<td>Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge or Passthrough mode. Note: this field only becomes visible when using Bridge or Passthrough mode.</td>

+

</tr>

+

</table>

+

=====Mode: Bridge=====

+

----

+

[[File:Networking_rutos_manual_interfaces_interface_configuration_general_mobile_bridge_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

+

<td>NAT {{!}} Bridge {{!}} Passthrough; default: NAT</td>

+

<td>Mobile connection operating mode.

+

<ul>

+

<li>NAT - the mobile connection uses NAT (network address translation).</li>

+

<li>Bridge - bridges the LTE data connection with LAN. The device assigns its WAN IP address to another device (first connected to LAN or specified with MAC address). Using Bridge mode will disable most of the device’s capabilities.</li>

+

<li>Passthrough - in this mode the {{{name}}} shares its WAN IP to a single LAN device (first connected to LAN or specified with MAC address). The LAN device will get WAN IP of {{{name}}} instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.</li>

+

</ul>

+

</td>

+

<tr>

+

<td>Subnet selection</td>

+

<td>Auto {{!}} P2P; default: Auto</td>

+

<td>Subnet selection method.</td>

+

</tr>

+

<tr>

+

+

<td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: IPv4</td>

+

<td>Specifies what of address will be requested from the operator.</td>

+

</tr>{{#ifeq: {{{dualsim}}} | 1 | {{#ifeq: {{{dualmodem}}} | 1 ||

+

<tr>

+

+

<td>SIM1 <nowiki>|</nowiki> SIM2; default: SIM1</td>

+

<td>Selects which SIM slot will be used for this interface.</td>

+

</tr>}}|}}{{#ifeq: {{{dualmodem}}} | 1 |

+

<tr>

+

<td>Modem</td>

+

<td>Primary modem <nowiki>|</nowiki> Secondary modem; default: Primary modem</td>

+

<td>Selects which modem will be used for this interface.</td>

+

</tr>|}}

<tr>

Line 283: Line 432:

</tr>

<tr>

−

<td~~>MAC Address~~</td>

+

<td>MAC Address</td>

<td>mac; default: none</td>

−

<td>Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge mode. Note: this field only becomes visible when using Bridge mode.</td>

+

<td>Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge or Passthrough mode. Note: this field only becomes visible when using Bridge or Passthrough mode.</td>

</tr>

</table>

−

~~~~

−

* In Bridge mode the device assigns its WAN IP address to another device (identified by its MAC address}. It is used instead of Network Address Translation (NAT) in order to make this device "transparent" in the communication process.

−

~~Important~~: using ~~Bridge mode will disable most of the device’s other capabilities~~.

+

{{#switch: {{{series}}}

−

~~~~

+

| TRB1|TRB5|RUT36X =

+

| TRB2 =

+

{{#ifeq: {{{name}}} | TRB245 |

+

=====Multi-APN=====

+

----

+

{{{name}}} supports Multiple PDN feature in order to establish connections to multiple mobile networks using a single SIM card. You can find a configuration example [[Multi-APN|here]].}}

+

| #default =

+

=====Multi-APN=====

+

----

+

{{{name}}} supports Multiple PDN feature in order to establish connections to multiple mobile networks using a single SIM card. You can find a configuration example [[Multi-APN|here]].

+

}}

|}}

−

====Advanced Settings====

+

===Advanced Settings===

----

The Advanced Settings section is used to set up some of the more specific and less frequently used interface parameters. This section is different for each protocol.

−

=====Advanced Settings: Static=====

+

====Advanced Settings: Static====

----

Advanced Settings information for Static protocol is provided in the table below.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_static_v1~~.png|border|class=tlt-border]]

+

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

Line 310: Line 469:

<th>Value</th>

<th>Description</th>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Bring up on boot</td>~~

−

~~<td>off | on; default: on</td>~~

−

~~<td>Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.</td>~~

</tr>

<tr>

Line 325: Line 479:

<td>off | on; default: on</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 gateway metric</td>

+

<td>integer; default: 3</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 MAC address</td>

<td>mac; default: none</td>

−

<td>When set, uses a user-defined MAC address for the interface.</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: none</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>

+

<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.

+

<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>~~Use gateway metric~~</td>

+

<td>IP4table</td>

−

<td>integer; default: none</td>

+

<td>integer [0..99999999]; default: none</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>

<td>IPv6 assignment length</td>

−

<td>integer [0..64] | ~~disabled~~; default: 60</td>

+

<td>integer [0..64] | Disabled; default: Disabled</td>

<td>Delegates a prefix of given length to the interface.</td>

</tr>

<tr>

−

<td>IPv6 address</td>

+

<td>IPv6 address</td>

<td>ip6; default: none</td>

−

<td>The interface's IPv6 address. An IP address identifies a device on a network and allows it to communicate with other devices~~. NOTE: this field only becomes visible when IPv6 assignment length is set to disabled~~. Note: this field only becomes visible when IPv6 assignment length is set to disabled</td>

+

<td>The interface's IPv6 address. An IP address identifies a device on a network and allows it to communicate with other devices. Note: this field only becomes visible when IPv6 assignment length is set to disabled</td>

</tr>

<tr>

−

<td>IPv6 gateway</td>

+

<td>IPv6 gateway</td>

<td>ip6; default: none</td>

<td>IPv6 prefix routed here for use on other interfaces. Note: this field only becomes visible when IPv6 assignment length is set to disabled.</td>

</tr>

<tr>

−

<td>IPv6 routed prefix</td>

+

<td>IPv6 routed prefix</td>

<td>ip6; default: none</td>

<td>IPv6 prefix routed here for use on other interfaces. Note: this field only becomes visible when IPv6 assignment length is set to disabled.</td>

Line 364: Line 528:

<td>IPv6 assignment hint</td>

<td>string; default: none</td>

−

<td>~~The subprefix-~~ID ~~that should~~ be ~~delegated as hexadecimal number~~.</td>

+

<td>Subprefix ID to be used if available (e.g., the value 1234 with an IPv6 assignment length of 64 will assign prefixes of the form …:1234::/64 or given LAN ports, LAN & LAN2, and a prefix delegation of /56, use IPv6 assignment hint of 00 and 80 which would give prefixes of LAN …:xx00::/64 and LAN2 …:xx80::/64)</td>

</tr>

<tr>

Line 371: Line 535:

<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>

+

-->

</table>

−

=====Advanced Settings: DHCP=====

+

====Advanced Settings: DHCP====

----

Advanced Settings information for DHCP protocol is provided in the table below.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_dhcp_v1~~.png|border|class=tlt-border]]

+

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

Line 384: Line 549:

<th>Value</th>

<th>Description</th>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Bring up on boot</td>~~

−

~~<td>off | on; default: on</td>~~

−

~~<td>Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.</td>~~

</tr>

<tr>

Line 409: Line 569:

<td>off | on; default: on</td>

<td>When checked, creates a default route for the interface.</td>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Use DNS servers advertised by peer</td>~~

−

~~<td>off | on; default: on</td>~~

−

~~<td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>~~

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Use custom DNS servers</td>~~

−

~~<td>off | on; default: on</td>~~

−

~~<td>Specifies whether to use DNS servers obtained automatically or specified manually. Note: this field only becomes visible when Use DNS servers advertised by peer is set to off</td>~~

</tr>

<tr>

Line 424: Line 574:

<td>integer; default: none</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: none</td>

+

<td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>

</tr>

<tr>

Line 438: Line 593:

<td>Override MAC address</td>

<td>mac; default: none</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 device). 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>

+

<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: none</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.</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.

+

<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: none</td>

+

<td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>

</tr>

</table>

−

=====Advanced Settings: DHCPv6=====

+

====Advanced Settings: DHCPv6====

----

Advanced Settings information for DHCPv6 protocol is provided in the table below.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_dhcpv6_v1~~.png|border|class=tlt-border]]

+

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

Line 458: Line 622:

<th>Value</th>

<th>Description</th>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Bring up on boot</td>~~

−

~~<td>off | on; default: on</td>~~

−

~~<td>Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.</td>~~

</tr>

<tr>

Line 480: Line 639:

</tr>

<tr>

−

<td>Use DNS servers ~~advertised by peer~~</td>

+

<td>Use custom DNS servers</td>

−

<td>~~off | on~~; default: on</td>

+

<td>ip4; default: none</td>

−

<td>Specifies ~~whether to use DNS servers obtained automatically or specified manually.</td>~~

+

<td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Use~~ custom DNS servers~~</td>~~

−

~~<td>off | on; default: on</td>~~

−

~~<td>Specifies whether to use DNS servers obtained automatically or specified manually~~.~~ Note: this field only becomes visible when Use~~ DNS servers advertised by peer ~~is set to off~~</td>

</tr>

<tr>

Line 502: Line 656:

<td>Override MAC address</td>

<td>mac; default: none</td>

−

<td>When set, uses a user-defined MAC address for the interface.</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: none</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>

+

<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.

+

<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>

+

<td>IP4table</td>

+

<td>integer [0..99999999]; default: none</td>

+

<td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>

+

</tr>

</table>

−

=====Advanced Settings: PPPoE=====

+

====Advanced Settings: PPPoE====

----

Advanced Settings information for PPPoE protocol is provided in the table below.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_pppoe_v1~~.png|border|class=tlt-border]]

+

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

Line 522: Line 685:

<th>Value</th>

<th>Description</th>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Bring up on boot</td>~~

−

~~<td>off | on; default: on</td>~~

−

~~<td>Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.</td>~~

</tr>

<tr>

Line 541: Line 699:

<td>Obtain IPv6 address</td>

<td>Automatic | Disabled | Manual; default: Automatic</td>

−

+

<td>Defines behaviour for obtaining an IPv6 address.</td>

</tr>

<tr>

Line 554: Line 712:

</tr>

<tr>

−

<td>Use DNS servers advertised by peer</td>

+

<td>Use custom DNS servers</td>

−

<td><~~span style="color: red;"~~>~~off~~<~~/span~~> ~~| on~~; default: on</td>

+

<td>ip4; default: none</td>

−

<td>~~Specifies whether to use DNS servers obtained automatically or specified manually~~.</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: none</td>

+

<td>VLAN tag value.</td>

</tr>

<tr>

−

<td>~~Use custom DNS servers~~</td>

+

<td>VLAN priority</td>

−

<td>~~off | on~~; default: on</td>

+

<td>integer [0..4095]; default: none</td>

−

<td>~~Specifies whether to use DNS servers obtained automatically or specified manually~~.~~ Note: this field only becomes visible when Use DNS servers advertised by peer is set to off~~</td>

+

<td>VLAN priority.</td>

</tr>

<tr>

Line 587: Line 750:

<td>integer [1..1500]; default: none</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: none</td>

+

<td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>

</tr>

</table>

−

{{#ifeq: {{{~~modem~~}}} | 1 |

+

{{#ifeq: {{{mobile}}} | 1 |

−

=====Advanced Settings: Mobile=====

+

====Advanced Settings: Mobile====

----

Advanced Settings information for Mobile protocol is provided in the table below.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_mobile_v1~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v5.png|border|class=tlt-border]]

Line 601: Line 769:

<th>Value</th>

<th>Description</th>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Bring up on boot</td>~~

−

~~<td>off <nowiki>|</nowiki> on; default: on</td>~~

−

~~<td>Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.</td>~~

</tr>

<tr>

Line 618: Line 781:

</tr>

<tr>

−

<td>Use DNS servers ~~advertised by peer~~</td>

+

<td>Use custom DNS servers</td>

−

<td>~~off <nowiki>|</nowiki> on~~; default: on</td>

+

<td>ip4; default: none</td>

−

<td>Specifies ~~whether to use DNS servers obtained automatically or specified manually.</td>~~

+

<td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Use~~ custom DNS servers~~</td>~~

−

~~<td>off <nowiki>|</nowiki> on; default: on</td>~~

−

~~<td>Specifies whether to use DNS servers obtained automatically or specified manually~~.~~ Note: this field only becomes visible when Use~~ DNS servers advertised by peer ~~is set to off~~</td>

</tr>

<tr>

Line 636: Line 794:

<td>integer [1..9200]; default: none</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: none</td>

+

<td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>

</tr>

</table>|}}

−

====Physical Settings====

+

===Physical Settings===

----

The Physical Settings section is used to create associations with physical interfaces and bridge network interfaces.

−

~~{{#ifeq: {{{series}}} | TRB14x~~

+

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

−

~~| [[File:Networking_trb14x_manual_interfaces_network_interfaces_lan_physical_settings_v1.png|border|class=tlt-border]]~~

+

−

| [[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_physical_settings_wifi_{{{wifi}}}_v1~~.png|border|class=tlt-border]]

−

}}

<tr>

Line 654: Line 816:

<tr>

<td>Bridge interfaces</td>

−

<td>off | on; default: on</td>

+

<td>off | on; default: on</td>

<td>Bridges physical interfaces specified in this configuration.</td>

</tr>

Line 660: Line 822:

<td>Enable STP</td>

<td>off | on; default: off</td>

−

<td>Turns the use of Spanning Tree Protocol (STP) for this interface on or off.</td>

+

<td>Turns the use of Spanning Tree Protocol (STP) for this interface on or off. Note: this field becomes visible when 'Bridge interfaces' is set to on.</td>

+

</tr>

+

<tr>

+

<td>Enable IGMP</td>

+

<td>off | on; default: off</td>

+

<td>Enabless IGMP snooping on this bridge. Note: this field becomes visible when 'Bridge interfaces' is set to on and 'Protocol' is set to PPPoE.</td>

</tr>

<tr>

<td>Interface</td>

−

<td>network interface(s); default: {{#ifeq:{{{~~series~~}}}|~~TRB14X~~|~~rndis0~~|~~eth0~~}}{{#ifeq:{{{~~wifi~~}}}|1| ~~wlan0 wlan1~~|}}</td>

+

<td>network interface(s); default: none</td>

−

<td>~~Ties this network interface~~ to physical ~~device~~ interfaces ~~such as Ethernet{{#ifeq~~:~~{{{wifi}}}|1| or WiFi radios|}}~~.</td>

+

<td>Ties this network interface to physical device interfaces such as Ethernet {{#ifeq:{{{wifi}}}|1| or WiFi radios|}}.</td>

−

</tr>

+

</tr>{{#ifeq: {{{name}}}| RUTXR1 |

+

<tr>

+

<td>Port priority</td>

+

<td>Ethernet<nowiki>|</nowiki>SFP default: SFP</td>

+

<td>Port priority option allows to change physical port priority (SFP or Ethernet). This option is uniform between all eth1 interfaces. Note: this field becomes visible when 'Interface' is set to eth1.</td>

+

</tr>|}}

</table>

−

====Firewall Settings====

+

===Firewall Settings===

----

−

The Firewall Settings section is used to specify to which firewall zone if any this interface belongs.

+

The Firewall Settings 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_network_interfaces_lan_firewall_settings_v1~~.png|border|class=tlt-border]]

+

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

Line 683: Line 857:

<tr>

<td>Create / Assign firewall-zone</td>

−

<td>firewall zone; default: ~~lan~~</td>

+

<td>firewall zone; default: none</td>

<td>Assigns this interface to the specified firewall zone.</td>

</tr>

Line 694: Line 868:

[[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]]

−

~~In order to view~~ the DHCP ~~server configuration~~, ~~the interface~~ protocol ~~must be set~~ to ~~~~Static~~~~</i~~>.</u~~>

+

To make the DHCP Server section visible, set interface protocol to Static.

====DHCP Server: General Setup====

Line 700: Line 874:

The General Setup section is used to set up the main operating parameters of the DHCP server.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_general_setup_v1~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_general_setup_lan_{{{lan}}}_v1.png|border|class=tlt-border]]

Line 714: Line 888:

</tr>

<tr>

−

<td>Start</td>

+

<td>Start IP</td>

−

<td>~~integer [1..255]~~; default: 100</td>

+

<td>ip4; default: {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.100|#default=192.168.1.100}}</td>

−

<td>The starting IP address ~~value~~. e.g., if your device’s LAN IP is 192.168.1.1 and your subnet mask is 255.255.255.0 that means that in your network a valid IP address has to be in the range of [192.168.1.0..192.168.1.254] (192.168.1.255 is a special unavailable address). If the ~~Start~~ value ~~is set~~ to ~~100 then the DHCP server will only lease out addresses starting from 192.168.1.100~~.</td>

+

<td>The starting IP address of the DHCP server IP address range. E.g., if your device’s LAN IP is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.1|#default=192.168.1.1}} and your subnet mask is 255.255.255.0 that means that in your network a valid IP address has to be in the range of [{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.0|#default=192.168.1.0}}..{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.254|#default=192.168.1.254}}] ({{#switch:{{{series}}}|TRB1|TRB5=192.168.2.255|#default=192.168.1.255}} is a special unavailable address). If the subnet of your LAN IP address changes, this value needs to be changed accordingly.</td>

</tr>

<tr>

−

<td>~~Limit~~</td>

+

−

<td>~~integer [1..255]~~; default: ~~150~~</td>

+

<td>ip4; default: {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.249|#default=192.168.1.249}}</td>

−

<td>~~How many addresses~~ the DHCP server ~~can lease out~~. Continuing from the example above: if the start address is 192.168.1.100 ~~and the server can lease out 150 addresses, available addresses will be from~~ 192.168.1.100 to 192.168.1.249 (~~100 + 150 – 1 =~~ 249~~; this is because~~ the ~~first~~ address ~~is inclusive)~~.</td>

+

<td>The ending IP address of the DHCP server IP address range. Continuing from the example above: if the start address is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.100|#default=192.168.1.100}} and the end address is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.249|#default=192.168.1.249}}, available addresses will be distributed from that range. If the subnet of your LAN IP address changes, this value needs to be changed accordingly.</td>

</tr>

<tr>

<td>Lease time</td>

−

<td>integer [2..999999]~~m/h~~; default: ~~12h~~</td>

+

<td>integer [1..999999]; default: 12 integer [2..999999]* integer [120..999999]**</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.</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. *If selected Units is Minutes. **If selected Units is seconds.</td>

+

</tr>

+

<tr>

+

<td>Units</td>

+

<td>Hours | Minutes | Seconds; default: Hours</td>

+

<td>Lease time units.</td>

</tr>

</table>

Line 738: Line 917:

Refer to the table below for information on the Advanced Settings section.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_advanced_settings_v1~~.png|border|class=tlt-border]]

+

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

Line 765: Line 944:

<td>dhcp options; default: none</td>

<td>Additional options to be added to the DHCP server. For example with '26,1470' or 'option:mtu, 1470' you can assign an MTU value per DHCP. You can find more information on DHCP Options [https://technet.microsoft.com/en-us/library/cc958941.aspx here].</td>

+

</tr>

+

<tr>

+

<td>Force DHCP options</td>

+

<td>off | on; default: off</td>

+

<td>If enabled, DHCP options will be sent even if it's not requested.</td>

</tr>

</table>

Line 772: Line 956:

Refer to the table below for information on the IPv6 Settings section.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_ipv6_settings_v1~~.png|border|class=tlt-border]]

+

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

Line 782: Line 966:

<tr>

<td>Router Advertisement Service</td>

−

<td>~~disabled~~ | ~~relay~~ mode | ~~server~~ mode | ~~hybrid~~ mode; default: Disabled</td>

+

<td>Disabled | Relay mode | Server mode | Hybrid mode; default: Disabled</td>

<td>Specifies whether router advertisements should be enabled (server mode), relayed or disabled. </td>

</tr>

<tr>

<td>DHCPv6 Service</td>

−

<td>~~disabled~~ | ~~relay~~ mode | ~~server~~ mode | ~~hybrid~~ mode; default: Disabled</td>

+

<td>Disabled | Relay mode | Server mode | Hybrid mode; default: Disabled</td>

<td>Specifies whether DHCPv6 server should be enabled (server), relayed (relay) or disabled (disabled).</td>

</tr>

<tr>

<td>NDP Proxy</td>

−

<td>~~disabled~~ | ~~relay~~ mode | ~~hybrid~~ mode; default: Disabled</td>

+

<td>Disabled | Relay mode | Hybrid mode; default: Disabled</td>

<td>Specifies whether NDP should be relayed or disabled.</td>

</tr>

<tr>

<td>DHCPv6 Mode</td>

−

<td>~~stateless~~ | ~~stateful~~-only | ~~stateless~~ + stateful; default: ~~stateless~~ + stateful</td>

+

<td>Stateless | Stateful-only | Stateless + stateful; default: Stateless + stateful</td>

−

+

<td>Router announcement (RA) mode.</td>

</tr>

<tr>

<td>Always announce default router</td>

<td>off | on; default: off</td>

−

+

<td>Default router lifetime in the the router announcement (RA) message will be set if default route is present and a global IPv6 address or if default route is present but no global IPv6 address or neither of both conditions.</td>

</tr>

<tr>

<td>Announced DNS server</td>

<td>ip; default: none</td>

−

+

<td>Supplements DHCP-assigned DNS server entries with ones specified in this field.</td>

</tr>

<tr>

<td>Announced DNS domains</td>

<td>ip; default: none</td>

−

+

<td>DNS domain handed out to DHCP clients.</td>

</tr>

</table>

Line 823: Line 1,007:

This section displays static IP leases currently existing on this device.

−

~~In order to view~~ the Static Lease section, ~~the interface~~ protocol ~~must be set~~ to ~~~~Static~~~~~~.~~

+

To make the Static Lease section visible, set interface protocol to Static.

−

~~[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_v1.png|border|class=tlt-border]]~~

−

~~====Static Lease: Settings====~~

----

−

To ~~access~~ a lease~~'s settings page,~~ click the '~~Edit~~' button ~~located to the right of the lease:~~

+

The Static Lease list is empty by default. To add a new Static Lease look to the Add Lease section; enter a custom name for the lease and click the 'Add' button.

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_edit_v1~~.png|border|class=tlt-border]]

+

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

−

You should be ~~directed~~ to ~~a window~~ that ~~looks like~~ this:

+

You should be redirected to the Settings page for that lease, which should look similar to this:

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_settings_v1~~.png|border|class=tlt-border]]

+

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

Line 846: Line 1,026:

<td>MAC address</td>

<td>mac; default: none</td>

−

<td>MAC address of a device that ~~is on~~ this interface~~'s network~~.</td>

+

<td>MAC address of a device that will connect to this network interface.</td>

</tr>

<tr>

Line 855: Line 1,035:

</table>

−

~~====Static Lease: Add Lease====~~

+

After you click 'Save & Apply' you will be redirected back to the [[#Network_Interfaces|Network Interfaces]] page. If you wish to modify the lease later, you can find in the Static Lease list. Simply click the 'Edit' button next to it in order to enter the Settings page for the Static Lease.

−

~~----~~

+

−

~~The Add Lease section is used~~ to ~~create new static leases~~. ~~To create a new~~ lease, ~~simply enter a custom name for it and~~ click the '~~Add~~' button.

+

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

−

~~[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_add_lease_v1.png|border|class=tlt-border]]~~

{{#ifeq: {{{wifi}}} | 1 |

===Relay Configuration===

----

The Relay Configuration section is used to relay and dynamically redirect incoming connections to a target host. Its main purpose is extending the wireless network. For example, when the device is in Wireless Station (client) mode, it can be used to bridge WAN and LAN interfaces to create a larger wireless network. You can find a detailed usage example [[Relayd|here]].

+

{{#switch: {{{series}}}

+

| #default =

+

| RUT36X|RUT9|TCR1 =

+

−

~~In order to view the~~ Relay ~~Configuration section,~~ the ~~interface~~ ~~protocol must be set to Static~~~~~~.

+

Note: Relay is additional software that can be installed from the System → [[{{{name}}} Package Manager|Package Manager]] page.

+

}}

−

[[File:~~Networking_rutos_manual_interfaces_network_interfaces_lan_relay_configuration_v1~~.png|border|class=tlt-border]]

+

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

Line 887: Line 1,071:

</table>|}}

−

[[Category:{{{name}}} ~~Services~~ section]]

+

===UDP Broadcast Relay===

+

----

+

The UDP Broadcast Relay will listen for broadcast traffic on the specified port and relay that traffic to the specified interface(s).

+

Note: UDP Broadcast Relay is additional software that can be installed from the System → [[{{{name}}} Package Manager|Package Manager]] page.

+

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

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enable</td>

+

<td>off <nowiki>|</nowiki> on; default: off</td>

+

<td>Turns UDP Broadcast Relay on or off.</td>

+

</tr>

+

<tr>

+

+

<td>integer [0..655353]; default: none</td>

+

<td>UDP port to listen for broadcast traffic.</td>

+

</tr>

+

<tr>

+

<td>Interfaces</td>

+

<td>network interface(s); default: none</td>

+

<td>The interface(s) to which the traffic will be redirected to.</td>

+

</tr>

+

</table>

+

{{#ifeq:{{{series}}}|TRB5||{{#ifeq: {{{mobile}}} | 1 |

+

===Mobile Data Limit===

+

----

+

The Mobile Data Limit 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.

+

In order to view the Mobile Data Limit section, the interface protocol must be set to Mobile.

+

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

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enable data connection limit</td>

+

<td>off <nowiki>|</nowiki> on; default: off</td>

+

<td>Turns mobile data limitations on or off.</td>

+

</tr>

+

<tr>

+

<td>Data limit* (MB)</td>

+

<td>integer; default: 1000</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>

+

<td>Period</td>

+

<td>Month <nowiki>|</nowiki> Week <nowiki>|</nowiki> Day; default: Day</td>

+

<td>Data limit period after which the data counter is reset on the specified Start day.</td>

+

</tr>

+

<tr>

+

<td>Start day <nowiki>|</nowiki> Start hour</td>

+

<td>day [1..31] <nowiki>|</nowiki> day [Monday..Sunday] {{!}} hour [1..24]; default: hour 0</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>

+

<td>Enable SMS warning</td>

+

<td>off <nowiki>|</nowiki> on; default: off</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>

+

<td>Data limit* (MB)</td>

+

<td>integer; default: none</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>

+

<td>Phone number</td>

+

<td>phone number; default: none</td>

+

<td>Recipient's phone numbers.</td>

+

</tr>

+

<tr>

+

<td>Data limit clear due</td>

+

+

<td>Display the date of the next automatic data limit clear.</td>

+

</tr>

+

</table>

+

*Your carrier's data usage accounting may differ. Teltonika is not liable should any accounting discrepancies occur.|}}}}

+

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

Gytispieze

Bureaucrats, Interface administrators, Administrators

9,561

edits

Namespaces

Variants

Views

More

Search

Changes

Template:Networking rutos manual interfaces (view source)

Revision as of 12:08, 24 October 2023

Navigation menu

Personal tools

NAVIGATION

Tools

Categories