#465 seems to be broken again in 10.3.2: I observe route expiration marching down to zero despite receiving RAs from the upstream router with route expirations that should reset the timer; then I see a pid 0 deleted default route via... message; followed a few seconds later by the route being added back.
(Note that I observe this behavior on two networks, Comcast and Spectrum, whose routers send unsolicited RAs at essentially the peak rate permitted by the neighbor discovery RFC 4861 (every three seconds). In each case, there appear to be two routers that both send at the maximum permitted rate, which means clients receiving, in aggregate, RAs more than once every three seconds. It is unclear based on my reading whether this is a misconfiguration or not; but regardless, it works this way on at least two major cable internet providers, which means the software probably just needs to deal.)
#465 seems to be broken again in 10.3.2: I observe route expiration marching down to zero despite receiving RAs from the upstream router with route expirations that should reset the timer; then I see a
pid 0 deleted default route via...message; followed a few seconds later by the route being added back.(Note that I observe this behavior on two networks, Comcast and Spectrum, whose routers send unsolicited RAs at essentially the peak rate permitted by the neighbor discovery RFC 4861 (every three seconds). In each case, there appear to be two routers that both send at the maximum permitted rate, which means clients receiving, in aggregate, RAs more than once every three seconds. It is unclear based on my reading whether this is a misconfiguration or not; but regardless, it works this way on at least two major cable internet providers, which means the software probably just needs to deal.)