From: Chris Friesen <chris.friesen@genband.com>
To: David Miller <davem@davemloft.net>
Cc: dev@nico22.de, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Network link detection
Date: Thu, 03 Mar 2011 17:54:12 -0600 [thread overview]
Message-ID: <4D702A24.70805@genband.com> (raw)
In-Reply-To: <20110303.140106.191399853.davem@davemloft.net>
On 03/03/2011 04:01 PM, David Miller wrote:
> From: Chris Friesen <chris.friesen@genband.com>
> Date: Thu, 03 Mar 2011 15:38:35 -0600
>
>> You might look at whether you could write a kernel module to register
>> for NETDEV_CHANGE notifications and pass that back to userspace.
>
> This is the kind of responses you get when you ask networking specific
> questions and don't CC: netdev :-/
My apologies for misleading the original poster. I can only claim a
brain fart since I've actually used rtnetlink for other things.
> There is this thing called netlink, you can listen for arbitrary
> network state change events on a socket, and get the link state
> notifications you are looking for. It's in use by many real
> applications like NetworkManager and co.
For future reference then, to listen for link state notifications you'd
use NETLINK_ROUTE with nl_groups set to RTMGRP_LINK, and the link state
will be signaled in the if_flags field of received messages?
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next prev parent reply other threads:[~2011-03-03 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 19:30 Network link detection Nico Schümann
2011-03-03 20:03 ` Jesper Juhl
2011-03-03 20:45 ` richard -rw- weinberger
2011-03-03 21:38 ` Chris Friesen
2011-03-03 22:01 ` David Miller
2011-03-03 22:29 ` Nico Schümann
2011-03-07 19:49 ` Dan Williams
2011-03-03 23:54 ` Chris Friesen [this message]
2011-03-03 22:07 ` Stephen Hemminger
2011-03-04 6:35 ` Nico Schümann
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=4D702A24.70805@genband.com \
--to=chris.friesen@genband.com \
--cc=davem@davemloft.net \
--cc=dev@nico22.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.