SSH Access Reference

Connection details for remote hosts. Aliases below assume a matching Host block in ~/.ssh/config on SERVER-PC. IPs and usernames are LAN-only or private-account tenancy; no secrets live in this file.

LAPTOP-KAI (MSI GE72 2QC, Ubuntu 24.04 side)

Field	Value
SSH alias	laptop-kai
Hostname	192.168.1.11
User	mpent
Auth	SSH key (ed25519)
Identity file	~/.ssh/id_ed25519 on SERVER-PC
Port	22 (default)
Sudo	passwordless for mpent
Dual-boot	Ubuntu 24.04 on secondary HDD (Disk 1), Windows 11 on Disk 0. Default boot is Ubuntu via GRUB2Win chainload.

Commands

ssh laptop-kai                                   # via ~/.ssh/config alias
/c/Windows/System32/OpenSSH/ssh.exe mpent@192.168.1.11  # direct from Git Bash on SERVER-PC

Known quirks

• Git Bash ssh fails with passphrase/agent mismatch. Always use the Windows native OpenSSH binary at /c/Windows/System32/OpenSSH/ssh.exe from Git Bash. Under PowerShell/cmd, the plain ssh mpent@192.168.1.11 works.
• WOL works only from Windows hibernation (S4), not shutdown (S5). Ubuntu WOL is NOT possible on this NIC. The alx driver (Atheros AR816x, enp4s0) does not support WOL; ethtool -s enp4s0 wol g returns netlink “Operation not supported”.
• Hibernate from SSH (Windows only): hibernate alias defined in C:\Users\mpent\scripts\hibernate.cmd.
• Wake from SERVER-PC (Windows target): powershell -f ~/scripts/wake-laptop.ps1 -Wait.
• MAC address: D8:CB:8A:80:C5:F6 (wired NIC, used for WOL magic packet).

Outbound SSH aliases configured on LAPTOP-KAI

Alias	Target	User	Key	Purpose
advin (also kc1)	208.84.101.84	root	~/.ssh/id_advin	GoLiveBro control plane + signal-feed Postgres

Remote hardware controls

All commands run over ssh laptop-kai (or via the explicit ssh.exe form). All writes below require sudo; mpent has passwordless sudo.

Laptop display backlight (Intel driver, range 0..488, 0 = off):

# off
echo 0 | sudo tee /sys/class/backlight/intel_backlight/brightness

# full
echo 488 | sudo tee /sys/class/backlight/intel_backlight/brightness

# read current
cat /sys/class/backlight/intel_backlight/brightness

MSI SteelSeries keyboard backlight (built-in, via gt683r_led kernel driver; 3 zones, each 0 or 1):

# all zones off
for zone in back front side; do
  echo 0 | sudo tee /sys/class/leds/0003:1770:FF00.0003::${zone}/brightness
done

# all zones on
for zone in back front side; do
  echo 1 | sudo tee /sys/class/leds/0003:1770:FF00.0003::${zone}/brightness
done

# mode (0 normal, 1 gaming, 2 breathing, 3 wave)
cat /sys/class/leds/0003:1770:FF00.0003::back/gt683r/mode

Note: the built-in MSI keyboard firmware can persist the pattern set on the Windows side. If sysfs shows all zones at 0 but lights still appear, check whether an external USB keyboard (below) is the actual source.

Logitech G513 RGB mechanical keyboard (external USB, VID 046d PID c33c, controlled via g810-led):

Package: g810-led (apt, already installed 2026-04-18).

# all keys off
sudo g810-led -dv 046d -dp c33c -a 000000

# all keys solid color (examples)
sudo g810-led -dv 046d -dp c33c -a 202020   # dim white
sudo g810-led -dv 046d -dp c33c -a 00a0ff   # cyan

# restore to default profile (if one is defined)
sudo g810-led -dv 046d -dp c33c -p

-a RRGGBB sets all keys. Keyboard firmware may reset on USB re-enumeration (unplug/replug or reboot); add a systemd unit running the desired command at boot if you want a persistent state.

Sources

Populated from reference_laptop_wol.md memory notes (2026-04-17 SSH setup session) and ~/.ssh/config on SERVER-PC.