WakeOnLan (There must be someone who knows the answer to this.)

[chalsall]

Originally Posted by wildrabbitt

This is what I get when I run arp -n :

What does "ethtool eth0 | grep Wake" as root say on the box you want to remotely wake up?

[wildrabbitt]

Supports Wake-on: pumbg

Wake-on: g

[chalsall]

Originally Posted by wildrabbitt

Supports Wake-on: pumbg
Wake-on: g

OK, then you should be good to go. Just to be clear, I'm assuming you wish to wake up william-desktop (IP: 192.168.1.70; MAC:00:e0:4c:e9:96:a7) from william-GA-78LMT-USB3?

Your "arp -n" from the latter didn't show william-desktop. Are you sure they are on the same LAN? If you "ping -c 1 192.168.1.70" and then "arp -n" does it show up?

If so, try powering down william-desktop, and then run "ether-wake 00:e0:4c:e9:96:a7" as root from william-GA-78LMT-USB3. If everything's good, william-desktop should power up.

[wildrabbitt]

It wasn't on the same LAN but is now. Great news :


william@william-GA-78LMT-USB3:~$ ping -c 1 192.168.1.70
PING 192.168.1.70 (192.168.1.70) 56(84) bytes of data.
64 bytes from 192.168.1.70: icmp_seq=1 ttl=64 time=0.337 ms

--- 192.168.1.70 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.337/0.337/0.337/0.000 ms
william@william-GA-78LMT-USB3:~$ arp -n
Address HWtype HWaddress Flags Mask Iface
192.168.1.254 ether c4:ea:1d:b0:a9:58 C enp3s0
192.168.1.70 ether 00:e0:4c:e9:96:a7 C enp3s0
william@william-GA-78LMT-USB3:~$


So what next?

[chalsall]

Already given.

Originally Posted by chalsall

If so, try powering down william-desktop, and then run "ether-wake 00:e0:4c:e9:96:a7" as root from william-GA-78LMT-USB3. If everything's good, william-desktop should power up.

Note that this is based on CentOS / RedHat / Fedora. The command "ether-wake" may be different under Ubuntu.

[wildrabbitt]

william@william-GA-78LMT-USB3:~$ sudo etherwake 00:e0:4c:e9:96:a7
SIOCGIFHWADDR on eth0 failed: No such device


I ran sudo poweroff on the machine I wanted to wake.

Is Wakeonlan intended to switch PC's on from a position like that?

[chalsall]

Originally Posted by wildrabbitt

william@william-GA-78LMT-USB3:~$ sudo etherwake 00:e0:4c:e9:96:a7
SIOCGIFHWADDR on eth0 failed: No such device

Hmmm... Weird.

When I ran the command from one of my CentOS boxens I got this:

[root@samba2 ~]# ether-wake -v -D 00:e0:4c:e9:96:a7
ether-wake.c: v1.09 11/12/2003 Donald Becker, http://www.scyld.com/
The target station address is 0:e0:4c:e9:96:a7.
Packet is  00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 08 42 ff ff ff ff ff ff 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7 00 e0 4c e9 96 a7.
The hardware address (SIOCGIFHWADDR) of enp11s0 is type 1  00:1a:ffffffa0:ffffffb0:ffffffda:29.
Sendto worked ! 116.
The hardware address (SIOCGIFHWADDR) of lo is type 772  00:00:00:00:00:00.
Sendto worked ! 116.

Perhaps try increasing the debugging / verbosity for the command, and report the results. Note that you are running a different derivative of Linux, so your etherwake may be completely different software than my ether-wake.

Having done a bit of Googling, is seems like Ubuntu also has a "powerwake" command. You might want to try installing and running that.

Originally Posted by wildrabbitt

I ran sudo poweroff on the machine I wanted to wake. Is Wakeonlan intended to switch PC's on from a position like that?

Yes. I often use this to bring machines back online after power failures and/or user shutdowns.

[wildrabbitt]

Can you tell me what this means ? :


<code>
william@william-GA-78LMT-USB3:~$ sudo etherwake 00:e0:4c:e9:96:a7
SIOCGIFHWADDR on eth0 failed: No such device
</code>

This was ran from the waker while it the only machine plugged into the modem.

I'm asking because I'm wondering if we identified correctly the machine to wake.

[chalsall]

Originally Posted by wildrabbitt

I'm asking because I'm wondering if we identified correctly the machine to wake.

Please take this as supportive... You seem to go out of your way to not follow suggestions. To be spoon-fed what to do next.

What happens when you run etherwake with deeper verbosity and/or debugging?

Have you tried using alternative programs from the waking machine? Have you tried thinking for yourself?

I try to be tolerant, but this is getting a bit ridiculous.

[chalsall]

Originally Posted by wildrabbitt

This was ran from the waker while it the only machine plugged into the modem.

Why on gods green earth would you think this would work?

How is william-desktop supposed to receive the broadcast message if it isn't plugged into the switch (on the modem)? Magic???

[wildrabbitt]

Why on gods green earth would you think this would work?

I know this wouldn't work with regards to switching on the machine we were

trying to wake.

I was trying to understand what arp -n

actually does and I wanted to try it (on the waker) with no other machines except the waker plugged in to the modem.