mirror of
https://github.com/opnsense/src.git
synced 2026-06-03 22:02:58 -04:00
26f21a6494
Changes: https://git.tcpdump.org/libpcap/blob/bbcbc9174df3298a854daee2b3e666a4b6e5383a:/CHANGES Reviewed by: emaste Obtained from: https://www.tcpdump.org/release/libpcap-1.10.5.tar.gz Sponsored by: The FreeBSD Foundation (cherry picked from commit afdbf109c6a661a729938f68211054a0a50d38ac) (cherry picked from commit ecb75be376a3e18d3e4836b6ee07015264784694) (cherry picked from commit f0bcebe67ef6cf9f104535d6cd9f151c1b61dd6a) (cherry picked from commit 34aa6f2c2db5cc9655f201a1ef01adbb9fb484d5)
28 lines
1.2 KiB
Text
28 lines
1.2 KiB
Text
TODO list for libpcap
|
|
=======================
|
|
|
|
Important stuff (to be done before the next release)
|
|
---------------
|
|
|
|
General
|
|
|
|
- The source files should be better documented. There is no official
|
|
design guideline for what is done where. There should be a common coding
|
|
style (okay, you can guess that by looking at the code) and a guide for
|
|
what needs to be documented.
|
|
|
|
Less urgent items
|
|
-----------------
|
|
|
|
- Better documentation and cleanup of the interface. I am seeing a few
|
|
problems at the first glance which needs fixing:
|
|
+ not very well suited for interactive programs (think ethereal). There
|
|
should be a way for the application to get a file descriptor which it
|
|
has to monitor and a callback in pcap which has to be called on
|
|
activity (XXX - "pcap_fileno()" handles the first part, although
|
|
"select()" and "poll()" don't work on BPF devices on most BSDs, and
|
|
you can call "pcap_dispatch()" as the dispatch routine after putting
|
|
the descriptor into non-blocking mode)
|
|
+ too many functions. There are a lot of functions for everything which
|
|
violates the KISS principle. Why do we need pcap_strerror, pcap_perror
|
|
and pcap_geterr?
|