From: David Woodhouse <dwmw2@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: rtnetlink interface state monitoring problems.
Date: Mon, 21 Oct 2002 12:18:04 +0100 [thread overview]
Message-ID: <27964.1035199084@passion.cambridge.redhat.com> (raw)
I'm playing with userspace applications which want to monitor the status of
IrDA and Bluetooth devices. Rather than polling for the interface state
(this is a handheld device and polling wastes CPU and battery), I want to
use netlink.
I have two problems:
1. I appear to need CAP_NET_ADMIN to bind to the netlink groups which give
me this information. I can poll for it just fine, but need
elevated privs to be notified. Why is this, and is there a workaround?
2. Even root doesn't get notification of state changes for Bluetooth
interfaces, because they're not treated as 'normal' network devices
like IrDA devices are. I can see the logic behind that -- by why
is it done differently from IrDA? Is there a way to get notification
of BT interface state changes?
--
dwmw2
next reply other threads:[~2002-10-21 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 11:18 David Woodhouse [this message]
2002-10-21 13:02 ` rtnetlink interface state monitoring problems jamal
2002-10-21 18:57 ` David Woodhouse
2002-10-23 0:59 ` jamal
2002-10-23 1:44 ` Tim Hockin
2002-10-23 3:17 ` jamal
2002-10-23 19:42 ` Maksim (Max) Krasnyanskiy
2002-10-28 12:35 ` jamal
2002-10-23 19:41 ` Maksim (Max) Krasnyanskiy
2002-10-21 13:46 ` James Morris
2002-10-21 13:48 ` James Morris
2002-10-21 17:01 ` David S. Miller
2002-10-24 3:41 ` [PATCH] " James Morris
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=27964.1035199084@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).