Template:Networking rutos manual network: Difference between revisions
Gytispieze (talk | contribs) No edit summary |
No edit summary |
||
| (78 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template: | {{Template: Networking_device_manual_fw_disclosure | ||
| fw_version ={{Template: | | series = {{{series}}} | ||
| name = {{{name}}} | |||
| fw_version ={{Template: Networking_device_manual_latest_fw | |||
| series = {{{series}}} | | series = {{{series}}} | ||
| name = {{{name}}} | | name = {{{name}}} | ||
}} | }} | ||
}} | }} | ||
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Network (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: | {{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Network (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}} | ||
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Network (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: | {{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Network (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}} | ||
__TOC__ | __TOC__ | ||
==Summary== | ==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. | 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. | ||
{{#ifeq:{{{mobile}}}|1| | {{#ifeq:{{{mobile}}}|1| | ||
| Line 21: | Line 19: | ||
The <b>Mobile</b> tab displays information about the mobile connection. The figure below is an example of the Mobile tab: | The <b>Mobile</b> tab displays information about the mobile connection. The figure below is an example of the Mobile tab: | ||
{{#switch: {{{series}}} | {{#switch: {{{series}}} | ||
| RUTX = | | RUTX | RUTM | RUTC = | ||
{{#switch: {{{name}}} | {{#switch: {{{name}}} | ||
| | |#default = [[File:Networking rutx manual network mobile v6.png|border|class=tlt-border]] | ||
| | | RUTX12|RUTM12|RUTM52 = [[File:Networking rutx12 manual network mobile v6.png|border|class=tlt-border]] | ||
}} | }} | ||
| TRB1 | | TRB1|RUT2|RUT2M|RUT36X|TRB5|RUT361|TCR1|TRB16|RUT206|TRB501 = [[File:Networking_trb14x_manual_network_v6.png|border|class=tlt-border]] | ||
| | | TRB2|RUT9|RUT9M|TRB2M|OTD140|OTD500|RUTE = [[File:Networking_trb2XX_manual_network_v6.png|border|class=tlt-border]] | ||
| RUT36X | |||
| | |||
| | |||
| | |||
| | |||
}} | }} | ||
<table class="nd-mantable"> | |||
<table class="nd- | |||
<tr> | <tr> | ||
<th width="250"> | <th width="250">Field name</th> | ||
<th width="900"> | <th width="900">Description</th> | ||
</tr> | </tr> | ||
{{#switch: {{{series}}} | {{#switch: {{{series}}} | ||
| | |RUTX|RUTM|RUTC= | ||
RUTX= | {{#switch:{{{name}}} | ||
{{# | |RUTX12 | RUTM12 | RUTM52 = | ||
|#default= <!-- dont show for rutx12 --> | |||
<tr> | <tr> | ||
<td>Sim card slot in use</td> | <td>Sim card slot in use</td> | ||
| Line 53: | Line 43: | ||
</tr> | </tr> | ||
}} | }} | ||
| | | TRB2 | RUT9 | RUT9M | TRB2M | OTD140 | OTD500 | RUTE = | ||
| | |||
RUT9= | |||
<tr> | <tr> | ||
<td>Sim card slot in use</td> | <td>Sim card slot in use</td> | ||
<td>Shows which sim card slot is currently in use</td> | <td>Shows which sim card slot is currently in use</td> | ||
</tr> | </tr> | ||
| | |#default= | ||
}} | }} | ||
<tr> | <tr> | ||
<td>SIM card state</td> | <td>SIM card state</td> | ||
| Line 80: | Line 59: | ||
</ul> | </ul> | ||
</td> | </td> | ||
</tr> | |||
<tr> | |||
<td>Provider</td> | |||
<td>Network operator's name</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 107: | Line 90: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Data connection state</td> | ||
<td> | <td>Indicates whether the device has a mobile data connection or not.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Connection stage</td> | ||
<td> | <td>Show intermediate stages of mobile connection establishing process.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Network type</td> | ||
<td>Mobile | <td>Mobile network type. Possible values are: | ||
<ul> | <ul>{{#ifeq: {{{5g}}} | 1 | | ||
<li> <b>5G</b>:{{#switch:{{{name}}}|RUT271|RUT276|RUT976=|#default= 5G (NSA),}} 5G (SA)</li>|}} | |||
<li> <b>4G</b>: | <li> <b>4G</b>: | ||
{{# | {{#switch: {{{name}}} | TRB255 | TRB256 = | ||
4G (NB), 4G (M1) | 4G (NB), 4G (M1) | ||
| 4G (LTE) }} | | #default = 4G (LTE) }} | ||
</li> | </li> | ||
{{# | {{#switch: {{{name}}} | TRB255 | TRB256 | RUT271 | RUT276 | RUT976 | RUTM59 | TRB247= | #default= | ||
<li> <b>3G</b>: 3G (WCDMA), 3G (HSDPA), 3G (HSUPA), 3G (HSPA), 3G (HSPA+), 3G (DC-HSPA+), 3G (HSDPA+HSUPA), UMTS</li> | <li> <b>3G</b>: 3G (WCDMA), 3G (HSDPA), 3G (HSUPA), 3G (HSPA), 3G (HSPA+), 3G (DC-HSPA+), 3G (HSDPA+HSUPA), UMTS</li> | ||
}} | }} | ||
{{#ifeq: {{{ | {{#ifeq: {{{2g}}} | 1 | <!-- add variable for rut9 devices --> | ||
<li><b>2G</b>: 2G (GSM), 2G (GPRS), 2G (EDGE)</li> | <li><b>2G</b>: 2G (GSM), 2G (GPRS), 2G (EDGE)</li> | ||
}} | }} | ||
| Line 136: | Line 120: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Carrier Aggregation</td> | |||
<td>LTE Advanced Carrier Aggregation, CA, is one of the key techniques used to enable the very high data rates of 4G to be achieved. | <td>LTE Advanced Carrier Aggregation, CA, is one of the key techniques used to enable the very high data rates of 4G to be achieved. | ||
By combining more than one carrier together, either in the same or different bands it is possible to increase the bandwidth available and in this way increase the capacity of the link. | By combining more than one carrier together, either in the same or different bands it is possible to increase the bandwidth available and in this way increase the capacity of the link. | ||
</td> | </td> | ||
</tr> | |||
<tr> | |||
<td>Bandwidth</td> | |||
<td>Bandwidth describes the maximum data transfer rate of Internet connection.</td> | |||
</tr> | |||
<tr> | |||
<td>Connected band</td> | <td>Connected band</td> | ||
<td>Currently used frequency band. | <td>Currently used mobile frequency band.</td> | ||
</tr> | |||
<tr> | |||
<td>RSSI</td> | |||
<td>Received signal strength indicator (<b>[[RSSI]]</b>) measured in dBm. Values closer to 0 indicate a better signal strength</td> | |||
</tr> | |||
<tr> | |||
<td>Data received</td> | |||
<td>Amount of data received through the mobile interface</td> | |||
</tr> | |||
<tr> | |||
<td>Data sent</td> | |||
<td>Amount of data sent through the mobile interface</td> | |||
</tr> | |||
<tr> | |||
<td>Cell ID</td> | |||
<td>The ID of the cell that the modem is currently connected to</td> | |||
</tr> | |||
<tr> | |||
<td>LAC/TAC</td> | |||
<td> | |||
<ul> | |||
<li><b>LAC</b> The Location Area Code, abbreviated as LAC is the unique number given to each location area within the network. The served area of a cellular radio access network is usually divided into location areas, consisting of one or several radio cells GSM/3G</li><li><b>TAC</b> Tracking Area Code is a numerical identifier used in LTE networks to distinguish different tracking areas. A tracking area is a group of cells that share the same identity for tracking and paging purposes. TAC is an essential parameter for the UE to determine its location within the LTE/5G network.</li> | |||
</ul> | |||
</td> | |||
</tr> | |||
<tr> | |||
<td>Physical cell ID</td> | |||
<td>Physical Cell ID is an identification of a cell at physical layer.</td> | |||
</tr> | |||
<tr> | |||
<td>ARFCN</td> | |||
<td>In mobile cellular networks, an absolute radio-frequency channel number (ARFCN) is a code that specifies a pair of physical radio carriers used for transmission and reception in a land mobile radio system, one for the uplink signal and one for the downlink signal.</td> | |||
</tr> | |||
<tr> | |||
<td>Mobile country code</td> | |||
<td>The Mobile Country Code, abbreviated as MCC, is the code uniquely identifying the home country of a (Glossary:Mobile network operator (MNO{{!}}mobile network operator (MNO).</td> | |||
</tr> | |||
<tr> | |||
<td>Mobile network code</td> | |||
<td>Mobile Network Code (MNC) is a unique two- or three-digit number used to identify a home Public Land Mobile Network (PLMN) to. MNC is allocated by the national regulator.</td> | |||
</tr> | |||
</table> | |||
If mobile data limit is set and reached, near ''Connection'' column warning mark will appear. E.g.: | |||
[[File:Networking rutos manual network mobile data limit.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th width="250">Bands information</th> | |||
<th width="900">Connected band</th> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Other signal level measurements</td> | <td>Other signal level measurements</td> | ||
<td>Overall signal quality for different | <td>Overall signal quality for different network types is defined by different measurements. Short explanations and recommendations are provided below. Click <b>[[Mobile Signal Strength Recommendations|here]]</b> for more in-depth information or click on one of the links below: | ||
<ul> | <ul>{{#ifeq: {{{5g}}} | 1 | | ||
<li> <b>5G</b> | |||
<ul> | |||
<li>[[RSRP and RSRQ|RSRP]] - reference signal received power, measured in dBm. Values closer to 0 indicate better signal strength</li> | |||
<li>[[RSRP and RSRQ|RSRQ]] - reference signal received quality, measured in dB. Values closer to 0 indicate a better rate of information transfer</li> | |||
<li>[[SINR]] - signal-to-interference-plus-noise ratio, measured in dB. Higher values indicate a better rate of information transfer</li> | |||
</ul></li>|}} | |||
<li><b>4G</b> | <li><b>4G</b> | ||
<ul> | <ul> | ||
| Line 161: | Line 202: | ||
</li> | </li> | ||
{{# | {{#switch: {{{name}}} | TRB255 | TRB256 | RUT271 | RUT276 | RUT976 | RUTM59 | TRB247= | #default = | ||
<li><b>3G</b> | <li><b>3G</b> | ||
<ul> | <ul> | ||
| Line 170: | Line 211: | ||
}} | }} | ||
{{#ifeq: {{{ | {{#ifeq: {{{2g}}} | 1 | | ||
<li><b>2G</b> | <li><b>2G</b> | ||
<ul> | <ul> | ||
| Line 179: | Line 220: | ||
</ul> | </ul> | ||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
}} <!-- ends all mobile section --> | }} <!-- ends all mobile section --> | ||
| Line 208: | Line 229: | ||
This tab displays information about the device's local network(s). The figure below is an example of the '''Network''' window: | This tab displays information about the device's local network(s). The figure below is an example of the '''Network''' window: | ||
[[File: | [[File:Networking rutos manual network lan ipv4 v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | |||
<table class="nd- | |||
<tr> | <tr> | ||
<th | <th width="250">Field name</th> | ||
<th width="900">Description</th> | |||
< | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Address</td> | ||
<td>IP address of the LAN interface</td> | <td>IP address of the LAN interface</td> | ||
</tr> | </tr> | ||
| Line 227: | Line 245: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th colspan="2"> | <th colspan="2">DHCP Leases</th> | ||
</tr> | |||
<tr> | |||
<td>Interface</td> | |||
<td>Interface which leased the address</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 234: | Line 256: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>IP | <td>IP Address</td> | ||
<td>IP address of a LAN client</td> | <td>IP address of a LAN client</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>MAC | <td>MAC Address</td> | ||
<td>MAC address of a LAN client</td> | <td>MAC address of a LAN client</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Leasetime | <td>Leasetime Remaining</td> | ||
<td>Remaining lease time for a DHCP client. Active DHCP lease holders will try to renew their DHCP leases after a half of the lease time passes. </td> | |||
</tr> | |||
<tr> | |||
<td>Static Lease</td> | |||
<td>This action will reserve currently assigned IP address for the device in Network -> Interfaces -> Static leases. </td> | |||
</tr> | |||
</table> | |||
Similarly there is an IPv6 dedicated tab. | |||
[[File:Networking rutos manual network lan ipv6 v1.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th width="250">Field name</th> | |||
<th width="900">Description</th> | |||
</tr> | |||
<tr> | |||
<td>Address</td> | |||
<td>IP address of the LAN interface</td> | |||
</tr> | |||
<tr> | |||
<td>Delegated prefix</td> | |||
<td>The delegated prefix is a smaller subnet given to a device to lease IPv6 addresses for its own DHCPv6 clients.</td> | |||
</tr> | |||
<tr> | |||
<th colspan="2">DHCP Leases</th> | |||
</tr> | |||
<tr> | |||
<td>Interface</td> | |||
<td>Interface which leased the address</td> | |||
</tr> | |||
<tr> | |||
<td>Hostname</td> | |||
<td>Hostname of a LAN client</td> | |||
</tr> | |||
<tr> | |||
<td>Address</td> | |||
<td>IP address of a LAN client</td> | |||
</tr> | |||
<tr> | |||
<td>Delegated prefix</td> | |||
<td>The delegated prefix is a smaller subnet given to a device to lease IPv6 addresses for its own DHCPv6 clients.</td> | |||
</tr> | |||
<tr> | |||
<td>DUID</td> | |||
<td>DHCP unique identifier is used by DHCPv6 to identify device. Similar to MAC that is used by DHCPv4. </td> | |||
</tr> | |||
<tr> | |||
<td>Leasetime Remaining</td> | |||
<td>Remaining lease time for a DHCP client. Active DHCP lease holders will try to renew their DHCP leases after a half of the lease time passes. </td> | <td>Remaining lease time for a DHCP client. Active DHCP lease holders will try to renew their DHCP leases after a half of the lease time passes. </td> | ||
</tr> | |||
<tr> | |||
<td>Static Lease</td> | |||
<td>This action will reserve currently assigned IP address for the device in Network -> Interfaces -> Static leases. </td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
== | ==Firewall== | ||
This page displays information about the device's firewall. Info is shown of IPv4 and IPv6 traffic. The figure below is an example of the '''Chains''' and '''Rules''' sections: | |||
[[File: | [[File:Networking rutos manual status network firewall chains.png|border|class=tlt-border]] | ||
<table class="nd- | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th width="250">Field name</th> | <th width="250">Field name</th> | ||
| Line 259: | Line 335: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Reset counters</td> | ||
<td> | <td>Resets all traffic and packet fields</td> | ||
</tr> | |||
<tr> | |||
<td>Name</td> | |||
<td>Name of the chain</td> | |||
</tr> | |||
<tr> | |||
<td>Traffic</td> | |||
<td>Size of traffic that was matched to the chain</td> | |||
</tr> | |||
<tr> | |||
<td>Packets</td> | |||
<td>Count of packets that were matched to the chain</td> | |||
</tr> | |||
<tr> | |||
<td>Policy</td> | |||
<td>Policy for traffic entering the zone. </td> | |||
</tr> | </tr> | ||
<tr> | |||
<td>Rules</td> | |||
<td>Count of rules the chain has</td> | |||
</tr> | |||
<tr> | |||
<td>References</td> | |||
<td>Count of times the chain was referenced in other chains </td> | |||
</tr> | |||
</table> | |||
For more information about specific firewall chain, <b>View</b> button can be pressed. Window like this should pop up: | |||
[[File:Networking rutos manual status network firewall chain_info.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th width="250">Field name</th> | |||
<th width="900">Description</th> | |||
</tr> | |||
<tr> | |||
<td>Traffic</td> | |||
<td>Size of traffic that was matched to the rule </td> | |||
</tr> | |||
<tr> | |||
<td>Packets</td> | |||
<td>Count of packets that were matched to the rule</td> | |||
</tr> | |||
<tr> | |||
<td>Target</td> | |||
<td>Name of the rule (if highlighted you can click it to open modal to it) </td> | |||
</tr> | |||
<tr> | <tr> | ||
<td> | <td>Protocol</td> | ||
<td> | <td>Filters by Internet protocol</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>In</td> | ||
<td> | <td>Filters by inbound interface</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Out</td> | ||
<td> | <td>Filters by outbound interface </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Source</td> | ||
<td> | <td>Filters by source address </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Destination</td> | ||
<td> | <td>Filters by destination address </td> | ||
</tr> | </tr> | ||
<tr> | |||
<td> | <td>Options</td> | ||
<td> | <td>Additional iptables options</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Comment</td> | ||
<td>Device' | <td>Filters by comment</td> | ||
</tr> | |||
</table> | |||
Rules section - displays rules assigned to chains: | |||
[[File:Networking rutos manual status network firewall rules.png|border|class=tlt-border]] | |||
To inspect rules, open chain and press on target. You will be redirected to inner chain modal: | |||
[[File:Networking rutos manual status network firewall rules_inner.png|border|class=tlt-border]] | |||
==Topology== | |||
The <b>Topology</b> tab allows scanning of WAN, LAN or both interfaces via arp scan to check active connected devices. After scan it shows how many active devices were found and on which interface. | |||
[[File:Networking_rutos_manual_status_network_topology_graf_v3.png|border|class=tlt-border]] | |||
<b>Topology scan results</b> | |||
This section displays the results of the scan. | |||
[[File:Networking_rutos_manual_status_network_topology_table_v3.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th width="250">Field name</th> | |||
<th width="900">Description</th> | |||
</tr> | |||
<tr> | |||
<td>Satus</td> | |||
<td>Satus of scanned device (green color indicates that device is Up/ red - Down)</td> | |||
</tr> | |||
<tr> | |||
<td>IP Address</td> | |||
<td>IP address of scanned device</td> | |||
</tr> | |||
<tr> | |||
<td>MAC Address</td> | |||
<td>MAC address of scanned device</td> | |||
</tr> | |||
<tr> | |||
<td>Interface</td> | |||
<td>The interface through which the device is connected</td> | |||
</tr> | |||
<tr> | |||
<td>Port</td> | |||
<td>The physical port through which the device is connected</td> | |||
</tr> | |||
<tr> | |||
<td>Type</td> | |||
<td>Device connection type</td> | |||
</tr> | |||
<tr> | |||
<td>Download</td> | |||
<td>Download speed between connected device</td> | |||
</tr> | |||
<tr> | |||
<td>Upload</td> | |||
<td>Upload speed between connected device</td> | |||
</tr> | |||
</table> | |||
{{#ifeq: {{{network_usage}}} | 1 | | |||
==Network Usage== | |||
The <b>Network Usage</b> page displays data usage and connection information from source IP and destination IP. To enable 'Network usage tracking' you can toggle it from the global settings: | |||
[[File:Networking_rutos_manual_status_network_usage_global.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th>Field</th> | |||
<th>Value</th> | |||
<th>Description</th> | |||
</tr> | |||
<tr> | |||
<td>Network usage tracking</td> | |||
<td>on {{!}} off; default: <b>off</b></td> | |||
<td>Enable network usage tracking.</td> | |||
</tr> | |||
<tr> | |||
<td>Save history</td> | |||
<td>on {{!}} off; default: <b>on</b></td> | |||
<td>Network traffic data is being recorded every last 12 hours.</td> | |||
</tr> | |||
</table> | |||
===Total usage=== | |||
[[File:Networking_rutos_manual_status_network_usage_total_usage.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th width="250">Field name</th> | |||
<th width="900">Description</th> | |||
</tr> | |||
<tr> | |||
<td>Delete data</td> | |||
<td>Delete all "Total usage" data</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Satus</td> | ||
<td> | <td>Satus of device (green color indicates that device is Up/ red - Down)</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Source IP Address</td> | ||
<td> | <td>IP address of source device</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Source MAC Address</td> | ||
<td> | <td>MAC address of source device</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Connections</td> | ||
<td> | <td>Number of connections made by the source IP</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Download</td> | ||
<td> | <td>Data downloaded from the source IP</td> | ||
</tr> | </tr> | ||
<tr> | |||
<td>Upload</td> | |||
<td>Data uploaded to the source IP</td> | |||
</tr> | |||
</table> | </table> | ||
}} | ===Connections usage=== | ||
[[File:Networking_rutos_manual_status_network_usage_connections_usage.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th width="250">Field name</th> | |||
<th width="900">Description</th> | |||
</tr> | |||
<tr> | |||
<td>Delete data</td> | |||
<td>Delete all "Connections" data</td> | |||
</tr> | |||
<tr> | |||
<td>Satus</td> | |||
<td>Satus of device (green color indicates that device is Up/ red - Down)</td> | |||
</tr> | |||
<tr> | |||
<td>Source IP Address</td> | |||
<td>IP address of source device</td> | |||
</tr> | |||
<tr> | |||
<td>Source MAC Address</td> | |||
<td>MAC address of source device</td> | |||
</tr> | |||
<tr> | |||
<td>Destination IP Address</td> | |||
<td>IP address of destination</td> | |||
</tr> | |||
<tr> | |||
<td>Protocol</td> | |||
<td>Protocol of connection</td> | |||
</tr> | |||
<tr> | |||
<td>Connections</td> | |||
<td>Number of connections made from source IP to the destination IP</td> | |||
</tr> | |||
<tr> | |||
<td>Download</td> | |||
<td>Data downloaded from destination IP</td> | |||
</tr> | |||
<tr> | |||
<td>Upload</td> | |||
<td>Data uploaded to destination IP</td> | |||
</tr> | |||
</table>|}} | |||
[[Category:{{{name}}} Status section]] | [[Category:{{{name}}} Status section]] | ||
Revision as of 16:50, 20 November 2025
The information in this page is updated in accordance with firmware version .
Summary
The Network page contains information related to the device's networking. This chapter is an overview of the Network page in {{{name}}} devices.
LAN
This tab displays information about the device's local network(s). The figure below is an example of the Network window:
| Field name | Description |
|---|---|
| Address | IP address of the LAN interface |
| Netmask | Netmask of the LAN interface. In a sense, a netmask specifies the size of a network. In other words, it indicates which part of the IP address denotes the network, and which denotes the device |
| DHCP Leases | |
| Interface | Interface which leased the address |
| Hostname | Hostname of a LAN client |
| IP Address | IP address of a LAN client |
| MAC Address | MAC address of a LAN client |
| Leasetime Remaining | Remaining lease time for a DHCP client. Active DHCP lease holders will try to renew their DHCP leases after a half of the lease time passes. |
| Static Lease | This action will reserve currently assigned IP address for the device in Network -> Interfaces -> Static leases. |
Similarly there is an IPv6 dedicated tab.
| Field name | Description |
|---|---|
| Address | IP address of the LAN interface |
| Delegated prefix | The delegated prefix is a smaller subnet given to a device to lease IPv6 addresses for its own DHCPv6 clients. |
| DHCP Leases | |
| Interface | Interface which leased the address |
| Hostname | Hostname of a LAN client |
| Address | IP address of a LAN client |
| Delegated prefix | The delegated prefix is a smaller subnet given to a device to lease IPv6 addresses for its own DHCPv6 clients. |
| DUID | DHCP unique identifier is used by DHCPv6 to identify device. Similar to MAC that is used by DHCPv4. |
| Leasetime Remaining | Remaining lease time for a DHCP client. Active DHCP lease holders will try to renew their DHCP leases after a half of the lease time passes. |
| Static Lease | This action will reserve currently assigned IP address for the device in Network -> Interfaces -> Static leases. |
Firewall
This page displays information about the device's firewall. Info is shown of IPv4 and IPv6 traffic. The figure below is an example of the Chains and Rules sections:
| Field name | Description |
|---|---|
| Reset counters | Resets all traffic and packet fields |
| Name | Name of the chain |
| Traffic | Size of traffic that was matched to the chain |
| Packets | Count of packets that were matched to the chain |
| Policy | Policy for traffic entering the zone. |
| Rules | Count of rules the chain has |
| References | Count of times the chain was referenced in other chains |
For more information about specific firewall chain, View button can be pressed. Window like this should pop up:
| Field name | Description |
|---|---|
| Traffic | Size of traffic that was matched to the rule |
| Packets | Count of packets that were matched to the rule |
| Target | Name of the rule (if highlighted you can click it to open modal to it) |
| Protocol | Filters by Internet protocol |
| In | Filters by inbound interface |
| Out | Filters by outbound interface |
| Source | Filters by source address |
| Destination | Filters by destination address |
| Options | Additional iptables options |
| Comment | Filters by comment |
Rules section - displays rules assigned to chains:
To inspect rules, open chain and press on target. You will be redirected to inner chain modal:
Topology
The Topology tab allows scanning of WAN, LAN or both interfaces via arp scan to check active connected devices. After scan it shows how many active devices were found and on which interface.
Topology scan results
This section displays the results of the scan.
| Field name | Description |
|---|---|
| Satus | Satus of scanned device (green color indicates that device is Up/ red - Down) |
| IP Address | IP address of scanned device |
| MAC Address | MAC address of scanned device |
| Interface | The interface through which the device is connected |
| Port | The physical port through which the device is connected |
| Type | Device connection type |
| Download | Download speed between connected device |
| Upload | Upload speed between connected device |
[[Category:{{{name}}} Status section]]







