mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
Add VXLAN packet analyzer, disable old analyzer
This commit is contained in:
parent
cbb0bcd49c
commit
05574ecce1
22 changed files with 194 additions and 29 deletions
|
@ -23,3 +23,4 @@
|
|||
@load base/packet-protocols/iptunnel
|
||||
@load base/packet-protocols/ayiya
|
||||
@load base/packet-protocols/geneve
|
||||
@load base/packet-protocols/vxlan
|
||||
|
|
1
scripts/base/packet-protocols/vxlan/__load__.zeek
Normal file
1
scripts/base/packet-protocols/vxlan/__load__.zeek
Normal file
|
@ -0,0 +1 @@
|
|||
@load ./main
|
20
scripts/base/packet-protocols/vxlan/main.zeek
Normal file
20
scripts/base/packet-protocols/vxlan/main.zeek
Normal file
|
@ -0,0 +1,20 @@
|
|||
module PacketAnalyzer::VXLAN;
|
||||
|
||||
export {
|
||||
# There's no indicator in the VXLAN packet header format about what the next protocol
|
||||
# in the chain is. All of the documentation just lists Ethernet, so default to that.
|
||||
const default_analyzer: PacketAnalyzer::Tag = PacketAnalyzer::ANALYZER_ETHERNET &redef;
|
||||
|
||||
## The set of UDP ports used for VXLAN traffic. Traffic using this
|
||||
## UDP destination port will attempt to be decapsulated. Note that if
|
||||
## if you customize this, you may still want to manually ensure that
|
||||
## :zeek:see:`likely_server_ports` also gets populated accordingly.
|
||||
const vxlan_ports: set[port] = { 4789/udp } &redef;
|
||||
}
|
||||
|
||||
redef likely_server_ports += { vxlan_ports };
|
||||
|
||||
event zeek_init() &priority=20
|
||||
{
|
||||
PacketAnalyzer::register_for_ports(PacketAnalyzer::ANALYZER_UDP, PacketAnalyzer::ANALYZER_VXLAN, vxlan_ports);
|
||||
}
|
Loading…
Add table
Add a link
Reference in a new issue