Hey, guys and gals I've been having stability issues with my DSL. I might have found a bug or located something that could improve the way PPPoE connections are handled on Tomato. Here is the problem. The modem sometimes resyncs. This causes the router to disconnect PPPoE erratically. This is fine under 99% of the connections. However, I've detected an issue in this tomato that's bugging me. If the DSL connection re-establishes the router can maintain the same IP and won't drop the PPPoE connection unless the "lcp echo fails -- "Tolerance to unanswered echo-requests" exceeds the user defined perimeters. I know these can be raised using this commands but at the cost of the router not disconnecting/reconnecting with the connection is really down (unable to self correct) pppoe_lei=30 # lcp echo interval -- "Interval between LCP echo-requests"; default is 30 pppoe_lef=5 # lcp echo fails -- "Tolerance to unanswered echo-requests"; default is 5 The problem I'm having is the tolerance isn't based around consecutive failures. If this is set to the default of five and the connection drops 4 request at 5 am then ten hours later drops one more it'll incorrectly disconnect on the first unanswered echo request instead of restarting at one. What this setting should be doing IMHO is counting consecutive failed request. From my understanding the original tomato version tolerance would restart the count and disconnect/reconnect based on the last successful echo request. It would maintain the PPPoE connection with a big lag spike. Is there another way to bypass this problem through a script or something so every few hours the tolerance gets reset without the errors stacking? This way the router can maintain/tolerate a few failed request that aren't consecutive. While detecting when the connection really need to be reestablished?