Re: [PATCH iproute2] ip monitor: Fixed printing timestamp few times | netdev | Ratatoskr

[PATCH iproute2] ip monitor: Fixed printing timestamp few times · Vadim Kochan <hidden> · 2014-11-30
Re: [PATCH iproute2] ip monitor: Fixed printing timestamp few times · Stephen Hemminger <stephen@networkplumber.org> · 2014-12-03
Re: [PATCH iproute2] ip monitor: Fixed printing timestamp few times · <hidden> · 2014-12-03
Re: [PATCH iproute2] ip monitor: Fixed printing timestamp few times · Stephen Hemminger <stephen@networkplumber.org> · 2014-12-03
Re: [PATCH iproute2] ip monitor: Fixed printing timestamp few times · <hidden> · 2014-12-03
Re: [PATCH iproute2] ip monitor: Fixed printing timestamp few times · Vadim Kochan <hidden> · 2014-12-04

Re: [PATCH iproute2] ip monitor: Fixed printing timestamp few times

From: <hidden>
Date: 2014-12-03 17:51:37

On Wed, Dec 03, 2014 at 09:47:31AM -0800, Stephen Hemminger wrote:

On Wed, 3 Dec 2014 19:11:26 +0200
vadim4j@gmail.com wrote:

quoted

I think it was caused by RTM_NEWNDUSEROPT which was sent by router.
So in this case the message will be skipped with printed timestamp.

Can that be decoded? it might be useful.

Sorry, you mean how it can be reproduced by clean scenario?