In the past i sometimes used ngrep successfully for ppp0. Now it fails with hafi@e675 ~ $ sudo ngrep -x -d ppp0 interface: ppp0 (78.49.14.82/255.255.255.255) fatal: unsupported interface type 113 I have found a related bug for debian which may be helpful: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546596 Reproducible: Always
Apparently fixed in Debian's ngrep_1.45.ds2-7.
So, according to that Debian bug, the fix for us would be this: Index: ngrep-1.45-r2.ebuild =================================================================== RCS file: /var/cvsroot/gentoo-x86/net-analyzer/ngrep/ngrep-1.45-r2.ebuild,v retrieving revision 1.8 diff -u -B -r1.8 ngrep-1.45-r2.ebuild --- ngrep-1.45-r2.ebuild 26 May 2010 16:31:12 -0000 1.8 +++ ngrep-1.45-r2.ebuild 15 Sep 2010 02:58:03 -0000 @@ -29,7 +29,7 @@ src_configure() { econf --with-dropprivs-user=ngrep \ - --with-pcap-includes="${EPREFIX}"/usr/include \ + --with-pcap-includes="${EPREFIX}"/usr/include/pcap \ $(use_enable pcre) \ $(use_enable ipv6) }
Created attachment 256638 [details] Modified ebuild
This looks like it resolves to a configure/ebuild a ebuild solution. But the ticket is assigned to me -- what would you guys like me to do?
Maybe, you can put the ebuild into the main branch.
Nobody has yet confirmed that the patch in comment #2 actually works.
I confirm that this Patch/eBuild -r3 works for me on x86
Arch teams, please test and mark stable: =net-analyzer/ngrep-1.45-r3 Target KEYWORDS="alpha amd64 arm hppa ia64 ppc ppc64 s390 sh sparc x86"
builds on amd64/arm/sparc, but shouldn't we wait 30 days?
(In reply to comment #9) > builds on amd64/arm/sparc, but shouldn't we wait 30 days? The fix solves a problem with the current stable. So I vote NO. The problem was there all along with newer libpcap versions, so this is rather urgent.
The 30 days is a guide line, not a hard rule.
x86 done. Thanks everyone.
amd64 ok
alpha/arm/ia64/s390/sh/sparc stable
Stable for HPPA PPC.
amd64 done. Thanks Agostino
ppc64 stable, last arch closing