Experienced an unusual disruption, attempting to understand it later.
Experienced an unusual disruption, attempting to understand it later.
Last night the internet went down. It was windy, so I checked the modem's status page to see if it dropped the signal or had weak reception. After a power cycle, nothing changed—lights were normal. On another device, Wi-Fi was active but no internet access or network connection. I rebooted the router/AP without results. I tried swapping it out, which restored Wi-Fi and allowed me to view the router settings over Wi-Fi. Wired devices still couldn’t connect, and I couldn’t access the modem’s status page. I contacted my ISP to request a reboot signal, which worked—now the new router showed internet through Wi-Fi, while wired devices remained offline and unseen on the network. Checking my IP settings revealed that Windows devices were getting static IPs (169.xxx), indicating a DHCP failure. I systematically tested each network device, changed switches, unplugged cables, and finally switched to a PC running NicehashOS. Rebooting it resolved the issue. I’m curious about what might have caused the DHCP failure on a PC using NHOS (Tiny Core Linux). It would help to understand what could have been fixed by a reboot. This was a frustrating process, but I’m now better prepared to avoid similar problems.
When a client crashes or freezes, or if a faulty service runs, network issues can arise. A failing network card may cause excessive traffic, overwhelming devices and disrupting services like DHCP. If bandwidth is fully used on a 1Gig link, the switch or router can become saturated, leading to lost connections. This situation often results in a rogue client generating massive broadcast traffic, overwhelming the network and causing services to fail. Windows clients may fall back to alternative peer-to-peer settings, highlighting the problem. Such incidents are uncommon at home but require prompt attention to prevent significant communication breakdowns.
Thanks for the clear breakdown. It seems the problem might be software-related, so I’d need to connect a gigabit NIC via NVME on the motherboard or consider a replacement.
I've faced this problem on an old desktop running Ubuntu Server. The hardware seems fine, but the kernel got unstable and started sending random data over the network. I lost contact with other servers for a few days, so it wasn't just a hardware issue. Sometimes it's related to drivers or services.
This setup makes sense given the mining rig's typical uptime between restarts. Running it lightly now seems sensible since boosting hardware stability isn't likely. The software issues probably stem from the firmware, so checking BIOS settings for scheduled reboots could help. Alternatively, using a power-saving timer might work well since the machine restarts automatically after power loss.