[Oisf-devel] [COMMIT] OISF branch, master-1.3.x, updated. suricata-1.3.5-14-gc5842e0

noreply at openinfosecfoundation.org noreply at openinfosecfoundation.org
Thu Feb 21 10:15:43 UTC 2013

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "OISF".

The branch, master-1.3.x has been updated
       via  c5842e0b8855503cc8439c3894cae9cb4fb0c887 (commit)
       via  c3afde71dbce242d593dc08a96e1de88aa77881e (commit)
      from  b35a5bc0273cd4959c74b2ba8e9e60f56f602db3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c5842e0b8855503cc8439c3894cae9cb4fb0c887
Author: Eric Leblond <eric at regit.org>
Date:   Thu Dec 13 16:49:37 2012 +0100

    log-pcap: don't limit snaplen.

commit c3afde71dbce242d593dc08a96e1de88aa77881e
Author: Eric Leblond <eric at regit.org>
Date:   Fri Feb 15 12:10:25 2013 +0100

    pcap: set snaplen to MTU if available.
    Main objective of this patch is to use a dynamic snaplen to avoid
    to truncate packet at the currently fixed snaplen.
    It set snaplen to MTU length if the MTU can be retrieved. If not, it
    does set the snaplen to 1518 (previous default). This approach is more
    conservative than the one used in master branch code.
    libpcap is trying to use mmaped capture and setup the ring by using buffer_size
    as the total memory. It also use "rounded" snaplen as frame size. So if we set
    snaplen to MTU when available we are optimal regarding the building of the ring.


Summary of changes:
 src/log-pcap.c    |    2 +-
 src/source-pcap.c |    9 ++++++++-
 suricata.yaml.in  |    5 ++++-
 3 files changed, 13 insertions(+), 3 deletions(-)


More information about the Oisf-devel mailing list