Better yet, post a link to the capture (google drive/dropbox) so it can be evaluated.
On Wed, Apr 3, 2019 at 11:11 PM Simon Barber via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > The timeline will not show up unless hardware timestamps are present for > *all* frames in the capture, and there are no large negative jumps in time. > Where does the capture file you are using come from? > > Simon > > On Wed, Apr 3, 2019 at 1:17 PM Do m <teammclaughl...@gmail.com> wrote: > >> Greetings... >> >> I came across this: >> https://meraki.cisco.com/blog/2019/02/wireshark-where-did-the-time-go/ >> >> Running wireshark 3.0 on Win10... can't seem to get the wireless timeline >> to show up. Am I missing something obvious (apart from configuring the >> dissector preferences to enable the experimental feature?) >> >> -- >> regards, >> -doug >> >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> Archives: https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org >> ?subject=unsubscribe > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
