Package: tcpreplay
Version: 4.4.0-1
Severity: wishlist
Tags: patch

Dear maintainer,

when configuring tcpreplay the configure script provides the following
warning:

| checking for libdnet... no
| configure: WARNING: libdnet not found, disabling fragroute feature

and then the following configuration results:

| ##########################################################################
|              TCPREPLAY Suite Configuration Results (4.4.0)
| ##########################################################################
| libpcap:                    /usr (>= 0.9.6)
| PF_RING libpcap             no
| libdnet:                    no
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| autogen:                    /usr/bin/autogen (5.18.16)
| Use libopts tearoff:        yes
| 64bit counter support:      yes
| tcpdump binary path:        /usr/bin/tcpdump
| fragroute support:          no
| tcpbridge support:          yes
| tcpliveplay support:        yes
| 
| Supported Packet Injection Methods (*):
| Linux TX_RING:              no
| Linux PF_PACKET:            yes
| BSD BPF:                    no
| libdnet:                    no
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| pcap_inject:                yes
| pcap_sendpacket:            yes **
| pcap_netmap                 no
| Linux/BSD netmap:           no
| Tuntap device support:      yes

(cf. e.g. 
<https://buildd.debian.org/status/fetch.php?pkg=tcpreplay&arch=amd64&ver=4.4.0-1&stamp=1644097626&raw=0>)


However, merely adding libdumbnet-dev to B-D like this here

| diff -Nru tcpreplay-4.4.0/debian/control tcpreplay-4.4.0/debian/control
| --- tcpreplay-4.4.0/debian/control      2022-01-31 23:39:12.000000000 +0100
| +++ tcpreplay-4.4.0/debian/control      2022-03-04 21:55:20.000000000 +0100
| @@ -8,6 +8,7 @@
|      autogen,
|      libpcap0.8-dev,
|      tcpdump,
| +    libdumbnet-dev,
|  Priority: optional
|  Rules-Requires-Root: no
|  Section: net

and then rebuilding results in

| checking for libdnet... /usr
| checking for dumbnet.h... yes

and then

| ##########################################################################
|              TCPREPLAY Suite Configuration Results (4.4.0)
| ##########################################################################
| libpcap:                    /usr (>= 0.9.6)
| PF_RING libpcap             no
| libdnet:                    /usr   1.14 (libdumbnet)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| autogen:                    /usr/bin/autogen (5.18.16)
| Use libopts tearoff:        yes
| 64bit counter support:      yes
| tcpdump binary path:        /usr/bin/tcpdump
| fragroute support:          yes
| tcpbridge support:          yes
| tcpliveplay support:        yes
| 
| Supported Packet Injection Methods (*):
| Linux TX_RING:              no
| Linux PF_PACKET:            yes
| BSD BPF:                    no
| libdnet:                    yes
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| pcap_inject:                yes
| pcap_sendpacket:            yes **
| pcap_netmap                 no
| Linux/BSD netmap:           no
| Tuntap device support:      yes

i.e. enabling fragroute support and the libdnet injection method.

The binary package debdiff then merely indicates the additional
dependency on libdumbnet1:

| Control files of package tcpreplay: lines which differ (wdiff format)
| ---------------------------------------------------------------------
| Depends: libc6 (>= 2.33), {+libdumbnet1 (>= 1.8),+} libpcap0.8 (>= 0.9.8)
| Installed-Size: [-1900-] {+1950+}
| Version: [-4.4.0-1-] {+4.4.0-1.1+}


Please consider whether it's worthwhile to include libdumbnet support
into tcpreplay, thanks.


Oh, JFTR, libdnet was renamed in Debian to libdumbnet due to a naming
conflict with a DECnet library, but luckily tcpreplay knows how to deal
with that, see above. The project lay dormant for quite some time but
now found a new upstream.
Disclaimer: I am the new libdumbnet maintainer, so of course I am biased
on whether libdumbnet should be used.

Cheers,
Flo

Attachment: signature.asc
Description: PGP signature

Reply via email to