8,941
edits
Changes
Template:Networking tswos manual network (view source)
Revision as of 14:20, 11 October 2023
, 14:20, 11 October 2023Created page with "{{Template: Networking_rutos_manual_fw_disclosure | fw_version ={{Template: Networking_rutos_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }} __TOC__ ==..."
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
__TOC__
==Summary==
The <b>Network</b> page contains information related to the device's networking. This chapter is an overview of the Network page in {{{name}}} devices.
==Forwarding Table==
The <b>Forwarding Table</b> also known as MAC table, is most commonly used in network bridging, routing, and similar functions to find the proper output network interface controller to which the input interface should forward a packet. It is a dynamic table that maps MAC addresses to ports.
[[File:Networking_tswos_manual_status_network_forwarding_table.png|border|class=tlt-border]]
<table class="nd-othertables">
<tr>
<th width="250">field name</th>
<th width="900">description</th>
</tr>
<tr>
<td>Port</td>
<td>Name of physical port.</td>
</tr>
<tr>
<td>VLAN</td>
<td>VLAN assigned to that port.</td>
</tr>
<tr>
<td>MAC Address</td>
<td>MAC address of devices connected to that port.</td>
</tr>
</table>
==Spanning Tree==
The table shows the <b>Spanning Tree</b> states of each port.
[[File:Networking_tswos_manual_status_network_spanning_tree.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Port</td>
<td>port number</td>
<td>Name of physical port.</td>
</tr>
<tr>
<td>Protocol</td>
<td>Inactive {{!}} STP {{!}} RSTP</td>
<td>Protocol used by the port.</td>
</tr>
<tr>
<td>State</td>
<td>Inactive {{!}} Learning {{!}} Forwarding {{!}} Blocking {{!}} Listening {{!}} Discarding</td>
<td>State of the port.</td>
</tr>
<tr>
<td>Role</td>
<td>Inactive {{!}} Root {{!}} Designated {{!}} Alternate {{!}} Backup</td>
<td>Role of the port. Roles are used only for RSTP.</td>
</tr>
<tr>
<td>Port cost</td>
<td>integer</td>
<td>Cost of the port is determined by the port speed. Higher speed ports have lower cost. Lower cost is more preferred by spanning tree.</td>
</tr>
<tr>
<td>Port priority</td>
<td>integer</td>
<td>Priority of the port is used when costs of the ports are the same. Lower priority is more preferred by spanning tree. Also the lowest priority port is put into forwarding state.</td>
</tr>
</table>
==DHCP Leases==
The <b>DHCP Leases</b> table shows information about hosts and the time period for which a DHCP server allocates a network address to a client.
[[File:Networking_tswos_manual_status_network_dhcp_leases.png|border|class=tlt-border]]
<table class="nd-othertables">
<tr>
<th width="250">field name</th>
<th width="900">description</th>
</tr>
<tr>
<td>Host name</td>
<td>Client name.</td>
</tr>
<tr>
<td>IP address</td>
<td>Leased IP address.</td>
</tr>
<tr>
<td>MAC address</td>
<td>MAC address of the device.</td>
</tr>
<tr>
<td>Leasing remaining</td>
<td>Remaining time on the lease.</td>
</tr>
</table>
==Routes==
===ARP===
----
The <b>Address Resolution Protocol</b> (<b>ARP</b>) is a communication protocol used for mapping an Internet Protocol address (IP address) to a physical machine's link layer address (MAC address) belonging to the local network.
The ARP section displays the router's <b>ARP cache</b> (also known as ARP table) data. The ARP cache contains information on each known MAC address and its corresponding IP address. When the router receives a packet destined for a local host, the ARP program attempts to find a physical host or MAC address in the ARP cache that matches the IP address. If the ARP cache doesn't contain the needed IP address, ARP broadcasts a request packet to all LAN machines in order to find the device with the IP address in question.
The figure below is an example of the ARP cache section:
[[File:Networking_tswos_manual_routes_arp.png]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>IP address</td>
<td>ip; Default: <b>none</b></td>
<td>IP address of a local host.</td>
</tr>
<tr>
<td>MAC address</td>
<td>mac; Default: <b>none</b></td>
<td>MAC address of a local host.</td>
</tr>
<tr>
<td>Interface</td>
<td>string; Default: <b>none</b></td>
<td>Interface through which the router is associated with the host.</td>
</tr>
</table>
You can also view the ARP cache via shell using the <b>arp</b> or <b>ip neigh</b> commands, depending on which output your prefer:
root@Teltonika-{{{name}}}:~# <b>arp</b>
IP address HW type Flags HW address Mask Device
192.168.11.126 0x1 0x2 00:1e:42:00:00:00 * br0.1
root@Teltonika-{{{name}}}:~# <b>ip neigh</b>
192.168.11.126 dev br0.1 lladdr 00:1e:42:00:00:00 STALE
===IPv4 Routes===
----
The <b>IPv4 Routes</b> section displays the router's <b>routing table</b>. A routing table contains a list of routes to network destinations associated with and known by the router.
The figure below is an example of the Active IP routes section:
[[File:Networking_tswos_manual_routes_ipv4_routes.png|border|class=tlt-border ]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Network</td>
<td>string; Default: <b>none</b></td>
<td>Associated network interface name.</td>
</tr>
<tr>
<td>Target</td>
<td>ip | ip/netmask; Default: <b>none</b></td>
<td>Destination network address.</td>
</tr>
<tr>
<td>IPv4 gateway</td>
<td>ip; Default: <b>none</b></td>
<td>Indicates the IP address of the gateway through which the target network can be reached.</td>
</tr>
<tr>
<td>Metric</td>
<td>integer [0..4,294,967,295]; Default: <b>none</b></td>
<td>Metrics help the router choose the best route among multiple feasible routes to a destination. The route will go in the direction of the gateway with the lowest metric value.</td>
</tr>
<tr>
<td>Table</td>
<td>string | integer; Default: <b>none</b></td>
<td>Name or number of the associated routing table.</td>
</tr>
</table>
You can also view the routing table via shell using the <b>route</b> or <b>ip route</b> commands, depending on which output your prefer:
root@Teltonika-{{{name}}}:~# <b>route</b>
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default RUTX12.lan 0.0.0.0 UG 2 0 0 br0.1
192.168.11.0 * 255.255.255.0 U 1 0 0 br0.1
192.168.12.0 * 255.255.255.0 U 2 0 0 br0.1
root@Teltonika-{{{name}}}:~# <b>ip route</b>
default via 192.168.12.1 dev br0.1 proto static src 192.168.12.125 metric 2
192.168.11.0/24 dev br0.1 proto static scope link src 192.168.11.2 metric 1 offload
192.168.12.0/24 dev br0.1 proto static scope link src 192.168.12.125 metric 2 offload
===IPv6 routes===
----
The <b>IPv6 Routes</b> section displays the router's IPv6 routing table.
The figure below is an example of the IPv6 routes section:
[[File:Networking_tswos_manual_routes_ipv6_routes.png|border|class=tlt-border ]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Network</td>
<td>string; Default: <b>none</b></td>
<td>Associated network interface name.</td>
</tr>
<tr>
<td>Target</td>
<td>ip6 | ip6/netmask; Default: <b>none</b></td>
<td>Destination network address.</td>
</tr>
<tr>
<td>IPv6-Gateway</td>
<td>ip6 | ip6/netmask; Default: <b>none</b></td>
<td>Source of the network address.</td>
</tr>
<tr>
<td>Metric</td>
<td>integer [0..4,294,967,295]; Default: <b>none</b></td>
<td>Metrics help the router choose the best route among multiple feasible routes to a destination. The route will go in the direction of the gateway with the lowest metric value.</td>
</tr>
<tr>
<td>Table</td>
<td>string | integer; Default: <b>none</b></td>
<td>Name or number of the associated routing table.</td>
</tr>
</table>
You can also view the routing table via shell using the <b>route -A inet6</b> or <b>ip -6 route show</b> commands, depending on which output your prefer:
root@Teltonika-{{{name}}}:~# <b>ip -6 route</b>
fda0:4802:e99d::/48 from fda0:4802:e99d::/64 via fe80::21e:42ff:fe5a:7a10 dev br0.1 proto static metric 512 pref medium
fda0:4802:e99d::/64 dev br0.1 proto static metric 256 pref medium
unreachable fda0:4802:e99d::/64 dev lo proto static metric 2147483647 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev br0 proto kernel metric 256 pref medium
fe80::/64 dev br0.1 proto kernel metric 256 pref medium
===IPv6 Neighbours===
----
The <b>IPv6 Neighbours</b> section displays IPv6 associated neighbours.
The figure below is an example of the Active IPv6 Neighbours section:
[[File:Networking_tswos_manual_routes_ipv6_neighbours_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>IPv6 Address</td>
<td>ip6; Default: <b>none</b></td>
<td>IPv6 address of the associated neighbour.</td>
</tr>
<tr>
<td>MAC Address</td>
<td>ip6; Default: <b>none</b></td>
<td>MAC address of the associated neighbour.</td>
</tr>
<tr>
<td>Interface</td>
<td>string; Default: <b>none</b></td>
<td>Name of the associated network interface.</td>
</tr>
</table>
[[Category:{{{name}}} Status section]]
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
__TOC__
==Summary==
The <b>Network</b> page contains information related to the device's networking. This chapter is an overview of the Network page in {{{name}}} devices.
==Forwarding Table==
The <b>Forwarding Table</b> also known as MAC table, is most commonly used in network bridging, routing, and similar functions to find the proper output network interface controller to which the input interface should forward a packet. It is a dynamic table that maps MAC addresses to ports.
[[File:Networking_tswos_manual_status_network_forwarding_table.png|border|class=tlt-border]]
<table class="nd-othertables">
<tr>
<th width="250">field name</th>
<th width="900">description</th>
</tr>
<tr>
<td>Port</td>
<td>Name of physical port.</td>
</tr>
<tr>
<td>VLAN</td>
<td>VLAN assigned to that port.</td>
</tr>
<tr>
<td>MAC Address</td>
<td>MAC address of devices connected to that port.</td>
</tr>
</table>
==Spanning Tree==
The table shows the <b>Spanning Tree</b> states of each port.
[[File:Networking_tswos_manual_status_network_spanning_tree.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Port</td>
<td>port number</td>
<td>Name of physical port.</td>
</tr>
<tr>
<td>Protocol</td>
<td>Inactive {{!}} STP {{!}} RSTP</td>
<td>Protocol used by the port.</td>
</tr>
<tr>
<td>State</td>
<td>Inactive {{!}} Learning {{!}} Forwarding {{!}} Blocking {{!}} Listening {{!}} Discarding</td>
<td>State of the port.</td>
</tr>
<tr>
<td>Role</td>
<td>Inactive {{!}} Root {{!}} Designated {{!}} Alternate {{!}} Backup</td>
<td>Role of the port. Roles are used only for RSTP.</td>
</tr>
<tr>
<td>Port cost</td>
<td>integer</td>
<td>Cost of the port is determined by the port speed. Higher speed ports have lower cost. Lower cost is more preferred by spanning tree.</td>
</tr>
<tr>
<td>Port priority</td>
<td>integer</td>
<td>Priority of the port is used when costs of the ports are the same. Lower priority is more preferred by spanning tree. Also the lowest priority port is put into forwarding state.</td>
</tr>
</table>
==DHCP Leases==
The <b>DHCP Leases</b> table shows information about hosts and the time period for which a DHCP server allocates a network address to a client.
[[File:Networking_tswos_manual_status_network_dhcp_leases.png|border|class=tlt-border]]
<table class="nd-othertables">
<tr>
<th width="250">field name</th>
<th width="900">description</th>
</tr>
<tr>
<td>Host name</td>
<td>Client name.</td>
</tr>
<tr>
<td>IP address</td>
<td>Leased IP address.</td>
</tr>
<tr>
<td>MAC address</td>
<td>MAC address of the device.</td>
</tr>
<tr>
<td>Leasing remaining</td>
<td>Remaining time on the lease.</td>
</tr>
</table>
==Routes==
===ARP===
----
The <b>Address Resolution Protocol</b> (<b>ARP</b>) is a communication protocol used for mapping an Internet Protocol address (IP address) to a physical machine's link layer address (MAC address) belonging to the local network.
The ARP section displays the router's <b>ARP cache</b> (also known as ARP table) data. The ARP cache contains information on each known MAC address and its corresponding IP address. When the router receives a packet destined for a local host, the ARP program attempts to find a physical host or MAC address in the ARP cache that matches the IP address. If the ARP cache doesn't contain the needed IP address, ARP broadcasts a request packet to all LAN machines in order to find the device with the IP address in question.
The figure below is an example of the ARP cache section:
[[File:Networking_tswos_manual_routes_arp.png]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>IP address</td>
<td>ip; Default: <b>none</b></td>
<td>IP address of a local host.</td>
</tr>
<tr>
<td>MAC address</td>
<td>mac; Default: <b>none</b></td>
<td>MAC address of a local host.</td>
</tr>
<tr>
<td>Interface</td>
<td>string; Default: <b>none</b></td>
<td>Interface through which the router is associated with the host.</td>
</tr>
</table>
You can also view the ARP cache via shell using the <b>arp</b> or <b>ip neigh</b> commands, depending on which output your prefer:
root@Teltonika-{{{name}}}:~# <b>arp</b>
IP address HW type Flags HW address Mask Device
192.168.11.126 0x1 0x2 00:1e:42:00:00:00 * br0.1
root@Teltonika-{{{name}}}:~# <b>ip neigh</b>
192.168.11.126 dev br0.1 lladdr 00:1e:42:00:00:00 STALE
===IPv4 Routes===
----
The <b>IPv4 Routes</b> section displays the router's <b>routing table</b>. A routing table contains a list of routes to network destinations associated with and known by the router.
The figure below is an example of the Active IP routes section:
[[File:Networking_tswos_manual_routes_ipv4_routes.png|border|class=tlt-border ]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Network</td>
<td>string; Default: <b>none</b></td>
<td>Associated network interface name.</td>
</tr>
<tr>
<td>Target</td>
<td>ip | ip/netmask; Default: <b>none</b></td>
<td>Destination network address.</td>
</tr>
<tr>
<td>IPv4 gateway</td>
<td>ip; Default: <b>none</b></td>
<td>Indicates the IP address of the gateway through which the target network can be reached.</td>
</tr>
<tr>
<td>Metric</td>
<td>integer [0..4,294,967,295]; Default: <b>none</b></td>
<td>Metrics help the router choose the best route among multiple feasible routes to a destination. The route will go in the direction of the gateway with the lowest metric value.</td>
</tr>
<tr>
<td>Table</td>
<td>string | integer; Default: <b>none</b></td>
<td>Name or number of the associated routing table.</td>
</tr>
</table>
You can also view the routing table via shell using the <b>route</b> or <b>ip route</b> commands, depending on which output your prefer:
root@Teltonika-{{{name}}}:~# <b>route</b>
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default RUTX12.lan 0.0.0.0 UG 2 0 0 br0.1
192.168.11.0 * 255.255.255.0 U 1 0 0 br0.1
192.168.12.0 * 255.255.255.0 U 2 0 0 br0.1
root@Teltonika-{{{name}}}:~# <b>ip route</b>
default via 192.168.12.1 dev br0.1 proto static src 192.168.12.125 metric 2
192.168.11.0/24 dev br0.1 proto static scope link src 192.168.11.2 metric 1 offload
192.168.12.0/24 dev br0.1 proto static scope link src 192.168.12.125 metric 2 offload
===IPv6 routes===
----
The <b>IPv6 Routes</b> section displays the router's IPv6 routing table.
The figure below is an example of the IPv6 routes section:
[[File:Networking_tswos_manual_routes_ipv6_routes.png|border|class=tlt-border ]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Network</td>
<td>string; Default: <b>none</b></td>
<td>Associated network interface name.</td>
</tr>
<tr>
<td>Target</td>
<td>ip6 | ip6/netmask; Default: <b>none</b></td>
<td>Destination network address.</td>
</tr>
<tr>
<td>IPv6-Gateway</td>
<td>ip6 | ip6/netmask; Default: <b>none</b></td>
<td>Source of the network address.</td>
</tr>
<tr>
<td>Metric</td>
<td>integer [0..4,294,967,295]; Default: <b>none</b></td>
<td>Metrics help the router choose the best route among multiple feasible routes to a destination. The route will go in the direction of the gateway with the lowest metric value.</td>
</tr>
<tr>
<td>Table</td>
<td>string | integer; Default: <b>none</b></td>
<td>Name or number of the associated routing table.</td>
</tr>
</table>
You can also view the routing table via shell using the <b>route -A inet6</b> or <b>ip -6 route show</b> commands, depending on which output your prefer:
root@Teltonika-{{{name}}}:~# <b>ip -6 route</b>
fda0:4802:e99d::/48 from fda0:4802:e99d::/64 via fe80::21e:42ff:fe5a:7a10 dev br0.1 proto static metric 512 pref medium
fda0:4802:e99d::/64 dev br0.1 proto static metric 256 pref medium
unreachable fda0:4802:e99d::/64 dev lo proto static metric 2147483647 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev br0 proto kernel metric 256 pref medium
fe80::/64 dev br0.1 proto kernel metric 256 pref medium
===IPv6 Neighbours===
----
The <b>IPv6 Neighbours</b> section displays IPv6 associated neighbours.
The figure below is an example of the Active IPv6 Neighbours section:
[[File:Networking_tswos_manual_routes_ipv6_neighbours_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>IPv6 Address</td>
<td>ip6; Default: <b>none</b></td>
<td>IPv6 address of the associated neighbour.</td>
</tr>
<tr>
<td>MAC Address</td>
<td>ip6; Default: <b>none</b></td>
<td>MAC address of the associated neighbour.</td>
</tr>
<tr>
<td>Interface</td>
<td>string; Default: <b>none</b></td>
<td>Name of the associated network interface.</td>
</tr>
</table>
[[Category:{{{name}}} Status section]]
