similar to: Wake on LAN

My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on

Hello list I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R motherboard. Integrated network card is Realtek 8111B. I can not wake the computer after I shutdown it from FreeBSD. It is a dualboot system - windows xp and freebsd. If I shutdown the computer from windows - later I can wake it up with magic packet. Even if i shutdown the machine on the boot menu with the power

On a semi-related subtopic, Why do I want WoL? What concrete examples are there where it's useful? I understand what it is and how it works but the "why" has eluded me. -- Drew "Nothing in life is to be feared. It is only to be understood." --Marie Curie

Many thanks to those that responded to my original posting with information about Network UPS Tools and commercial UPS products. In our planning a path forward to implement UPS-based power fail protection, we have come across what appears to be an issue with the state of the CentOS 6 machines being UPS protected.? Most of these machines are desktop/deskside machines that are likely to be idle

The WoL magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it could be sent as any network- and transport-layer protocol, although it is typically sent as a UDP <https://en.m.wikipedia.org/wiki/User_Datagram_Protocol> datagram <https://en.m.wikipedia.org/wiki/Datagram> to port <https://en.m.wikipedia.org/wiki/TCP_and_UDP_port> 0,]

On Sun, 2020-05-17 at 20:25 -0600, R C wrote: > Ok, I get that, found it before; "typically sent as a UDP datagram to > port 0, 7 or 9, or directly over Ethernet as EtherType 0x0842" > > > The keyword being 'typically', but what is it that ether-wake actually > uses/does? (I need to forward a WOL packet to a different > > vlan on some Cisco

Some switch hardware can generate the packets directly, negating the need for a box on every VLAN. Meraki hardware can do it, but you have to go through the dashboard so automating it isn't currently possible. Here is some documentation on forwarding WoL on catalyst 3750 switches from Cisco:

> Actually you are not correct. > > > 1st: I didn't quote the wikipedia article,? someone sent that as an > answer to my previous post. > > ?? (similar mindset probably, as in your response) > > 2: You are wrong,? broadcast packets, like for example DHCP, and also > WOL (if UDP), can be routed, by > > the means of ip helper addresses and directed broadcasts

Everyone, I have not been able to get ether-wake to work waking up other centos 7.6 machines after the upgrade to Centos 7.6. Has anyone else had this problem, and if so any luck with a fix? Greg Ennis

I have just noticed what appears to be a problem with my CentOS 3.7 servers shutting down. I have Netgear FA312 NICs in some of my DELL PowerEdge 700 servers and this particular NIC has WOL ability. I cannot turn this off in the BIOS or limit the error responses. When I do a "halt", the server goes only as far as closing the ethernet card and stops, resulting in a hardboot being

Running CentOS 6.4. Hi I have a bunch of Intel systems. Ivy Bridge Q77 chipset with 82579LM nics. I can't seem to wake them up with ether-wake. The nic driver is the intel e1000e. #ether-wake -i ethX mac-addr Once up (manually) ethtool reports Supports Wake-on: pumbg Wake-on: g I'm sure I've set the bios up properly. Any advice?

On 01/16/2015 09:51 AM, Kay Diederichs wrote: > On 01/16/2015 05:05 AM, Devin Reade wrote: >> I've got a fresh CentOS 7 test machine, fully patched. The command: >> >> shutdown -h now >> >> surprisingly does not halt the machine. Instead it reboots it. WTF? >> >> I found the following Debian discussion which seems to be the same >>

Hello! I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it). FreeBSD 6.3-STABLE was running fine on it, but I decided to update the machine to 9.1-STABLE. Well, neither my own custom kernel, nor even the official 9.1-RELEASE CD1 would boot... In both cases the boot process runs up to detecting uhub0, then either hangs forever or shuts off after a short while. Again, I thought I

Actually you are not correct. 1st: I didn't quote the wikipedia article,? someone sent that as an answer to my previous post. ?? (similar mindset probably, as in your response) 2: You are wrong,? broadcast packets, like for example DHCP, and also WOL (if UDP), can be routed, by the means of ip helper addresses and directed broadcasts on Cisco equipment Also, you like others seem to

>> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Rich Greenwood >> Sent: Monday, 18 May, 2020 08:34 >> To: centos at centos.org >> Subject: Re: [CentOS] ether-wake >> >> Some switch hardware can generate the packets directly, negating the need >> for a box on every VLAN. Meraki hardware can do it, but

On 20.10.2014 21:30, poma wrote: > On 20.10.2014 08:13, poma wrote: >> >> 02:00.0 VGA compatible controller: >> NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) >> Chipset: G98 (NV98) >> Family : NV50 >> >> The same for all four kernel: >> - 3.18.0-0.rc0.git8.1.fc22.x86_64 >> - 3.18.0-0.rc0.git9.1.fc22.x86_64 >> -

Ive got a soekris 4801 on which Ive used pxelinux... its bios is set to go to pxeboot 1st, then localboot. Ive got: label bootlocal MENU label ^9 Boot Local localboot 0 # timeout 80 # TOTALTIMEOUT 9000 but using hangs: Booting from local disk... PXE-M0F: Exiting MacPhyter PXE ROM. then nothing. the same compact flash image works fine when boot order is 80 1st, or

Ok,? I get that, found it before;? "typically sent as a UDP datagram to port 0, 7 or 9, or directly over Ethernet as EtherType 0x0842" The keyword being 'typically',?? but what is it that ether-wake actually uses/does?? (I need to forward a WOL packet to a different vlan on some Cisco hardware, between two Centos machines). Ron On 5/17/20 8:14 PM, John Pierce wrote: >

Hi, I just setup a very basic HTTP proxy with Squid on a router running CentOS 7. Up until early 2020 I've been using a bone-headed shell script with iptables to configure my firewall. But I decided to follow advice from a few gurus on this list, and I've since moved my configurations to FirewallD, which works nicely. There's one configuration left to tackle, that's port

I am using centos 5.1. I want to keep my machines always powered on. Some machines (important ones) are UPS'd. I have also set in the BIOS (gigabyte motherboard) the power options that after power loss should do a full on. The other day we had just a momentary power drop. the UPS machines had no issue of course with that. However, the other machines did not come back on. Is there anything