How to trigger PPPoE client restart?

[unixadmin]

Someone from the ISP brought a new modem today, they are transitioning us from ADSL to VDSL... and now I am using PPPoE client on the Netduma. But the ISP forces a line reset every 24 hours, just like they did with ADSL.

 

Every time the modem resets Netduma loses connection to the Internet permanently. No matter how many times I switch between "Disable" and "Enable" for PPPoE, no matter if I submit Apply or not. I have to restart the Netduma and modem several times over until they decide to cooperate again.  Doing this in the middle of a game session is driving me nuts.

 

 

I was hoping there is a "helper script" somewhere in the cgi-bin that can be called directly that would trigger pppoe-stop, then I would call to trigger start? 

 

 

Also maybe the client configuration could be improved for such situations? There are ppp settings like maxfail and persist that could help with automatic reconnections, unlimited attempts.

[Netduma Fraser]

There is no way to at the moment. DumaOS will be out soon, would you like to be beta tester in order to test that feature? As we will include a solution for it, you can test that specific one, maybe we can do auto reset or set a timer etc.

[unixadmin]

Thanks for the offer, but today I'm having another problem entirely which makes the first

one seem trivial, item for a wishlist more than a feature list.

 

I wanted to mention it in another post, but since I'm here...

 

PPPoE was disconnecting every few minutes, as I'm playing a multiplayer game. Here's a log: 

 

Start, Stop, Downloaded, Uploaded, PPPoE duration

21.9. 16:02:26     21.9. 16:22:26     196,31 MB     22,34 MB     0 h 20 m 0 s
21.9. 16:22:57     21.9. 16:31:23     85,57 MB     20,55 MB     0 h 8 m 26 s
21.9. 16:31:53     21.9. 16:33:24     0,57 MB     0,20 MB     0 h 1 m 31 s 
 

...but I noticed a pattern when it would happen.  I was pinging google.com continuosly as I was playing

and every time the disconnect happened there was a huge ping spike (from usual 25ms), to between

300ms ~ 900ms.

 

That in turn was happening as the uplink was completely saturated because of what was happening in the game.

I trade a kill, rockets explode, lots is happening on the screen.... and that's when Destiny completely hogs the uplink --

which is very poor in my case, middle of the day ISP delivery 650kbit/s out of it and yet Destiny easily needs double

that in such hectic situations because of its P2P network model as I have to talk to every player at once.

 

(You can also see why I can't really use congestion control any more aggressively to limit ping spikes from happening

in the first place,  because it would make the game perform worse and hit detection wouldn't reliably work for me.)

 

 

This was a very long introduction, but I had to go through it to say the following few things:

 

- This never happened when pppoe was on the modem (maybe their ppp configuration

is more tolerant of losses in communication to the server?)

 

- My line is supposed to be switched to VDSL in the next 10 days providing me with 10Mbit/s

uplink and that would probably make this a non issue for *me*,  so I'm not really asking for

support/help here at this moment.

 

- But maybe there is something to be learned about PPPoE client configuration for low bandwidth

connections. Are you able to retrieve syslog messages from a Netduma if remote support is

enabled? (Maybe that has some clues from pppd about timeouts, or what was really happening

during that time... for all I know I could be wrong and ETH port link went down several times over.)