[FS#964] odhcpdIPv6 node(Win 10) stops sending Router Solicitation but it still receives RAs from LEDE

[LEDE Bugs]

The following task has a new comment added:

FS#964 - odhcpdIPv6 node(Win 10) stops sending Router Solicitation but it still receives RAs from LEDE
User who did this - Eric Luehrsen (EricLuehrsen)

----------
@Hans Dedecker, you have hit it right on the head. There is no one specification limit, but rather a set of parametric relationships in a __system__. There are also simple matters of reality. A certain too fast RA represents congestion or link waste. It is not possible to robustly maintain a link if the information for the link is not refreshed at least 3 times in its link life (an RA may go missing or be garbled). At 20-40 odd seconds, it would be further ridiculous for a client to RA solicit as a fall-back-measure after the routers half-life and get things more in a knot. This is why I said "implied best practices," because the __system__ of relationships just doesn't work well any other way.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=964#comment3296