Large af_packet buffer size == missing logs

Mark Gardner <[email protected]>
Newsgroups gmane.comp.security.detection.bro
Message-ID <CAG=_CgCpwBLLA8fEC6T02teGFnezsSx7gNjXnmxeq8x4obQ7aA@mail.gmail.com>
In an effort to reduce capture loss, the af_packet buffer size was
increased from the default to 2GB in node.cfg using
"af_packet_buffer_size=2*1024*1024*1024". The capture loss afterwards was
zero but many of the other logs also went missing, including conn.log.

Going to 1GB with "af_packet_buffer_size=1*1024*1024*1024" and the missing
logs started being collected again. The capture loss, while better, was
still up to 10%.

Choosing the middle with 1.5GB via "af_packet_buffer_size=1536*1024*1024"
(seems it has to be integer calculations) and several of the logs including
conn.log went missing again.

The sensors all have 128 GB RAM for only 15 workers so memory should not be
an issue. But it seems something goes wrong while trying to utilize the
wealth of RAM.

Any idea what I am doing wrong?

_______________________________________________
Zeek mailing list
[email protected]
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/zeek
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.