Dear Kristian,
Your watchdog script gave me the idea to try something similar. I have
now made a script with the following line:
logread -f | awk '/transmit timed out/ {system("/etc/init.d/network restart")}'
Which is continuously running in the background. Is this similar to
how your script operates? The network restart command does take a bit
to complete, so I was wondering if there is a command that also
restores connectivity but would result in a shorter break than this
current command does. Thank you!
Best regards,
Jaap
On Fri, Aug 7, 2020 at 10:09 AM Kristian Evensen
<kristian.even...@gmail.com> wrote:
>
> Hello,
>
> On Thu, Aug 6, 2020 at 1:44 PM Jaap Buurman <jaapbuur...@gmail.com> wrote:
> > However, on this mailing list a user by the name of Kristian claims
> > that disabling flow control helps fix this problem, as can be read
> > here:
> > https://lists.openwrt.org/pipermail/openwrt-devel/2017-November/009882.html
>
> My patch unfortunately does not solve the problem, as I can still see
> the timeout error. However, by disabling flow control, the frequency
> of the error is decreased to the point where it almost never happens
> (even on devices where I would frequently see the error). In order to
> deal with the remaining timeout cases, I wrote a small watchdog script
> that checks syslog for the timeout message and restarts networking if
> the error occurs. A restart has always been able to recover networking
> (at the cost of a small interruption).
>
> Kristian
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
