Libnet is a high-level API (toolkit) allowing the application programmer to
construct and inject network packets. It provides a portable and simplified
interface for low-level network packet shaping, handling and injection.
Libnet hides much of the tedium of packet creation from the application
programmer such as multiplexing, buffer management, arcane packet header
information, byte-ordering, OS-dependent issues, and much more.
Libnet features portable packet creation interfaces at the IP layer
and link layer, as well as a host of supplementary and complementary
functionality.
Using libnet, quick and simple packet assembly applications can be whipped up
with little effort. With a bit more time, more complex programs can be written
(Traceroute and ping were easily rewritten using libnet and libpcap).
Libnet is distrubuted under the BSD license.
Author: Mike D. Schiffman <mike at infonexus dot com>
WWW: http://www.packetfactory.net/projects/libnet/
===> The following configuration options are available for libnet-1.1.6:
DOCS=on: Build and/or install documentation
EXAMPLES=on: Build and/or install examples
====> Options available for the radio LINK: you can only select none or one of them
SNOOP=off: link layer (snoop.h)
PF=off: link layer pf
BPF=on: link layer bpf
===> Use 'make config' to modify these settings
- update to 1.1.5
- set LATEST_LINK
- use OPTIONS
- use PLIST_SUB to get versions out pkg-plist
- fix build in jail without /dev/bpf
- take maintainership
-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22.
-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.
It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.
With help: marcus and kwm
Pointyhat-exp: a few times by pav
Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and
a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by: marcus
Approved by: portmgr
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
- Patch net/libnet* to versioned libraries and header files, so they can
coexist
PR: ports/103861
Submitted by: alepulver
Tested by: pointyhat
With hat: portmgr
libnet update:
- move 1.0 obsoleted version to net/libnet10
net/libnet is latest Stable Version
net/libnet is latest Beta Version
- Fix all depended ports with a new DEPENDS scheme
- While I'm here fix security/yersinia build on 4.x
(getopt_long and ncurses issues)
PR: ports/85519 (based on)
Submitted by: Stas Yakovlev <stas.yakovlev_at_gmail.com>
- Update to 1.1.1
- Removed dependency on automake and autoconf
- Use PKGNAMESUFFIX
- Use CONFLICTS to prevent installation over stable version
- Install examples and documentation
- Use DOCSDIR/EXAMPLESDIR
- Reword COMMENT and pkg-descr, add Author tag
PR: 54421
Submitted by: sergei
Approved by: maintainer timeout (5 months)
Add libnet-devel
libnet-devel will maintain libnet-1.1.x. A limited number of ports currently
support or will require libnet-1.1.x in the future. The API is not backwards
compatible. Unfortunately many ports still require libnet-1.0.x and do not
support the new API (and may never support it). libnet-devel will fill the
gap until the API change settles out and 1.0.x is fully deprecated.
