You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until v1.2.2, Sniffnet only supported parsing Ethernet packets.
With #421 support for interfaces based on raw IP and null/loopback was added to Sniffnet, covering the vast majority of possible use cases and scenarios.
This issue is intended to track the necessity to add support for even more link types.
The most important scenario that's still unsupported is, for example, parsing packets from the any interface on Linux, since this particular interface is based on a peculiar link type (known as LINUX_SLL or Linux cooked) that adds to packets a special header.
Ran across this while trying to find out how to parse SLL packets from a pcap file and just wanted to point out for future searchers that this is about "sll" link type, not "ssl" link type.
GyulyVGC
changed the title
Add support for additional link types (e.g., LINUX_SSL)
Add support for additional link types (e.g., LINUX_SLL)
Jan 12, 2024
Ran across this while trying to find out how to parse SLL packets from a pcap file and just wanted to point out for future searchers that this is about "sll" link type, not "ssl" link type.
Until v1.2.2, Sniffnet only supported parsing Ethernet packets.
With #421 support for interfaces based on raw IP and null/loopback was added to Sniffnet, covering the vast majority of possible use cases and scenarios.
This issue is intended to track the necessity to add support for even more link types.
The most important scenario that's still unsupported is, for example, parsing packets from the
any
interface on Linux, since this particular interface is based on a peculiar link type (known asLINUX_SLL
or Linux cooked) that adds to packets a special header.A full list of link types is available here.
Originally posted by @GyulyVGC in #30 (comment)
The text was updated successfully, but these errors were encountered: