From: W.F. Y. <wen...@mo...> - 2016-07-12 15:48:57
|
Richard, Here i got a minor suspect issue: Role: slave node Delay Mechanism: E2E Scenario: slave sent a delay_req to master, and duration period of issuing delay_req for next time is determined by set_tmo_random(), it is a random value. If the slave node send the delay_req again prior to receiving the first delay_resp from master, the first delay_resp will be discarded due to having previous sequence number Anyway, it does not bring big impact. *Best Regards* *Yang Wenfeng* On Tue, Jul 12, 2016 at 7:30 PM, Richard Cochran <ric...@gm...> wrote: > Dear linuxptp users and developers, > > I am planning to release version 1.7 in one week, without any major > new features, in order to fix the regressions in version 1.6. The two > bugs that need fixing are: > > - time stamping in one step P2P mode > - bogus announce timer on the UDS interface > > If you know of any other problems with v1.6 or in the current git > head, please let me know right away. > > Thanks, > Richard > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users > |