From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: Wake On Lan device semantics Date: Fri, 3 Nov 2006 17:37:51 -0800 Message-ID: <20061103173751.581ca5ab@localhost.localdomain> References: <20061103152025.5d27bd8d@freekitty> <454BD44D.2060005@intel.com> <20061103155006.68099f6e@freekitty> <454BEEAD.70108@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Jeff Garzik , "David S. Miller" , netdev@vger.kernel.org Return-path: Received: from smtp.osdl.org ([65.172.181.4]:63375 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1753565AbWKDBiE (ORCPT ); Fri, 3 Nov 2006 20:38:04 -0500 To: Auke Kok In-Reply-To: <454BEEAD.70108@intel.com> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, 03 Nov 2006 17:36:45 -0800 Auke Kok wrote: > Stephen Hemminger wrote: > > On Fri, 03 Nov 2006 15:44:13 -0800 > > Auke Kok wrote: > > > >> Stephen Hemminger wrote: > >>> It doesn't seem like a good idea for a network device to wake the system > >>> if it is down. > >> before suspend existed this was the only useful case for WoL. Why does it not seem a > >> good idea to wake up a machine that was shutdown (and thus the interface `downed`) ? > >> > >> Auke > > > > Interestingly it looks like e100 is one of the ones that only wakes from suspend (not when down). > > that would be a bug, I'll have to get that checked especially after the latest changes > to it. > Sorry, my bad my test machine was not setup properly.