From: "Holger Hoffstaette" <holger.hoffstaette@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Packet sniffing broken recently?
Date: Thu, 29 Dec 2011 17:09:58 +0100 [thread overview]
Message-ID: <pan.2011.12.29.16.09.58.900750@googlemail.com> (raw)
In-Reply-To: jdi11h$6up$1@dough.gmane.org
On Thu, 29 Dec 2011 07:29:51 -0800, walt wrote:
> This change appears to be somewhere in userland, though, not in the kernel
> per se. I copied the kernel .config file from my working amd64 machine to
> the 'broken' ~amd64 machine and recompiled the kernel.
>
> No improvement. I had to enable the nfnetlink module to make packet
> sniffing work again. I suppose one of the networking packages changed in
> a recent ~arch update.
Yup, this was libpcap moving to 1.2 recently. You can get the old
behaviour back by downgrading to 1.1.x, though for me 1.2 also worked
after building all the netfilter modules (default settings) and enabling
linbl for libpcap.
-h
prev parent reply other threads:[~2011-12-29 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 1:01 [gentoo-user] Packet sniffing broken recently? walt
2011-12-29 7:10 ` [gentoo-user] " Lubos Kolouch
2011-12-29 10:09 ` Mick
2011-12-29 15:29 ` walt
2011-12-29 16:09 ` Holger Hoffstaette [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2011.12.29.16.09.58.900750@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox