https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14306

            Bug ID: 14306
           Summary: Export time shift packets into new pcapng file.
           Product: Wireshark
           Version: 2.4.1
          Hardware: x86-64
                OS: Windows 10
            Status: UNCONFIRMED
          Severity: Enhancement
          Priority: Low
         Component: Extras
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: anderse...@gmail.com
  Target Milestone: ---

Build Information:
TShark (Wireshark) 2.4.1 (v2.4.1-0-gf42a0d2b6c)

Copyright 1998-2017 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with
SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS 3.4.11, with Gcrypt
1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0, with LZ4, with
Snappy, with libxml2 2.9.4.

Running on 64-bit Windows 10, build 16299, with       Intel(R) Core(TM)
i7-3632QM CPU @ 2.20GHz (with SSE4.2), with 16266 MB of physical memory, with
locale English_United States.1252, with WinPcap version 4.1.3 (packet.dll
version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
with GnuTLS 3.4.11, with Gcrypt 1.7.6.

Built using Microsoft Visual C++ 14.0 build 24215
--
Need to be able to perform 'time shift' from captured NTP packets to ALL
packets and then save back into another pcap/ng file. Currently I can't save
changed packets into another pcap/ng file for archiving? I've also tried to
save as "K12" format, but when I open the <k12.txt> file into Wireshark, the
changed Frame times resort back to a DTG of 1999-12-31 and bogus date? Is this
possible?
 If so, how can I modify the frame times and save as a new modified pcap/ng
file?

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to