Live data from Hacker News

Automatically fixing packet loss on my connection

senryu.pub

11–20 of 40 posts

Re: Automatically fixing packet loss on my connection

#11
post #10

Basically restart the modem by cutting the power every time the connection is flaky. With a very complicated setup. 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.

On the upside, if he manages to brick it, the ISP will replace it and maybe his problem will be fixed.

Re: Automatically fixing packet loss on my connection

#12
post #10

Basically restart the modem by cutting the power every time the connection is flaky. With a very complicated setup. 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.

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.

Re: Automatically fixing packet loss on my connection

#13
post #10

Basically restart the modem by cutting the power every time the connection is flaky. With a very complicated setup. 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.

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.

Could you put a dumb switch between the Vigor and your LAN? And have the Raspberry PI be connected with a fixed IP directly to the modem?

Then you could use WiFi to talk to the PI?

Re: Automatically fixing packet loss on my connection

#14
post #11
post #10

Basically restart the modem by cutting the power every time the connection is flaky. With a very complicated setup. 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.

On the upside, if he manages to brick it, the ISP will replace it and maybe his problem will be fixed.

I’ve never had a device brick by removing the power. The only button on the Vigor 130 immediately cuts the power too: there’s no “shutdown” button.

Re: Automatically fixing packet loss on my connection

#15
post #13

Earlier quoted context omitted.

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.

Could you put a dumb switch between the Vigor and your LAN? And have the Raspberry PI be connected with a fixed IP directly to the modem? Then you could use WiFi to talk to the PI?

Interesting idea! It might be possible; I haven’t touched the thing since first configuring it a few years ago so I’m a bit fuzzy on how exactly the interface works.

Re: Automatically fixing packet loss on my connection

#16
post #11

Earlier quoted context omitted.

On the upside, if he manages to brick it, the ISP will replace it and maybe his problem will be fixed.

I’ve never had a device brick by removing the power. The only button on the Vigor 130 immediately cuts the power too: there’s no “shutdown” button.

Your device’s firmware is not even able to keep a connection up for a few hours. Which is its main function. Do you trust that they tested its code for recovering partitions that were not unmounted cleanly?

Re: Automatically fixing packet loss on my connection

#17
post #6
post #2

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).

Working in IT as a Systems Engineer, My thought process is always first -> Existing solution or Tool, if not exist, Patching existing tools together, if not exist, code our own solution.

Re: Automatically fixing packet loss on my connection

#18
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.

Re: Automatically fixing packet loss on my connection

#20
post #16

Earlier quoted context omitted.

I’ve never had a device brick by removing the power. The only button on the Vigor 130 immediately cuts the power too: there’s no “shutdown” button.

Your device’s firmware is not even able to keep a connection up for a few hours. Which is its main function. Do you trust that they tested its code for recovering partitions that were not unmounted cleanly?

There’s no problem with the device: I triggered the failures/packet loss manually by pulling the cable to test the system. The actual packet loss is intermittent and reasonably rare, and is I suspect a fault at the line level with BT/OpenReach. A&A didn’t provide me with the Vigor 130 btw, it’s my own device. In general I find DrayTek devices very solid and I’ve not had any issues so far when powercycling it over the past few years. It’s pretty much a stateless device, as the actual connection is established from the router on my side of it.
Post reply on HN