similar to: Centos 7.6 & ether-wake

Can you be more specific about the hardware? I have a setup of DELL desktop, DELL Server SuperMicro Server and couple other devices. I am using from a cgi script the next on one server to wake the other: /usr/bin/sudo /usr/sbin/ether-wake "XY::XY" -b && echo 1 All of my servers have Intel PRO 1Gbit ethernet nics(2,4,1.. ports per machine). To make the Desktop wakeup I had to do

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

> 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

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:

Has anyone experience with WOL under Centos (5.3).? If so, how exactly do you put the machine to sleep, and how exactly do you wake it up remotely? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin

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

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

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 Sun, May 17, 2020 at 07:46:00PM -0600, R C wrote: > what port does ether-wake use?? (I believe it is port 9? but not sure). The 'ether-wake' command in net-tools doesn't use a port at all. It's just a raw packet of EtherType 0x0842 as the so-called "Magic Packet" <https://en.wikipedia.org/wiki/Wake-on-LAN#Magic_packet> For example, if you were to run:

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

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: >

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?

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

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

Everyone, Apparently, aeskulap is broken during the upgrade fro 7.5 to 7.6, and is no longer available in the epel repos. I had some difficulty having it function, and during the debug process I decided to do a yum remove, but when I tried a yum install to reinstall it, aeskulap was no longer present. This problem may also affect other modules. I have placed a bug report :

Hello, what port does ether-wake use?? (I believe it is port 9? but not sure). Ron

Everyone, I am putting together a new mail server for our firm using a SuperMicro with Centos 7.0. When performed the install of the os, I put 16 gigs of memory in the wrong slots on the mother board which caused the SuperMicro to recognize 8 gigs instead of 16 gigs. When I installed Centos 7.0, this error made the swap file 8070 megs instead of what I would have expected to be a over 16000