Changes

Template:Networking rutos manual interfaces (view source)

Revision as of 18:02, 22 November 2021

5,314 bytes added , 18:02, 22 November 2021

no edit summary

Line 1: Line 1: −

{{Template:Networking_rutos_manual_fw_disclosure

+

{{Template: Networking_rutos_manual_fw_disclosure

−

| fw_version = {{{series}}}_R_00.02.04.1

+

| fw_version = {{{series}}}{{#ifeq:{{{name}}}|RUT241|M|}}_R_00.07.01{{#ifeq:{{{series}}}|RUT9|.1|}}

| series = {{{series}}}

}}

Line 18: Line 18:

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

−

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

+

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

+

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

+

==Add Interface==

Line 44: Line 46:

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

Line 52: Line 54:

−

+

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

</tr>

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

Line 61: Line 63:

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

−

+

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

</tr>

|

Line 84: Line 86:

===General Setup===

----

−

The General Setup section is used to configure the protocol of an interface 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====

Line 220: Line 222:

<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>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>{{#ifeq: {{{dualsim}}} | 1 |~~

<tr>

Line 230: Line 231:

<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>}}|}}{{#ifeq: {{{dualmodem}}} | 1 |

<tr>

<td>Modem</td>

Line 267: Line 269:

</tr>

<tr>

−

<td>Bridge <nowiki>|</nowiki> Passthrough: MAC Address</td>

+

<td>Bridge <nowiki>|</nowiki> Passthrough: 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>

+

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

+

| TRB1 =

+

| RUT30X =

+

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

+

}}

|}}

Line 304: Line 322:

<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 broadcast flag</td>

+

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

+

<td>Required for certain ISPs. For example, Charter with DOCSIS 3.</td>

+

</tr>

+

<tr>

+

<td>Use default gateway</td>

+

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

+

<td>When checked, creates a default route for the interface.</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>Use custom DNS servers</td>

+

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

+

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

+

</tr>

+

<tr>

+

<td>Client ID to send when requesting DHCP</td>

+

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

+

<td>Vendor class which will be sent when requesting a DHCP lease.</td>

</tr>

<tr>

Line 316: Line 364:

</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: Disabled</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</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>

</tr>

<tr>

−

<td~~>IPv6 assignment hint~~</td>

+

<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 350: Line 398:

<td>When an IPv6 prefix (like 'a:b:c:d::') is received from a delegating server, use a suffix (like '::1') to form an IPv6 address ('a:b:c:d::1') for the interface. Leave empty to generate a random suffix.</td>

</tr>

+

-->

</table>

Line 356: Line 405:

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

−

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

+

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

Line 378: Line 427:

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

<tr>

Line 391: Line 445:

<tr>

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

−

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

Line 430: Line 484:

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

−

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

+

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

Line 452: Line 506:

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

<tr>

Line 460: Line 519:

<tr>

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

−

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

Line 494: Line 553:

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

−

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

+

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

Line 516: Line 575:

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

<tr>

Line 534: Line 598:

<tr>

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

−

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

Line 573: Line 637:

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

−

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

+

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

Line 595: Line 659:

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

<tr>

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

−

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

+

<td>off <nowiki>|</nowiki> 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>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>

Line 621: Line 690:

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

−

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

+

[[File:Networking_rutos_manual_interfaces_interface_configuration_physical_settings.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 633: Line 700:

<tr>

<td>Bridge interfaces</td>

−

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

+

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

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

</tr>

<tr>

−

<td>Enable STP</td>

+

<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>Interface</td>

−

<td>network interface(s); default: ~~{{#ifeq:{{{series}}}|TRB1|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|}}.{{#ifeq:{{{name}}}|RUTXR1| ~~If the eth1 interface is selected, then port priority selection appears. </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>

+

<tr>

−

<td~~>Port priority~~</td>

+

<td>Port priority</td>

−

<td>Ethernet<nowiki>|</nowiki>SFP default: SFP</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.

+

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

+

</tr>|}}

−

|</td> </tr>}}

</table>

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

−

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

+

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

Line 679: Line 747:

[[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 685: Line 753:

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}}}.png|border|class=tlt-border]]

Line 710: Line 778:

<tr>

<td>Lease time</td>

−

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

+

<td>integer [1..999999]; default: 12integer [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 723: Line 796:

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.png|border|class=tlt-border]]

Line 757: Line 830:

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 767: Line 840:

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

Line 808: Line 881:

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 831: Line 900:

<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 840: Line 909:

</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 Services → [[{{{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 871: Line 944:

</tr>

</table>|}}

+

===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 Services → [[{{{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: {{{mobile}}} | 1 |

===Mobile Data Limit===

Line 876: Line 980:

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~~~~</i~~>.</u~~>

+

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

−

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

+

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

Line 922: Line 1,026:

</table>

−

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

+

*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,312

edits

Namespaces

Variants

Views

More

Search

Changes

Template:Networking rutos manual interfaces (view source)

Revision as of 18:02, 22 November 2021

Navigation menu

Personal tools

NAVIGATION

Tools

Categories