Upstream changes:
1.17 Sun 17 Jun 13:10:12 CEST 2018
- bugfix: Dump::Online*: fixed a memleak due to the lack of freeing the pcap filter
in stop() method in N:F:Dump::Online and N:F:Dump::Online2.
1.15 Tue 1 May 09:16:32 CEST 2018
- BUGFIX: Dump::Online2: yes, again. Since some newer version of libpcap
and changes in pcap_dispatch(), we have to call can_read() on the
selectable file descriptor and call pcap_dispatch() only when
there is something to read. Which sounds logical, after all.
- update: copyright notice
-------------------
1.14 Tue Dec 9 19:12:25 CET 2014
- BUGFIX: Dump::Online2: do not eat 100% and do not block for timeoutOnNext
seconds when it is not REALLY needed. We had to remove the
setnonblock option and to use pcap_dispatch i/o pcap_next_ex.
This should be the final bugfix...
There was also an infinite loop condition.
- new: Dump::Online2: maxRunTime() option to stop looping on next() forever
when we do not want. Default to loop forever.
1.13 Sun Dec 2 15:44:14 CET 2012
- BUGFIX: Dump::Online2: in non-blocking mode, we must handle our internal
received frame ring buffer. Many packets were missed because of
that.
1.12 Tue Nov 13 20:15:19 CET 2012
- UPDATE: Dump::Online2: now uses IO::Select to avoid eating 100% CPU
- update: mailing list link
1.11 Sun Nov 11 15:23:04 CET 2012
- bugfix: Dump::Online2 pod
- new: Dump::Online2: support for capture only mode
- new: examples for Dump::Online2
1.10 Wed Sep 12 20:15:09 CEST 2012
- bugfix: Online: use SUPER::next() instead of next()
- update: error messages scheme changed
- update: copyright notice
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
provided in PR pkg/45720.
Net::Frame::Dump is the base class for all dump modules. With them, you can
open a device for live capture, for offline analysis, or for creating a pcap
file.
See Net::Frame::Dump::Offline, Net::Frame::Dump::Online,
Net::Frame::Dump::Writer for specific usage.