Adding upstream version 1.44.3.upstream/1.44.3upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 36 insertions, 0 deletions

diff --git a/health/guides/net/interface_inbound_errors.md b/health/guides/net/interface_inbound_errors.md
new file mode 100644
index 00000000..6c8bcfcd
--- /dev/null
+++ b/health/guides/net/interface_inbound_errors.md
@@ -0,0 +1,36 @@
+- Troubleshoot errors related to network congestion
+
+Network congestion can cause packets to be dropped, leading to interface inbound errors. To determine if congestion is the issue, you can monitor the network for any signs of excessive workload or high utilization rates.
+
+1. Use `ifconfig` to check the network interface utilization:
+   ```
+   ifconfig <your_interface>
+   ```
+
+2. Check the network switch/router logs for any indication of high utilization, errors or warnings.
+
+3. Use monitoring tools like `iftop`, `nload`, or `iptraf` to monitor network traffic and identify any bottle-necks or usage spikes.
+
+If you find that congestion is causing the inbound errors, consider ways to alleviate the issue including upgrading your network infrastructure or load balancing the traffic.
+
+- Troubleshoot errors caused by faulty network equipment
+
+Faulty network devices, such as switches and routers, can introduce errors in packets. To identify the cause, you should review the logs and statistics of any network devices in the path of the communication between the sender and this system.
+
+1. Check the logs of the network equipment for any indications of errors, problems or unusual behavior.
+
+2. Review the error counters and statistics of the network equipment to identify any trends or issues.
+
+3. Consider replacing or upgrading faulty equipment if it is found to be responsible for inbound errors.
+
+- Troubleshoot errors caused by software or configuration issues
+
+Incorrect configurations or software issues can also contribute to interface inbound errors. Some steps to troubleshoot these potential causes are:
+
+1. Review the system logs for any errors or warnings related to the network subsystem.
+
+2. Ensure that the network interface is configured correctly, and proper drivers are installed and up-to-date.
+
+3. Examine the system's firewall and security settings to verify that there are no inappropriate blockings or restrictions that may be causing the errors.
+
+In conclusion, by following these troubleshooting steps, you should be able to identify and resolve the cause of interface inbound errors on your FreeBSD system. Remember to monitor the situation regularly and address any new issues that may arise to ensure a stable and efficient networking environment.
\ No newline at end of file