Wake-on-LAN from suspended state

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Wake-on-LAN from suspended state

Paul de Weerd
Hi all,

I've been playing with WoL recently and found that my desktop machine
(a Dell Optiplex 9020) can be woken up from another OpenBSD machine on
the same network with `doas arp -W ${MAC} em1` (where ${MAC} is the
mac address of my desktop machine).  As I'm using softraid full disk
encryption, this doesn't help too much - I still need to be present to
unlock the crypto volume manually.

Figured I try waking the machine up from sleep mode.  This machine
suspends fine with zzz, and also wakes perfectly from sleep by pushing
the power button (included dmesg contains one suspend / resume cycle).
However, in suspended state, I can't wake up the machine with the
magic packet.

Reading up on the topic of WoL shows a field full of rabbit holes.
Does anyone know if it is possible at all to do this with OpenBSD?
I'm guessing the NIC should be left in a state that allows it to wake
the rest of the machine when entering suspend - perhaps that's not
done on purpose because it's not wanted.  Can anyone shed some light
on this matter?

Thanks,

Paul 'WEiRD' de Weerd

OpenBSD 6.3-current (GENERIC.MP) #8: Sun Apr 22 00:40:30 MDT 2018
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34243903488 (32657MB)
avail mem = 33198944256 (31660MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec410 (88 entries)
bios0: vendor Dell Inc. version "A21" date 12/27/2017
bios0: Dell Inc. OptiPlex 9020
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT SLIC LPIT SSDT SSDT SSDT HPET SSDT MCFG SSDT ASF! DMAR
acpi0: wakeup devices UAR1(S3) PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) PXSX(S4) RP05(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S4) HDEF(S4) PEG0(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.98 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 MHz
cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 MHz
cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 MHz
cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 MHz
cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 1, package 0
cpu6 at mainbus0: apid 5 (application processor)
cpu6: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 MHz
cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 1, core 2, package 0
cpu7 at mainbus0: apid 7 (application processor)
cpu7: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 MHz
cpu7: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu7: 256KB 64b/line 8-way L2 cache
cpu7: smt 1, core 3, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec00000, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP05)
acpiprt3 at acpi0: bus -1 (PEG0)
acpiprt4 at acpi0: bus -1 (PEG1)
acpiprt5 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu4 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu5 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu6 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu7 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
acpicmos0 at acpi0
"INT3F0D" at acpi0 not configured
acpibtn0 at acpi0: PWRB
"PNP0C14" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 3691 MHz: speeds: 3401, 3400, 3200, 3000, 2800, 2700, 2500, 2300, 2100, 1900, 1700, 1500, 1400, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1920x1080, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi
azalia0: No codecs found
xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x04: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
puc0 at pci0 dev 22 function 3 "Intel 8 Series KT" rev 0x04: ports: 16 com
com4 at puc0 port 0 apic 8 int 19: ns16550a, 16 byte fifo
com4: probed fifo depth: 0 bytes
em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x04: msi, address b8:ca:3a:93:03:e8
ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x04: apic 8 int 16
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x04: msi
azalia1: codecs: Realtek/0x0280
audio0 at azalia1
ppb0 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd4
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 4 "Intel 8 Series PCIE" rev 0xd4: msi
pci2 at ppb1 bus 2
ahci0 at pci2 dev 0 function 0 vendor "Marvell", unknown product 0x9128 rev 0x20: msi, AHCI 1.2
ahci0: port 7: 1.5Gb/s
scsibus1 at ahci0: 32 targets
uk0 at scsibus1 targ 7 lun 0: <Marvell, 91xx Config, 1.01> ATAPI 3/processor fixed
ehci1 at pci0 dev 29 function 0 "Intel 8 Series USB" rev 0x04: apic 8 int 23
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel Q87 LPC" rev 0x04
ahci1 at pci0 dev 31 function 2 "Intel 8 Series AHCI" rev 0x04: msi, AHCI 1.3
ahci1: port 0: 6.0Gb/s
ahci1: port 1: 1.5Gb/s
ahci1: port 2: 6.0Gb/s
scsibus2 at ahci1: 32 targets
sd0 at scsibus2 targ 0 lun 0: <ATA, Samsung SSD 850, EMT0> SCSI3 0/direct fixed naa.5002538d41b86e4d
sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin
cd0 at scsibus2 targ 1 lun 0: <HL-DT-ST, DVD+-RW GT80N, A103> ATAPI 5/cdrom removable
sd1 at scsibus2 targ 2 lun 0: <ATA, WDC WD60EFRX-68L, 82.0> SCSI3 0/direct fixed naa.50014ee2b81f4111
sd1: 5723166MB, 512 bytes/sector, 11721045168 sectors
ichiic0 at pci0 dev 31 function 3 "Intel 8 Series SMBus" rev 0x04: apic 8 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM PC3-12800
spdmem1 at iic0 addr 0x51: 8GB DDR3 SDRAM PC3-12800
spdmem2 at iic0 addr 0x52: 8GB DDR3 SDRAM PC3-12800
spdmem3 at iic0 addr 0x53: 8GB DDR3 SDRAM PC3-12800
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vmm0 at mainbus0: VMX/EPT
uhub3 at uhub0 port 3 configuration 1 interface 0 "VIA Labs, Inc. USB2.0 Hub" rev 2.10/d.a0 addr 2
urtwn0 at uhub3 port 1 configuration 1 interface 0 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 3
urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 84:1b:5e:94:98:30
uhidev0 at uhub3 port 4 configuration 1 interface 0 "Metadot - Das Keyboard Das Keyboard" rev 2.00/1.00 addr 4
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub3 port 4 configuration 1 interface 1 "Metadot - Das Keyboard Das Keyboard" rev 2.00/1.00 addr 4
uhidev1: iclass 3/0, 3 report ids
uhid0 at uhidev1 reportid 1: input=0, output=0, feature=7
uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
uhid2 at uhidev1 reportid 3: input=3, output=0, feature=0
uhidev2 at uhub0 port 5 configuration 1 interface 0 "Logitech USB Gaming Mouse" rev 2.00/46.00 addr 5
uhidev2: iclass 3/1
ums0 at uhidev2: 16 buttons, Z and W dir
wsmouse0 at ums0 mux 0
uhidev3 at uhub0 port 5 configuration 1 interface 1 "Logitech USB Gaming Mouse" rev 2.00/46.00 addr 5
uhidev3: iclass 3/0, 17 report ids
uhid3 at uhidev3 reportid 16: input=6, output=6, feature=0
uhid4 at uhidev3 reportid 17: input=19, output=19, feature=0
uvideo0 at uhub0 port 6 configuration 1 interface 0 "Logitech QuickCam Pro 9000" rev 2.00/0.08 addr 6
video0 at uvideo0
uaudio0 at uhub0 port 6 configuration 1 interface 2 "Logitech QuickCam Pro 9000" rev 2.00/0.08 addr 6
uaudio0: audio rev 1.00, 2 mixer controls
audio1 at uaudio0
uhidev4 at uhub0 port 10 configuration 1 interface 0 "RDing TEMPERHUM1V1.2" rev 2.00/0.01 addr 7
uhidev4: iclass 3/1, 1 report id
ukbd1 at uhidev4 reportid 1: 8 variable keys, 5 key codes
wskbd2 at ukbd1 mux 1
wskbd2: connecting to wsdisplay0
uhidev5 at uhub0 port 10 configuration 1 interface 1 "RDing TEMPERHUM1V1.2" rev 2.00/0.01 addr 7
uhidev5: iclass 3/1
ugold0 at uhidev5
uhub4 at uhub0 port 20 configuration 1 interface 0 "VIA Labs, Inc. USB3.0 Hub" rev 3.00/d.a1 addr 8
uhub5 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.04 addr 2
uhub6 at uhub2 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.04 addr 2
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
sd2 at scsibus4 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct fixed
sd2: 953866MB, 512 bytes/sector, 1953519473 sectors
root on sd2a (a0b80508b6693ba1.a) swap on sd2b dump on sd2b
ugold0: 2 sensors type si7006 (temperature and humidity)
uhub4 detached
urtwn0 detached
wskbd1: disconnecting from wsdisplay0
wskbd1 detached
ukbd0 detached
uhidev0 detached
uhid0 detached
uhid1 detached
uhid2 detached
uhidev1 detached
uhub3 detached
wsmouse0 detached
ums0 detached
uhidev2 detached
uhid3 detached
uhid4 detached
uhidev3 detached
video0 detached
uvideo0 detached
audio1 detached
uaudio0 detached
wskbd2: disconnecting from wsdisplay0
wskbd2 detached
ukbd1 detached
uhidev4 detached
ugold0 detached
uhidev5 detached
uhub0 detached
uhub5 detached
uhub1 detached
uhub6 detached
uhub2 detached
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ahci1: device on port 2 didn't come ready, TFD: 0x80<BSY>
ahci1: stopping the port, softreset slot 31 was still active.
ahci1: unable to communicate with device on port 2
uhub3 at uhub0 port 3 configuration 1 interface 0 "VIA Labs, Inc. USB2.0 Hub" rev 2.10/d.a0 addr 2
urtwn0 at uhub3 port 1 configuration 1 interface 0 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 3
urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 84:1b:5e:94:98:30
uhidev0 at uhub3 port 4 configuration 1 interface 0 "Metadot - Das Keyboard Das Keyboard" rev 2.00/1.00 addr 4
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub3 port 4 configuration 1 interface 1 "Metadot - Das Keyboard Das Keyboard" rev 2.00/1.00 addr 4
uhidev1: iclass 3/0, 3 report ids
uhid0 at uhidev1 reportid 1: input=0, output=0, feature=7
uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
uhid2 at uhidev1 reportid 3: input=3, output=0, feature=0
uhidev2 at uhub0 port 5 configuration 1 interface 0 "Logitech USB Gaming Mouse" rev 2.00/46.00 addr 5
uhidev2: iclass 3/1
ums0 at uhidev2: 16 buttons, Z and W dir
wsmouse0 at ums0 mux 0
uhidev3 at uhub0 port 5 configuration 1 interface 1 "Logitech USB Gaming Mouse" rev 2.00/46.00 addr 5
uhidev3: iclass 3/0, 17 report ids
uhid3 at uhidev3 reportid 16: input=6, output=6, feature=0
uhid4 at uhidev3 reportid 17: input=19, output=19, feature=0
uvideo0 at uhub0 port 6 configuration 1 interface 0 "Logitech QuickCam Pro 9000" rev 2.00/0.08 addr 6
video0 at uvideo0
uaudio0 at uhub0 port 6 configuration 1 interface 2 "Logitech QuickCam Pro 9000" rev 2.00/0.08 addr 6
uaudio0: audio rev 1.00, 2 mixer controls
audio1 at uaudio0
uhidev4 at uhub0 port 10 configuration 1 interface 0 "RDing TEMPERHUM1V1.2" rev 2.00/0.01 addr 7
uhidev4: iclass 3/1, 1 report id
ukbd1 at uhidev4 reportid 1: 8 variable keys, 5 key codes
wskbd2 at ukbd1 mux 1
wskbd2: connecting to wsdisplay0
uhidev5 at uhub0 port 10 configuration 1 interface 1 "RDing TEMPERHUM1V1.2" rev 2.00/0.01 addr 7
uhidev5: iclass 3/1
ugold0 at uhidev5
uhub4 at uhub0 port 20 configuration 1 interface 0 "VIA Labs, Inc. USB3.0 Hub" rev 3.00/d.a1 addr 8
uhub5 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.04 addr 2
uhub6 at uhub2 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.04 addr 2
ugold0: 2 sensors type si7006 (temperature and humidity)

--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
                 http://www.weirdnet.nl/                 

Reply | Threaded
Open this post in threaded view
|

Re: Wake-on-LAN from suspended state

Daniel Melameth
On Tue, Apr 24, 2018 at 2:11 PM, Paul de Weerd <[hidden email]> wrote:

> I've been playing with WoL recently and found that my desktop machine
> (a Dell Optiplex 9020) can be woken up from another OpenBSD machine on
> the same network with `doas arp -W ${MAC} em1` (where ${MAC} is the
> mac address of my desktop machine).  As I'm using softraid full disk
> encryption, this doesn't help too much - I still need to be present to
> unlock the crypto volume manually.
>
> Figured I try waking the machine up from sleep mode.  This machine
> suspends fine with zzz, and also wakes perfectly from sleep by pushing
> the power button (included dmesg contains one suspend / resume cycle).
> However, in suspended state, I can't wake up the machine with the
> magic packet.
>
> Reading up on the topic of WoL shows a field full of rabbit holes.
> Does anyone know if it is possible at all to do this with OpenBSD?
> I'm guessing the NIC should be left in a state that allows it to wake
> the rest of the machine when entering suspend - perhaps that's not
> done on purpose because it's not wanted.  Can anyone shed some light
> on this matter?

If I understand you correctly, have you tried enabling WoL via ifconfig?

Reply | Threaded
Open this post in threaded view
|

Re: Wake-on-LAN from suspended state

Jiri B-2
In reply to this post by Paul de Weerd
On Tue, Apr 24, 2018 at 10:11:44PM +0200, Paul de Weerd wrote:
> [...]
> em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x04: msi, address b8:ca:3a:93:03:e8

IIUC em does not support WOL. Am I right?

Jiri

Reply | Threaded
Open this post in threaded view
|

Re: Wake-on-LAN from suspended state

Paul de Weerd
On Wed, Apr 25, 2018 at 02:27:44AM -0400, Jiri B wrote:
| On Tue, Apr 24, 2018 at 10:11:44PM +0200, Paul de Weerd wrote:
| > [...]
| > em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x04: msi, address b8:ca:3a:93:03:e8
|
| IIUC em does not support WOL. Am I right?

Thanks Jiri, Daniel and one person who responded off-list.  I had
missed the ifconfig wol option, this does exactly what I want:

    wol     Enable Wake on LAN (WoL).  When enabled, reception of a
            WoL frame will cause the network card to power up the
            system from standby or suspend mode.  WoL frames are sent
            using arp(8).


But indeed, as Jiri suggests, it seems that em(4) doesn't support WOL:

        [weerd@pom] $ doas ifconfig em0 wol
        ifconfig: SIOCSIFXFLAGS: Not supported

Thanks for all the replies!

Paul 'WEiRD' de Weerd

--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
                 http://www.weirdnet.nl/                 

Reply | Threaded
Open this post in threaded view
|

Re: Wake-on-LAN from suspended state

george-3


On 25/04/18 07:55, Paul de Weerd wrote:

> On Wed, Apr 25, 2018 at 02:27:44AM -0400, Jiri B wrote:
> | On Tue, Apr 24, 2018 at 10:11:44PM +0200, Paul de Weerd wrote:
> | > [...]
> | > em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x04: msi, address b8:ca:3a:93:03:e8
> |
> | IIUC em does not support WOL. Am I right?
>
> Thanks Jiri, Daniel and one person who responded off-list.  I had
> missed the ifconfig wol option, this does exactly what I want:
>
>      wol     Enable Wake on LAN (WoL).  When enabled, reception of a
>              WoL frame will cause the network card to power up the
>              system from standby or suspend mode.  WoL frames are sent
>              using arp(8).
>
>
> But indeed, as Jiri suggests, it seems that em(4) doesn't support WOL:
>
> [weerd@pom] $ doas ifconfig em0 wol
> ifconfig: SIOCSIFXFLAGS: Not supported
>
> Thanks for all the replies!
>
> Paul 'WEiRD' de Weerd
>
Hi Paul,

I see the same apparent lack of support but I've been using wol happily
with em on both 6.2 and 6.3 i386 ...  I use it to wake up a box shutdown
with "halt -p".

I don't remember doing anything clever and I can't see anything related
in any config files.

Regards,
George.

Reply | Threaded
Open this post in threaded view
|

Re: Wake-on-LAN from suspended state

Erling Westenvik-2
On Wed, Apr 25, 2018 at 05:33:15PM +0100, [hidden email] wrote:

> On 25/04/18 07:55, Paul de Weerd wrote:
> > On Wed, Apr 25, 2018 at 02:27:44AM -0400, Jiri B wrote:
> > | On Tue, Apr 24, 2018 at 10:11:44PM +0200, Paul de Weerd wrote:
> > | > [...]
> > | > em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x04: msi, address b8:ca:3a:93:03:e8
> > |
> > | IIUC em does not support WOL. Am I right?
> >
> > Thanks Jiri, Daniel and one person who responded off-list.  I had
> > missed the ifconfig wol option, this does exactly what I want:
> >
> >      wol     Enable Wake on LAN (WoL).  When enabled, reception of a
> >              WoL frame will cause the network card to power up the
> >              system from standby or suspend mode.  WoL frames are sent
> >              using arp(8).
> >
> >
> > But indeed, as Jiri suggests, it seems that em(4) doesn't support WOL:
> >
> > [weerd@pom] $ doas ifconfig em0 wol
> > ifconfig: SIOCSIFXFLAGS: Not supported
> >
> > Thanks for all the replies!
> >
> > Paul 'WEiRD' de Weerd
> >
> Hi Paul,
>
> I see the same apparent lack of support but I've been using wol happily with
> em on both 6.2 and 6.3 i386 ...  I use it to wake up a box shutdown with
> "halt -p".
>
> I don't remember doing anything clever and I can't see anything related in
> any config files.

In this context, em(4) refers to the OpenBSD driver (man em), not the
actual physical device. Many em-devices support WoL at BIOS-level and
machines with such setup will cold boot successfully. Resuming from
suspend/hibernate is an altogheter different affair. It works partly on
an em-machine I have. At least for the first zzz/arp cycle.

I'm wondering: are there any OpenBSD drivers that support WoL at all?

Regards,
Erling

Reply | Threaded
Open this post in threaded view
|

Re: Wake-on-LAN from suspended state

Paul de Weerd
In reply to this post by george-3
Hi George,

On Wed, Apr 25, 2018 at 05:33:15PM +0100, [hidden email] wrote:
| I see the same apparent lack of support but I've been using wol happily with
| em on both 6.2 and 6.3 i386 ...  I use it to wake up a box shutdown with
| "halt -p".

Yes, as I mentioned in my original mail, that works fine for me too:
when the machine is powered off (as in your case with `halt -p`), I
can wake up the machine just fine with WoL.

| I don't remember doing anything clever and I can't see anything related in
| any config files.

My challenge is waking the machine with WoL after suspending it
through `zzz`.  To that end, as has been pointed out by a few people
on the list, you'd have to put 'wol' in the relevant hostname.if(5)
file (see the ifconfig manpage for details).  But, since the driver
for Intel gigabit network cards (em(4)) doesn't support this option,
it doesn't work.

Cheers,

Paul 'WEiRD' de Weerd

--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
                 http://www.weirdnet.nl/                 

Reply | Threaded
Open this post in threaded view
|

Re: Wake-on-LAN from suspended state

Paul de Weerd
In reply to this post by Erling Westenvik-2
Hi Erling,

On Thu, Apr 26, 2018 at 12:31:27AM +0200, Erling Westenvik wrote:
| In this context, em(4) refers to the OpenBSD driver (man em), not the
| actual physical device. Many em-devices support WoL at BIOS-level and
| machines with such setup will cold boot successfully. Resuming from
| suspend/hibernate is an altogheter different affair. It works partly on
| an em-machine I have. At least for the first zzz/arp cycle.

Hmm?  So you're saying you *can* resume a suspended machine through
WoL to its em(4) interface?

| I'm wondering: are there any OpenBSD drivers that support WoL at all?

re(4) has this bit:

> The re driver additionally supports Wake on LAN (WoL).  See arp(8)
> and ifconfig(8) for more details.

Maybe other NIC drivers support it too, I didn't check them all.  Just
remembered that Stefan Sperling (stsp@) added it there a looong long
time ago.  Just checked: 7 years ago!

http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/share/man/man4/re.4?rev=1.45&content-type=text/x-cvsweb-markup

Cheers,

Paul 'WEiRD' de Weerd

--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
                 http://www.weirdnet.nl/