A lightweight service that wakes up LAN machines via Wake-on-LAN when network traffic is detected on their spoofed IP addresses.
Wakupator is a lightweight Linux service that automatically wakes up machines on a local network using Wake-on-LAN when it detects incoming traffic destined for those machines. It solves the problem of energy waste by allowing servers and workstations to remain powered off until they are actually needed, then bringing them online seamlessly.
Home lab enthusiasts, small infrastructure administrators, and developers who run intermittent services (like game servers, media servers, or development environments) and want to reduce electricity consumption without sacrificing accessibility.
Developers choose Wakupator because it requires no firewall reconfiguration, works with any IP-based service, and is designed to be non-intrusive and easy to integrate into existing self-hosted setups—all while keeping dependencies minimal and operation transparent.
Automatically starts machines based on incoming traffic, using smart local IP spoofing and Wake-on-LAN.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Intercepts packets at the raw socket level before they reach the host firewall, eliminating the need for complex firewall reconfiguration as stated in the Advantages section.
Works with any IP-based service (TCP/UDP) at the network layer, independent of application protocols, making it versatile for various use cases like game servers or SSH.
Designed to reduce power consumption by waking machines only upon traffic detection, aligning with its 'sleep-until-needed' philosophy for intermittent services.
Detects when monitored machines are manually powered on and ceases spoofing, preventing network conflicts as highlighted in the Automatic Detection feature.
Admits in Limitations that services exposed to the internet, especially HTTP/HTTPS, can trigger unwanted wake-ups due to frequent scans, reducing reliability.
Requires disabling Duplicate Address Detection (DAD) on client machines for IPv6, a manual and error-prone step that can cause address conflicts if overlooked.
Must run with cap_net_raw and cap_net_admin capabilities, which poses security risks and requires careful setup, as noted in the Precautions section.
Limited to same local area network traffic, making it unsuitable for WAN or cloud-based environments without additional networking hurdles.