If you are willing to throw a bit of money rather than code at the problem:
Ubiquiti has a power strip in beta now that uses statistics from their routers to decide when to power cycle upstream devices.
You can also find "Web Power Switches" (https://www.amazon.com/dp/B0765NCB2L) under $200 that are scriptable, so when a ping to a specific site fails it cycles power to a set of devices.
Ooh I didn’t know about that Ubiquiti strip. I must admit that I didn’t even look about for existing solutions (honestly I just wanted to finally have a use for these plugs I had lying about).
The LAN interface on my ISP mandated box frequently fails along with whatever else is going on with the modem. Even the reset button fails at times, though not as often. Cutting power is literally the only reliable way of addressing the problem
I don't agree that a hard rest is as risky as you are claiming, but even if you are right, who cares? The ISP mandated use of a shiity modem, they made it a black box that can't be troubleshooted and if it breaks then they will just send me a new one at zero cost to me.
You can’t access that web interface from the internal network as the Vigor 130 is not a router. Unless someone has a fancy trick I’m missing I have to disconnect my router and connect a laptop directly to the modem with a fixed IP to access it, unfortunately. The Vigor 130 is really more of a PPPoA to PPPoE converter, or at least, that’s how it’s commonly used.
This seems like an over-engineered, half-assed solution like putting tape on a check engine light.
There is no reason why properly working equipment should need a periodic restart. Either his modem is bad and needs to be replaced or the other end (the DSLAM) is bad and bouncing the link temporarily fixes the problem as a side-effect.
The modem is fine; this is a very intermittent issue, like once every two months, if that, and caused further up the line. In the UK most of our internet infrastructure is, frankly, a bit shit, and maintained by a small subset of companies. These issues occur on every ISP I've had here, as unfortunately most rely on OpenReach's infrastructure.
The reason I chose to automate it is that when I'm away from the house I want the connection to self-repair where possible, and resetting the modem is something basically everyone in the UK has to do sometimes to fix their line (seriously). Yes I could probably have A&A investigate it, but at some point, if it is an identifiable issue, they'd likely have to request an OpenReach engineer to work on something and then there's just the risk of it being made even worse.
As A&A's wiki (https://support.aa.net.uk/Packet_Loss) describes, you can see packet loss at link saturation. There is another option, buffering, which causes high latency. The intermediate device must either buffer (causing "buffer bloat" = increased latency) or drop the packet.
If increased packet loss is occurring seemingly randomly, it could be something on the network is updating/syncing and saturating the link. It could be Steam games, desktop OS updates, mobile device updates, podcast downloading, game console updates, etc.
Yeah I have run into this, notably with the Xbox Live app for Windows, which totally saturates the line and generates something like 15% packet loss reports. However that's a different event to the occasional lower but prolonged packet loss which occurs infrequently and usually on a more idle line; which I believe to almost certainly be caused by something beyond my equipment. Knowing how OpenReach operate (who manage our largest internet infrastructure) it's a fairly safe assumption that it's a fault they've introduced somewhere.
This is incredibly cool! I’ve never worked with Z-Wave plugs before, the only home automation stuff I have set up involves WiFi connected smart plugs running Tasmota. How do you get the Z-Wave ones to talk to your Home Assistant setup?
Won't this cause issues with retraining? You'll end up with a high SNR and lower sync speed, which may solve the packet loss problem but isn't ideal. It would be better to either work out whether the router is the issue and replace it or work out if the line is a problem and get an engineer booked out to investigate it.
It’s quite a peculiar issue when it does happen (which is rarely), in that the only way I’ve found of resolving it myself is by dropping the line at that modem. I’m always hesitant to have the line inspected in the UK because there’s every chance OpenReach will come around and balls it up further.
I’ve been doing this manually for the past couple of years without any negative effects that I’ve seen. I’d say it tends to happen maybe once every two to three months, which makes me think it’s more likely an issue further up the chain. A&A are pretty spry at resolving issues but often I just drop the line myself to sort it out quicker.
[+] [-] mike_d|5 years ago|reply
Ubiquiti has a power strip in beta now that uses statistics from their routers to decide when to power cycle upstream devices.
You can also find "Web Power Switches" (https://www.amazon.com/dp/B0765NCB2L) under $200 that are scriptable, so when a ping to a specific site fails it cycles power to a set of devices.
[+] [-] robotmay|5 years ago|reply
[+] [-] readmodifywrite|5 years ago|reply
[+] [-] lrossi|5 years ago|reply
Cutting power repeatedly a large number of times is a great way of eventually bricking the box.
This modem has an admin web interface. The author could have used it to trigger a restart.
The whole thing could have been automated with just a pi at 100 times less cost, effort and risks.
[+] [-] xnyan|5 years ago|reply
The LAN interface on my ISP mandated box frequently fails along with whatever else is going on with the modem. Even the reset button fails at times, though not as often. Cutting power is literally the only reliable way of addressing the problem
I don't agree that a hard rest is as risky as you are claiming, but even if you are right, who cares? The ISP mandated use of a shiity modem, they made it a black box that can't be troubleshooted and if it breaks then they will just send me a new one at zero cost to me.
[+] [-] robotmay|5 years ago|reply
[+] [-] lrossi|5 years ago|reply
[+] [-] Nextgrid|5 years ago|reply
There is no reason why properly working equipment should need a periodic restart. Either his modem is bad and needs to be replaced or the other end (the DSLAM) is bad and bouncing the link temporarily fixes the problem as a side-effect.
[+] [-] robotmay|5 years ago|reply
The reason I chose to automate it is that when I'm away from the house I want the connection to self-repair where possible, and resetting the modem is something basically everyone in the UK has to do sometimes to fix their line (seriously). Yes I could probably have A&A investigate it, but at some point, if it is an identifiable issue, they'd likely have to request an OpenReach engineer to work on something and then there's just the risk of it being made even worse.
RevK's blog has plenty of interesting anecdotes about the issues with our internet infrastructure here: https://www.revk.uk/search/label/BT
[+] [-] tinus_hn|5 years ago|reply
[+] [-] cyounkins|5 years ago|reply
If increased packet loss is occurring seemingly randomly, it could be something on the network is updating/syncing and saturating the link. It could be Steam games, desktop OS updates, mobile device updates, podcast downloading, game console updates, etc.
[+] [-] robotmay|5 years ago|reply
[+] [-] whoisburbansky|5 years ago|reply
[+] [-] tamu_nerd|5 years ago|reply
[+] [-] kraftman|5 years ago|reply
[+] [-] robotmay|5 years ago|reply
I’ve been doing this manually for the past couple of years without any negative effects that I’ve seen. I’d say it tends to happen maybe once every two to three months, which makes me think it’s more likely an issue further up the chain. A&A are pretty spry at resolving issues but often I just drop the line myself to sort it out quicker.
[+] [-] lupinglade|5 years ago|reply
[+] [-] tareqak|5 years ago|reply
[+] [-] robotmay|5 years ago|reply
[+] [-] dilyevsky|5 years ago|reply