Supports Wake On Pumbg
2021年2月28日Download here: http://gg.gg/oh6q2
Today, we continue our series on readying the homelab for unattended access. Previously, we set up a Raspberry Pi to allow us to remote into our network via a reverse SSH tunnel. That’s useful by itself, especially as a backup if our normal route of access (VPN) is down, but we can also use that same reverse SSH tunnel to do some other incredibly useful things such as waking up other devices on the network with wake-on-LAN (WOL). Today’s tutorial will focus on precisely that: enabling our servers to be woken up on LAN, and configuring our RPi sleeper cell to wake those servers up. Let’s begin!
*Supports Wake On Lan Pumbg
*Proxmox Enable Wake On Lan
*Supports Wake-on: PubgEnable Server for Wake-On-LAN (WOL):
1. On your server, install ethtool:
*The older method uses a Wake On LAN three pin connector between your Ethernet card and your main board. Both headers are usually labelled ’wol’. The newer system uses a Wake On LAN pin on the PCI bus, negating the need for the cable.
*Use ethtool to set “Wake-on” option to “g” value And that’s all, then you put your server in suspend or hibernate mode and wake it up remotely. It works like a charm, but then you try a second time, you hibernate the server again and it doesn’t wake remotely.
*The ’g’ in Supports Wake-on: pumbg indicates that wake-on-lan by using a ’magic packet’ is indeed supported. Next, you need to make sure that wake-on-lan support is enabled in the BIOS (although, this does not seem to be necessary for my motherboard). In addition, you need to tell your network card to enable wake-on-lan: # ethtool -s eth0 wol g.
I’m looking to buy a motherboard, and I need one with wake on lan, but I’m not really sure where I should expect to see that a motherboard supports wake on lan. For example I’m looking at MSI Z97I AC, and I cant see that it says ’supports Wake On Lan’ or something like that on the dedicated page, and not in the board’s manual either.
ethtool allows us to verify that our NIC can support wake-on-lan. It is also used to enable wake-on-LAN on Ubuntu.
2. Find the name of the network adapter you are currently using with the following command:
If you don’t already have ifconfig, you can install it with:
If you need help figuring out which network adapter you are currently using, look for the one with an IP address assigned. You can also look at which network adapter has had traffic go through it (the RX and TX packets line will have non-blank values):
In my case, eth0 is the network adapter in use, and chances are it probably is for you too. If you need help with this, feel free to ask me in the comments/forum.
3. While you’re here, record the address next to ether (highlighted above). That’s your MAC address and that’s how we will ultimately address the server when we are ready to wake it up.
4. Check to see if wake-on-LAN is available on your NIC with ethtool:
In my case that command would be:
If WOL is available on your card, you should see a line that appears as so:
We really only care to see that this line contains a ’g’, indicating a that it will accept a ’magic packet’ (the mechanism by which wake-on-LAN works).
N.B.: If you don’t see it, all hope is not lost, you may just need to enable ’Wake-On-LAN’ in the BIOS. This varies from motherboard to motherboard but almost all have this setting so look for it.
5. Enable the system for Wake-On-LAN:
Don’t forget to replace eth0 with the adapter you’re using if you have a different one.
6. Create the script to insure that WOL is always enabled:
Now, there’s an unpleasant little ’feature’ in OS’s where the above setting gets reset after every reboot. Supports Wake On Lan Pumbg
If you’re using unRAID, this easily handled with the User Scripts plugin. Just create a user script with the following content and set it to run ’At startup of array’ (make sure you have the array set to always start):
If you’re using Ubuntu, we’ll need to create a system service:
In this add the following:
Again, don’t forget to replace eth0 with whatever network adapter you’re using.
Enable the service:
That’s it for setting everything up on the server side. Now, let’s set everything up on our RPi (or whatever other device you have the reverse SSH tunnel set up on).Install Etherwake on RPi:
7. Super easy job here. Just install etherwake on the RPi with:
That’s all!Test Everything Out:
8. Shutdown your server so we can test waking it up.
9. SSH (reverse SSH if working remotely) into your RPi.
10. Just like we did in Step 2 above, identify the network device in use on your RPi.
This is where A LOT of people trip up and why they fail to get wake-on-LAN/etherwake working. By default, etherwake attempts to send out the WOL magic packet on eth0 of the device it’s being run on. If eth0 isn’t in use, you’ll get the following error message:
11. Send the WOL magic packet with the following command using the MAC address you found in Step 2/3 above and the RPi network device you found in step 10 above:Proxmox Enable Wake On Lan
Example:
At this point, you should hear your server kick on and boot up!
As always, let me know if you run into any problems or have any questions in the comments below!
Interested in this topic and others like it? Join our community and join in the discussion! We currently have a need for moderators so if you can help out it would be much appreciated!
I don’t know if you lost interest or if you solved this already but here’s a datapoint of my own: recent(1) kernels make my desktop system(2) reboot instead of shutdown, I have not bothered to look into it because I don’t use it very often but after your inquiry I decided to look into my own problem.
Symantec winfax pro and .fxm viewer for mac. It seems that for some systems, having ’Resume by pci device pme’ will cause the machine to reboot instead of shutdown, and indeed after looking into the bios setting on my desktop system I had that enabled. If anything I’d say that this behavior may be a mix of a wonky bios and a kernel regression.Supports Wake-on: Pubg
(1) Can’t say for sure when this started happening, but current Arch kernels do this (didn’t try LTS though), both windows xp and 7 work as expected. The current kernel shipped by CentOS 6 (2.6.32-431) also shuts down the machine as expected so you might want to try a livecd of a distro with an older kernel to see if the problem goes away. Caterpillar service manuals free download | Truckmanualshub.com.
(2) The machine is getting old and is starting to misbehave so initially I dismissed the wonky behavior as some early impending failure sign.
Download here: http://gg.gg/oh6q2
https://diarynote.indered.space
Today, we continue our series on readying the homelab for unattended access. Previously, we set up a Raspberry Pi to allow us to remote into our network via a reverse SSH tunnel. That’s useful by itself, especially as a backup if our normal route of access (VPN) is down, but we can also use that same reverse SSH tunnel to do some other incredibly useful things such as waking up other devices on the network with wake-on-LAN (WOL). Today’s tutorial will focus on precisely that: enabling our servers to be woken up on LAN, and configuring our RPi sleeper cell to wake those servers up. Let’s begin!
*Supports Wake On Lan Pumbg
*Proxmox Enable Wake On Lan
*Supports Wake-on: PubgEnable Server for Wake-On-LAN (WOL):
1. On your server, install ethtool:
*The older method uses a Wake On LAN three pin connector between your Ethernet card and your main board. Both headers are usually labelled ’wol’. The newer system uses a Wake On LAN pin on the PCI bus, negating the need for the cable.
*Use ethtool to set “Wake-on” option to “g” value And that’s all, then you put your server in suspend or hibernate mode and wake it up remotely. It works like a charm, but then you try a second time, you hibernate the server again and it doesn’t wake remotely.
*The ’g’ in Supports Wake-on: pumbg indicates that wake-on-lan by using a ’magic packet’ is indeed supported. Next, you need to make sure that wake-on-lan support is enabled in the BIOS (although, this does not seem to be necessary for my motherboard). In addition, you need to tell your network card to enable wake-on-lan: # ethtool -s eth0 wol g.
I’m looking to buy a motherboard, and I need one with wake on lan, but I’m not really sure where I should expect to see that a motherboard supports wake on lan. For example I’m looking at MSI Z97I AC, and I cant see that it says ’supports Wake On Lan’ or something like that on the dedicated page, and not in the board’s manual either.
ethtool allows us to verify that our NIC can support wake-on-lan. It is also used to enable wake-on-LAN on Ubuntu.
2. Find the name of the network adapter you are currently using with the following command:
If you don’t already have ifconfig, you can install it with:
If you need help figuring out which network adapter you are currently using, look for the one with an IP address assigned. You can also look at which network adapter has had traffic go through it (the RX and TX packets line will have non-blank values):
In my case, eth0 is the network adapter in use, and chances are it probably is for you too. If you need help with this, feel free to ask me in the comments/forum.
3. While you’re here, record the address next to ether (highlighted above). That’s your MAC address and that’s how we will ultimately address the server when we are ready to wake it up.
4. Check to see if wake-on-LAN is available on your NIC with ethtool:
In my case that command would be:
If WOL is available on your card, you should see a line that appears as so:
We really only care to see that this line contains a ’g’, indicating a that it will accept a ’magic packet’ (the mechanism by which wake-on-LAN works).
N.B.: If you don’t see it, all hope is not lost, you may just need to enable ’Wake-On-LAN’ in the BIOS. This varies from motherboard to motherboard but almost all have this setting so look for it.
5. Enable the system for Wake-On-LAN:
Don’t forget to replace eth0 with the adapter you’re using if you have a different one.
6. Create the script to insure that WOL is always enabled:
Now, there’s an unpleasant little ’feature’ in OS’s where the above setting gets reset after every reboot. Supports Wake On Lan Pumbg
If you’re using unRAID, this easily handled with the User Scripts plugin. Just create a user script with the following content and set it to run ’At startup of array’ (make sure you have the array set to always start):
If you’re using Ubuntu, we’ll need to create a system service:
In this add the following:
Again, don’t forget to replace eth0 with whatever network adapter you’re using.
Enable the service:
That’s it for setting everything up on the server side. Now, let’s set everything up on our RPi (or whatever other device you have the reverse SSH tunnel set up on).Install Etherwake on RPi:
7. Super easy job here. Just install etherwake on the RPi with:
That’s all!Test Everything Out:
8. Shutdown your server so we can test waking it up.
9. SSH (reverse SSH if working remotely) into your RPi.
10. Just like we did in Step 2 above, identify the network device in use on your RPi.
This is where A LOT of people trip up and why they fail to get wake-on-LAN/etherwake working. By default, etherwake attempts to send out the WOL magic packet on eth0 of the device it’s being run on. If eth0 isn’t in use, you’ll get the following error message:
11. Send the WOL magic packet with the following command using the MAC address you found in Step 2/3 above and the RPi network device you found in step 10 above:Proxmox Enable Wake On Lan
Example:
At this point, you should hear your server kick on and boot up!
As always, let me know if you run into any problems or have any questions in the comments below!
Interested in this topic and others like it? Join our community and join in the discussion! We currently have a need for moderators so if you can help out it would be much appreciated!
I don’t know if you lost interest or if you solved this already but here’s a datapoint of my own: recent(1) kernels make my desktop system(2) reboot instead of shutdown, I have not bothered to look into it because I don’t use it very often but after your inquiry I decided to look into my own problem.
Symantec winfax pro and .fxm viewer for mac. It seems that for some systems, having ’Resume by pci device pme’ will cause the machine to reboot instead of shutdown, and indeed after looking into the bios setting on my desktop system I had that enabled. If anything I’d say that this behavior may be a mix of a wonky bios and a kernel regression.Supports Wake-on: Pubg
(1) Can’t say for sure when this started happening, but current Arch kernels do this (didn’t try LTS though), both windows xp and 7 work as expected. The current kernel shipped by CentOS 6 (2.6.32-431) also shuts down the machine as expected so you might want to try a livecd of a distro with an older kernel to see if the problem goes away. Caterpillar service manuals free download | Truckmanualshub.com.
(2) The machine is getting old and is starting to misbehave so initially I dismissed the wonky behavior as some early impending failure sign.
Download here: http://gg.gg/oh6q2
https://diarynote.indered.space
コメント