pcap: implement LINKTYPE_NULL #1416
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implement LINKTYPE_NULL for pcap live and pcap file. From: http://www.tcpdump.org/linktypes.html "BSD loopback encapsulation; the link layer header is a 4-byte field, in host byte order, containing a PF_ value from socket.h for the network-layer protocol of the packet. Note that ``host byte order'' is the byte order of the machine on which the packets are captured, and the PF_ values are for the OS of the machine on which the packets are captured; if a live capture is being done, ``host byte order'' is the byte order of the machine capturing the packets, and the PF_ values are those of the OS of the machine capturing the packets, but if a ``savefile'' is being read, the byte order and PF_ values are not necessarily those of the machine reading the capture file." Feature ticket #1445
inliniac
added
needs testing
needs ticket
Merged
|
Merged through #1454 |
uqs
pushed a commit
to freebsd/freebsd-ports
that referenced
this pull request
May 13, 2015
Backport upstream Pull Request #1416 [1] adding support for LINKTYPE_NULL. [1] OISF/suricata#1416 [2] https://redmine.openinfosecfoundation.org/issues/1445 Submitted by: Bill Meeks <bmeeks8 bellsouth net> (via gnn) git-svn-id: svn+ssh://svn.freebsd.org/ports/head@386186 35697150-7ecd-e111-bb59-0022644237b5
koobs
added a commit
to freebsd/freebsd-ports
that referenced
this pull request
May 13, 2015
Backport upstream Pull Request #1416 [1] adding support for LINKTYPE_NULL. [1] OISF/suricata#1416 [2] https://redmine.openinfosecfoundation.org/issues/1445 Submitted by: Bill Meeks <bmeeks8 bellsouth net> (via gnn)
svmhdvn
pushed a commit
to svmhdvn/freebsd-ports
that referenced
this pull request
Jan 10, 2024
Backport upstream Pull Request #1416 [1] adding support for LINKTYPE_NULL. [1] OISF/suricata#1416 [2] https://redmine.openinfosecfoundation.org/issues/1445 Submitted by: Bill Meeks <bmeeks8 bellsouth net> (via gnn)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement LINKTYPE_NULL for pcap live and pcap file.
From: http://www.tcpdump.org/linktypes.html
"BSD loopback encapsulation; the link layer header is a 4-byte field,
in host byte order, containing a PF_ value from socket.h for the
network-layer protocol of the packet.
Note that
host byte order'' is the byte order of the machine on which the packets are captured, and the PF_ values are for the OS of the machine on which the packets are captured; if a live capture is being done,host byte order'' is the byte order of the machinecapturing the packets, and the PF_ values are those of the OS of
the machine capturing the packets, but if a ``savefile'' is being
read, the byte order and PF_ values are not necessarily those of
the machine reading the capture file."
Feature ticket #1445: https://redmine.openinfosecfoundation.org/issues/1445
Prscript: