mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
Include in Jan's AF_PACKET plugin as builtin plugin
This has come up a few times and the motivation is mainly better "first timer" experience with Zeek. Concretely, if one wants to run a Zeek cluster with multiple workers and reasonable load balancing on Linux, AF_PACKET is a decent start. Without AF_PACKET support being built into Zeek, however, a new user's next experience is that of setting up a development environment in order to compile an external plugin (think compiler, kernel headers, zkg, ...). Only to get what could be termed basic functionality. This is using the ZEEK_INCLUDE_PLUGINS infrastructure. I've used the all upper case spelling of AF_PACKET in the help output because it seems everyone else references/writes it like that. I think we should also write it like that in the docs.
This commit is contained in:
parent
a4ad4a34b2
commit
0bc7d0905e
12 changed files with 88 additions and 3 deletions
|
@ -577,6 +577,16 @@ endif()
|
|||
# Tell the plugin code that we're building as part of the main tree.
|
||||
set(ZEEK_PLUGIN_INTERNAL_BUILD true CACHE INTERNAL "" FORCE)
|
||||
|
||||
if ( ${CMAKE_SYSTEM_NAME} MATCHES Linux )
|
||||
if ( NOT DISABLE_AF_PACKET )
|
||||
if ( NOT AF_PACKET_PLUGIN_PATH )
|
||||
set(AF_PACKET_PLUGIN_PATH ${CMAKE_SOURCE_DIR}/auxil/zeek-af_packet-plugin)
|
||||
endif ()
|
||||
|
||||
string(APPEND ZEEK_INCLUDE_PLUGINS ";${AF_PACKET_PLUGIN_PATH}")
|
||||
endif ()
|
||||
endif ()
|
||||
|
||||
set(DEFAULT_ZEEKPATH .:${ZEEK_SCRIPT_INSTALL_PATH}:${ZEEK_SCRIPT_INSTALL_PATH}/policy:${ZEEK_SCRIPT_INSTALL_PATH}/site:${ZEEK_SCRIPT_INSTALL_PATH}/builtin-plugins)
|
||||
|
||||
if ( NOT BINARY_PACKAGING_MODE )
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue