From cee10b5dc66b1bdebcb4dfcb2723e4be7df977d1 Mon Sep 17 00:00:00 2001 From: Jon Siwek Date: Wed, 23 Sep 2020 22:52:35 -0700 Subject: [PATCH] Fix a Sphinx warning about misformatted packet analyzer comment --- scripts/base/packet-protocols/null/main.zeek | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/scripts/base/packet-protocols/null/main.zeek b/scripts/base/packet-protocols/null/main.zeek index e1aff33dcd..650ae97448 100644 --- a/scripts/base/packet-protocols/null/main.zeek +++ b/scripts/base/packet-protocols/null/main.zeek @@ -11,14 +11,13 @@ redef PacketAnalyzer::ROOT::dispatch_map += { [DLT_NULL] = PacketAnalyzer::DispatchEntry($analyzer=PacketAnalyzer::ANALYZER_NULL) }; +## From the Wireshark Wiki: AF_INET6ANALYZER, unfortunately, has different +## values in {NetBSD,OpenBSD,BSD/OS}, {FreeBSD,DragonFlyBSD}, and +## {Darwin/macOS}, so an IPv6 packet might have a link-layer header with 24, 28, +## or 30 as the ``AF_`` value. As we may be reading traces captured on platforms +## other than what we're running on, we accept them all here. redef dispatch_map += { - [2] = PacketAnalyzer::DispatchEntry($analyzer=PacketAnalyzer::ANALYZER_IPV4), - - ## From the Wireshark Wiki: AF_INET6ANALYZER, unfortunately, has different values in - ## {NetBSD,OpenBSD,BSD/OS}, {FreeBSD,DragonFlyBSD}, and {Darwin/Mac OS X}, so an IPv6 - ## packet might have a link-layer header with 24, 28, or 30 as the AF_ value. As we - ## may be reading traces captured on platforms other than what we're running on, we - ## accept them all here. + [2] = PacketAnalyzer::DispatchEntry($analyzer=PacketAnalyzer::ANALYZER_IPV4), [24] = PacketAnalyzer::DispatchEntry($analyzer=PacketAnalyzer::ANALYZER_IPV6), [28] = PacketAnalyzer::DispatchEntry($analyzer=PacketAnalyzer::ANALYZER_IPV6), [30] = PacketAnalyzer::DispatchEntry($analyzer=PacketAnalyzer::ANALYZER_IPV6)