From owner-freebsd-current@freebsd.org  Fri Nov 13 01:02:35 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D1CAA2CA39
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 13 Nov 2015 01:02:35 +0000 (UTC) (envelope-from yuri@rawbw.com)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id E9B981452
 for <freebsd-current@freebsd.org>; Fri, 13 Nov 2015 01:02:34 +0000 (UTC)
 (envelope-from yuri@rawbw.com)
Received: by mailman.ysv.freebsd.org (Postfix)
 id E8BA7A2CA38; Fri, 13 Nov 2015 01:02:34 +0000 (UTC)
Delivered-To: current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8517A2CA37
 for <current@mailman.ysv.freebsd.org>; Fri, 13 Nov 2015 01:02:34 +0000 (UTC)
 (envelope-from yuri@rawbw.com)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by mx1.freebsd.org (Postfix) with ESMTP id D2FF71451
 for <current@freebsd.org>; Fri, 13 Nov 2015 01:02:34 +0000 (UTC)
 (envelope-from yuri@rawbw.com)
Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net
 [50.184.63.128]) (authenticated bits=0)
 by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id tAD12RxZ094637
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO)
 for <current@freebsd.org>; Thu, 12 Nov 2015 17:02:27 -0800 (PST)
 (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be
 yuri.doctorlan.com
Subject: Re: Wake on LAN broken (probably between r290542 - r290606)?
To: current@freebsd.org
References: <20151111143337.GN1235@albert.catwhisker.org>
From: Yuri <yuri@rawbw.com>
Message-ID: <564536A3.5050202@rawbw.com>
Date: Thu, 12 Nov 2015 17:02:27 -0800
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <20151111143337.GN1235@albert.catwhisker.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2015 01:02:35 -0000

On 11/11/2015 06:33, David Wolfskill wrote:
> Can anyone else confirm or refute my observations?  Or suggest a
> hint?  I'll try narrowing it down myself, but I need to do it during
> times I'm at home (so I can manually power the machine back up when
> it fails to respond to WoL), so it may be a few days before I can
> accomplish much that way.

Did you confirm (for ex. with Wireshark) that wol actually sends the packet?
If you are trying to wake the machine that is not booted, this is 
primarily dependent on the BIOS of the target machine to wake it up.
In my experience, BIOSes are prone to losing settings, due to low 
battery, or other (sometimes mysterious) reasons.
Please confirm that BIOS setting "Wake On LAN" is on on target.

Yuri