Changes

971 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_rutos_manual_fw_disclosure~~

+

{{Template: Networking_device_manual_fw_disclosure

−

| fw_version ={{Template: ~~Networking_rutos_manual_latest_fw~~

+

| series = {{{series}}}

+

| name = {{{name}}}

+

| fw_version ={{Template: Networking_device_manual_latest_fw

| series = {{{series}}}

| name = {{{name}}}

Line 21: Line 23:

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

−

[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_{{{lan}}}_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}_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]]|}}

==Add Interface==

Line 84: 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_edit_button_lan_{{{lan}}}.png]]

+

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

===General Setup===

Line 104: 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 276: Line 278:

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

----

−

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

+

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

Line 294: Line 296:

</ul>

</td>

+

<tr>

+

<td>Subnet selection</td>

+

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

+

<td>Subnet selection method.</td>

+

</tr>

<tr>

Line 360: Line 367:

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

----

−

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

+

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

Line 370: Line 377:

<tr>

−

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

+

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

<td>Mobile connection operating mode.

<ul>

Line 378: Line 385:

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

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

<tr>

Line 428: Line 439:

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

−

| TRB1 =

+

| TRB1|TRB5|RUT36X =

−

| ~~RUT30X =~~

−

| RUT36X =

| TRB2 =

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

Line 453: Line 462:

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

−

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

+

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

Line 460: 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 489: Line 493:

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

Line 533: Line 542:

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

−

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

+

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

Line 540: 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 594: Line 598:

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

Line 607: Line 615:

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

−

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

+

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

Line 614: 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 658: Line 661:

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

Line 671: Line 678:

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

−

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

+

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

Line 678: 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 760: Line 762:

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

−

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

+

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

Line 767: 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 787: Line 784:

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

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

−

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

+

</tr>

<tr>

<td>Use gateway metric</td>

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

<tr>

<td>Override MTU</td>

Line 804: Line 801:

</tr>

</table>|}}

+

===Physical Settings===

----

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

−

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

+

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

Line 822: Line 820:

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

Line 871: Line 874:

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

−

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

Line 1,045: Line 1,048:

−

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

+

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

}}

Line 1,072: Line 1,075:

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.

+

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

Line 1,098: Line 1,101:

</tr>

</table>

−

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

+

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

===Mobile Data Limit===

----

Line 1,105: Line 1,108:

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

+

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

Line 1,146: Line 1,149:

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

+

*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