From: Stefan Rompf <stefan@loplof.de>
To: Thomas Ogrisegg <tom-lkml@lkml.fnord.at>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netdev/uevent
Date: Wed, 22 Feb 2006 23:37:34 +0100 [thread overview]
Message-ID: <200602222337.34755.stefan@loplof.de> (raw)
Thomas Ogrisegg wrote:
> What do you mean with "ethtool and netlink"? At least the current
> release of ethtool does not seem to have any netlink support.
You can listen to RTMGRP_LINK on NETLINK_ROUTE. IFF_RUNNING will give you the
link state information you're looking for.
For you application scenario: I'm working on a DHCP client that uses this
netlink information, so don't invent the wheel twice ;-)
Stefan
next reply other threads:[~2006-02-22 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 22:37 Stefan Rompf [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-21 23:48 [PATCH] netdev/uevent Thomas Ogrisegg
2006-02-22 0:17 ` Greg KH
2006-02-22 8:37 ` Thomas Ogrisegg
2006-02-22 17:53 ` Greg KH
2006-02-22 17:54 ` Chris Wright
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=200602222337.34755.stefan@loplof.de \
--to=stefan@loplof.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tom-lkml@lkml.fnord.at \
/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