similar to: Wake-Up Call didn't work

Hi there! I just try to play with die wake-up function described in http://www.voip-info.org/wiki-Asterisk+tips+wake-up Everything looks fine but there seem to be missing some soundfiles like "wakeup-menu". Where can I get these files in order to make this feature usable? Regards Julian Pawlowski

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

On 2018?08?03? 11:24, Tonghao Zhang wrote: > On Fri, Aug 3, 2018 at 11:07 AM Jason Wang <jasowang at redhat.com> wrote: >> >> >> On 2018?08?03? 10:51, Tonghao Zhang wrote: >>> On Thu, Aug 2, 2018 at 5:23 PM Jason Wang <jasowang at redhat.com> wrote: >>>> >>>> On 2018?08?02? 16:41, Toshiaki Makita wrote: >>>>> On

On 2018?08?03? 11:24, Tonghao Zhang wrote: > On Fri, Aug 3, 2018 at 11:07 AM Jason Wang <jasowang at redhat.com> wrote: >> >> >> On 2018?08?03? 10:51, Tonghao Zhang wrote: >>> On Thu, Aug 2, 2018 at 5:23 PM Jason Wang <jasowang at redhat.com> wrote: >>>> >>>> On 2018?08?02? 16:41, Toshiaki Makita wrote: >>>>> On

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

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 2018?08?03? 12:04, Tonghao Zhang wrote: > On Fri, Aug 3, 2018 at 11:43 AM Jason Wang<jasowang at redhat.com> wrote: >> >> On 2018?08?03? 11:24, Tonghao Zhang wrote: >>> On Fri, Aug 3, 2018 at 11:07 AM Jason Wang<jasowang at redhat.com> wrote: >>>> On 2018?08?03? 10:51, Tonghao Zhang wrote: >>>>> On Thu, Aug 2, 2018 at 5:23 PM

Hi, i've set up a little mailserver for my homeoffice, and after some problems everything works fine for me, I've some virtual users which get their mail delivered via getmail, and I can access my mails from my windows mailclient. The only issue I'm still facing is, that I don't like to run getmail as a cronjob that connects to my online mailboxes every minute or so,

On 2018?08?03? 10:51, Tonghao Zhang wrote: > On Thu, Aug 2, 2018 at 5:23 PM Jason Wang <jasowang at redhat.com> wrote: >> >> >> On 2018?08?02? 16:41, Toshiaki Makita wrote: >>> On 2018/08/02 17:18, Jason Wang wrote: >>>> On 2018?08?01? 17:52, Tonghao Zhang wrote: >>>>>> +static void vhost_net_busy_poll_check(struct vhost_net *net,

On 2018?08?03? 10:51, Tonghao Zhang wrote: > On Thu, Aug 2, 2018 at 5:23 PM Jason Wang <jasowang at redhat.com> wrote: >> >> >> On 2018?08?02? 16:41, Toshiaki Makita wrote: >>> On 2018/08/02 17:18, Jason Wang wrote: >>>> On 2018?08?01? 17:52, Tonghao Zhang wrote: >>>>>> +static void vhost_net_busy_poll_check(struct vhost_net *net,

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

This patch series makes suspend support in qemu alot more useful. Right now the guest can put itself into s3, but qemu will wakeup the guest instantly. With this patch series applied the guest will stay suspended instead and there are a few events which can kick the guest out of suspend state: A monitor command, ps/2 input, serial input, rtc. Not much yet, but it''s a start with the

On 2018/08/03 12:24, Tonghao Zhang wrote: > On Fri, Aug 3, 2018 at 11:07 AM Jason Wang <jasowang at redhat.com> wrote: >> On 2018?08?03? 10:51, Tonghao Zhang wrote: >>> On Thu, Aug 2, 2018 at 5:23 PM Jason Wang <jasowang at redhat.com> wrote: >>>> On 2018?08?02? 16:41, Toshiaki Makita wrote: >>>>> On 2018/08/02 17:18, Jason Wang wrote:

On 2018/08/03 12:24, Tonghao Zhang wrote: > On Fri, Aug 3, 2018 at 11:07 AM Jason Wang <jasowang at redhat.com> wrote: >> On 2018?08?03? 10:51, Tonghao Zhang wrote: >>> On Thu, Aug 2, 2018 at 5:23 PM Jason Wang <jasowang at redhat.com> wrote: >>>> On 2018?08?02? 16:41, Toshiaki Makita wrote: >>>>> On 2018/08/02 17:18, Jason Wang wrote:

On 2018?08?02? 16:41, Toshiaki Makita wrote: > On 2018/08/02 17:18, Jason Wang wrote: >> On 2018?08?01? 17:52, Tonghao Zhang wrote: >>>> +static void vhost_net_busy_poll_check(struct vhost_net *net, >>>> + struct vhost_virtqueue *rvq, >>>> + struct vhost_virtqueue *tvq, >>>>

On 2018?08?02? 16:41, Toshiaki Makita wrote: > On 2018/08/02 17:18, Jason Wang wrote: >> On 2018?08?01? 17:52, Tonghao Zhang wrote: >>>> +static void vhost_net_busy_poll_check(struct vhost_net *net, >>>> + struct vhost_virtqueue *rvq, >>>> + struct vhost_virtqueue *tvq, >>>>

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 1579 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040705/76f81abb/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

On Tue, Apr 26, 2016 at 03:35:53AM -0400, Jason Wang wrote: > We don't stop polling socket during rx processing, this will lead > unnecessary wakeups from under layer net devices (E.g > sock_def_readable() form tun). Rx will be slowed down in this > way. This patch avoids this by stop polling socket during rx > processing. A small drawback is that this introduces some overheads

On Tue, Apr 26, 2016 at 03:35:53AM -0400, Jason Wang wrote: > We don't stop polling socket during rx processing, this will lead > unnecessary wakeups from under layer net devices (E.g > sock_def_readable() form tun). Rx will be slowed down in this > way. This patch avoids this by stop polling socket during rx > processing. A small drawback is that this introduces some overheads

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