From: Stephen Hemminger <shemminger@osdl.org>
To: David Miller <davem@davemloft.net>
Cc: jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: Wake On Lan device semantics
Date: Fri, 3 Nov 2006 16:11:21 -0800 [thread overview]
Message-ID: <20061103161121.7533b32c@freekitty> (raw)
In-Reply-To: <20061103.160230.71088561.davem@davemloft.net>
On Fri, 03 Nov 2006 16:02:30 -0800 (PST)
David Miller <davem@davemloft.net> wrote:
> From: Jeff Garzik <jgarzik@pobox.com>
> Date: Fri, 03 Nov 2006 18:51:25 -0500
>
> > The purpose of WOL is being able to turn on a system remotely, if it is
> > in a power-off or sleep state.
> >
> > So, if the system is -on- and the interface is down and/or driver is
> > unloaded, are you saying WOL is a problem somehow?
>
> Stephen is saying that if you down an interface, it should disable
> that WoL functionality.
>
> I guess you can argue that, like IP addresses, this WoL thing is an
> attribute of the "system".
Looking harder. The semantic needs to be WOL is okay if driver is loaded
and device is up or down. But the default for WOL should be disabled until
enabled by ethtool (or parameter).
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-11-04 0:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 23:20 Wake On Lan device semantics Stephen Hemminger
2006-11-03 23:44 ` Auke Kok
2006-11-03 23:48 ` Stephen Hemminger
2006-11-04 1:35 ` Auke Kok
2006-11-03 23:50 ` Stephen Hemminger
2006-11-04 1:36 ` Auke Kok
2006-11-04 1:37 ` Stephen Hemminger
2006-11-04 1:44 ` Auke Kok
2006-11-03 23:51 ` Jeff Garzik
2006-11-04 0:02 ` David Miller
2006-11-04 0:11 ` Stephen Hemminger [this message]
2006-11-04 1:53 ` Auke Kok
2006-11-04 0:42 ` Jeff Garzik
2006-11-04 1:02 ` David Miller
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=20061103161121.7533b32c@freekitty \
--to=shemminger@osdl.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--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 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).