similar to: WakeUp XEN-VMs

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

On 8/16/2017 7:49 AM, Chris Olson wrote: > 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 >

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

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

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,]

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

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

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

> 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

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've migrated a Windows7 vm from F17 to F20 and it appears to be working okay. Apparently when it's left idle for some period, it automatically goes into a pmsuspend state, and I'm unable to wake it. I've figured out the virsh dompmwakeup command, which then virsh shows it's running, but the vm is still unresponsive. It doesn't respond to ping and the display is just

Hi list, I've encountered a problem with wol. I'm not new to this but this time I found unwanted behaviuor. I'm triyng to wol another c7 machine. When I run ether-wake @mac the system is started. When I shutdown the system after 3 seconds it start again and again and again. To block this wol-loop I must disable wol on uefi or shutdown the switch. I don't know what check. Any

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

I''ve been mucking with xen for quite a while but recently started focusing on custom network setups. I''d like to be able to create VMs on the fly from a base image and set network settings in each without booting the image up. This strange setup is for a classroom environment. At the beginning of the quarter the instructor would run a script that creates all the

I am testing several Operating System Streaming products to streams virtual desktops. They always requires pxe boot but xen seems to have a pxe which is not suitable. I got the same problem with kqemu and kvm and I solved it using gpxe. With xen I tried to chainloading gpxe (following gpxe wiki) but hvmloader fails to load it (memory problem?). Any workaround

Hi, I hope someone can help me with this. Problem Dovecot writes to _/var/lib/dovecot/instances_ 1 up to 3 times a day, causing the system to wake up and disks to spin up. Details content of /var/lib/dovecot/instances : 1549073010 dovecot /var/run/dovecot /etc/dovecot/dovecot.conf --> only the timestamp is changed (to current time) when dovecot writes to this file --> during write the

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

On Thu, Feb 08, 2018 at 02:47:26PM +0100, David Hildenbrand wrote: > > Sure, I do understand that Red Hat (or any other vendor) is taking no > > support responsibility for this. At this point I'd just like to > > contribute to a better understanding of what's expected to definitely > > _not_ work, so that people don't bloody their noses on that. :) > >

fredag 27 oktober 2023 20:07:58 CET skrev Jim Klimov: > Hi, this does sound like a useful idea - although for the principle of > least surprise and for variation in deployments, I'd rather have it as a > (non-default state of a) configuration toggle that can be set via > `upsmon.conf`: whether this particular client exits after processing FSD or > not. The onus for the rest

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