Raspberry Pi WOL via cable

Headless Raspberry Pi set up: https://www.youtube.com/watch?v=9fEnvDgxwbI

curl -fsSL https://pkgs.tailscale.com/stable/debian/trixie.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null

echo 'deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian trixie main' | sudo tee /etc/apt/sources.list.d/tailscale.list

sudo tailscale up --ssh

sudo pacman -S wakeonlan

By default, the ethtool setting for Wake-on-LAN does not persist across reboots on most Linux systems. To make Wake-on: g permanent for your network interface (enp69s0), you have several reliable options:

1.

Create a custom systemd service that sets WOL after the network interface is up:

Create the service file /etc/systemd/system/wol@.service with the following content:


text
[Unit]
Description=Enable Wake-on-LAN for %i
Requires=network.target
After=network.target

[Service]
Type=oneshot
ExecStart=/usr/bin/ethtool -s %i wol g

[Install]
WantedBy=multi-user.target

Enable the service for your interface:
```
text
sudo systemctl enable wol@enp69s0.service
```
This ensures the command runs at every boot, after the network is initialized1 23.

2.

Alternatively, you can use a udev rule to apply the setting whenever the interface appears:

Create the file /etc/udev/rules.d/81-wol.rules with:
```
text
ACTION=="add", SUBSYSTEM=="net", NAME=="enp69s0", RUN+="/usr/bin/ethtool -s enp69s0 wol g"
```
This ensures the setting is applied every time the device is added (e.g., at boot or after suspend)45.

3.

If you manage your network with NetworkManager, you can set WOL via:


text
nmcli connection modify <connection-name> 802-3-ethernet.wake-on-lan magic

Replace <connection-name> with the actual connection name for enp69s0. This will set the WOL option at the NetworkManager level4.

When connecting two Linux devices directly via Ethernet (without a switch/router), common issues include:

: By default, neither side provides DHCP, so both devices may not get an IP address, resulting in connection errors.
NetworkManager Misconfiguration: If the connection profile is not set to "shared" or "link-local", automatic IP assignment may fail.
: Windows uses APIPA to assign addresses automatically, but Linux requires explicit configuration.

Option 1: Use NetworkManager's "Shared" Method

On your Arch system, run:


text
nmcli con add type ethernet ifname enp69s0 con-name direct-pi ipv4.method shared
nmcli con up direct-pi

This will assign a local IP and enable basic network sharing67.

: Manual Static IPs

Assign static IPs on both devices. For example:
- On Arch: sudo ip addr add 10.0.0.1/24 dev enp69s0
- On Raspberry Pi: sudo ip addr add 10.0.0.2/24 dev eth0
Now you should be able to ping each device from the other8.

Ensure the Ethernet cable is good and supports direct connections (modern devices usually auto-negotiate, but older ones may need a crossover cable).
Disable or configure firewalls if needed for testing.
If using Avahi/mDNS for .local hostnames, ensure nss-mdns is installed and configured on both systems6.

Task	Recommended Solution
Persist WOL setting	systemd service (`wol@enp69s0.service`) or udev rule
Fix direct LAN "connection errors"	Use NetworkManager's "shared" method or assign static IPs on both devices

By following these steps, you can make Wake-on-LAN persistent and resolve direct LAN connection errors between your Arch Linux system and Raspberry Pi.

Linux Setup Notes

Search This Blog