From: jamal <hadi@cyberus.ca>
To: David Woodhouse <dwmw2@infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <netdev@oss.sgi.com>
Subject: Re: rtnetlink interface state monitoring problems.
Date: Tue, 22 Oct 2002 20:59:22 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.30.0210222055170.24323-100000@shell.cyberus.ca> (raw)
In-Reply-To: <24818.1035226670@passion.cambridge.redhat.com>
On Mon, 21 Oct 2002, David Woodhouse wrote:
>
> hadi@cyberus.ca said:
> > I cant see anything on netlink and irda; i am also not very familiar
> > with either IrDA or Bluetooth. Regardless, you dont need to be a net
> > device to use netlink.
>
> IrDA devices are network devices. The core network code sends a RTM_NETLINK
> message when they go up or down. All is well, and once the permission fix
> gets into the kernel I'm using, my irda monitor applet no longer needs to
> poll the state of the interface.
>
Ah, ok. I see what you mean - for a moment i thought IrDA was doing
something clever with netlink.
> But Bluetooth devices are not network devices, it seems. There exists no
> current mechanism for notifying anyone of state changes. Should we invent a
> new method of notification using netlink, or should Bluetooth interfaces in
> fact be normal network devices just like IrDA devices are?
>
I think the only time you should go netdev is when it makes sense to run
IP. Is there IP over bluttooth? Then you could take advantage of all the
nice features provided by netdevices (other than being IP devices;->).
If not, it probably time for someone to write a generic notification
scheme via netlink.
cheers,
jamal
next prev parent reply other threads:[~2002-10-23 1:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 11:18 David Woodhouse
2002-10-21 13:02 ` jamal
2002-10-21 18:57 ` David Woodhouse
2002-10-23 0:59 ` jamal [this message]
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-22 17:16 Jean Tourrilhes
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=Pine.GSO.4.30.0210222055170.24323-100000@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=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
all inboxes | Powered by JetHome®