Lan Mouse

Lan Mouse is a cross-platform mouse and keyboard sharing software similar to universal-control on Apple devices. It allows for using multiple PCs via a single set of mouse and keyboard. This is also known as a Software KVM switch.

Goal of this project is to be an open-source alternative to proprietary tools like Synergy 2/3, Share Mouse and an alternative to other open source tools like Deskflow or Input Leap (Synergy fork).

Focus lies on performance, ease of use and a maintainable implementation that can be expanded to support additional backends for e.g. Android, iOS, ... in the future.

blazingly fast™ because it's written in rust.

• Now with a gtk frontend

[!WARNING] DISCLAIMER: Until #200 is merged, all network traffic is unencrypted and sent in plaintext!

A malicious actor with access to the network could read input data or send input events with spoofed IPs to take control over a device.

Therefore you should only use this tool in your local network with trusted devices. I take no responsibility for any security breaches!

OS Support

Most current desktop environments and operating systems are fully supported, this includes

• GNOME >= 45

• KDE Plasma >= 6.1

• Most wlroots based compositors, including Sway (>= 1.8), Hyprland and Wayfire

• Windows

• MacOS

Caveats / Known Issues

[!Important]

• X11 currently only has support for input emulation, i.e. can only be used on the receiving end.

• Sway / wlroots: Wlroots based compositors without libei support on the receiving end currently do not handle modifier events on the client side. This results in CTRL / SHIFT / ALT / SUPER keys not working with a sending device that is NOT using the layer-shell backend

• Wayfire: If you are using Wayfire, make sure to use a recent version (must be newer than October 23rd) and add shortcuts-inhibit to the list of plugins in your wayfire config! Otherwise input capture will not work.

• Windows: The mouse cursor will be invisible when sending input to a Windows system if there is no real mouse connected to the machine.

For more detailed information about os support see Detailed OS Support

Installation

pacman -S lan-mouse

paru -S lan-mouse-git

# install lan-mouse (replace path/to/ with the correct path)
sudo cp path/to/lan-mouse /usr/local/bin/

# install app icon
sudo mkdir -p /usr/local/share/icons/hicolor/scalable/apps
sudo cp lan-mouse-gtk/resources/de.feschber.LanMouse.svg /usr/local/share/icons/hicolor/scalable/apps

# update icon cache
gtk-update-icon-cache /usr/local/share/icons/hicolor/

# install desktop entry
sudo mkdir -p /usr/local/share/applications
sudo cp de.feschber.LanMouse.desktop /usr/local/share/applications

# when using firewalld: install firewall rule
sudo cp firewall/lan-mouse.xml /etc/firewalld/services
# -> enable the service in firewalld settings

# compile in release mode
cargo build --release

# install lan-mouse
sudo cp target/release/lan-mouse /usr/local/bin/

# will end up in ~/.cargo/bin
cargo install lan-mouse

# you can find the executable in result/bin/lan-mouse
nix-build

cargo build --no-default-features --features wayland

Installing Dependencies for Development / Compiling from Source

brew install libadwaita pkg-config

sudo apt install libadwaita-1-dev libgtk-4-dev libx11-dev libxtst-dev

sudo pacman -S libadwaita gtk libx11 libxtst

sudo dnf install libadwaita-devel libXtst-devel libX11-devel

nix-shell .

nix develop

# install chocolatey
Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

# install gvsbuild dependencies
choco install python git msys2 visualstudio2022-workload-vctools

# install gvsbuild with python
python -m pip install --user pipx
python -m pipx ensurepath

pipx install gvsbuild

# build gtk + libadwaita
gvsbuild build gtk4 libadwaita librsvg adwaita-icon-theme

Usage

$ cargo run --release -- --frontend cli
(...)
> connect <host> left|right|top|bottom
(...)
> list
(...)
> activate 0

lan-mouse --daemon

cp service/lan-mouse.service ~/.config/systemd/user
systemctl --user daemon-reload
systemctl --user enable --now lan-mouse.service

Configuration

To automatically load clients on startup, the file $XDG_CONFIG_HOME/lan-mouse/config.toml is parsed. $XDG_CONFIG_HOME defaults to ~/.config/.

To create this file you can copy the following example config:

Example config

[!TIP] key symbols in the release bind are named according to their names in src/scancode.rs#L172. This is bound to change

# example configuration

# configure release bind
release_bind = [ "KeyA", "KeyS", "KeyD", "KeyF" ]

# optional port (defaults to 4242)
port = 4242
# # optional frontend -> defaults to gtk if available
# # possible values are "cli" and "gtk" 
# frontend = "gtk"

# define a client on the right side with host name "iridium"
[right]
# hostname
hostname = "iridium"
# activate this client immediately when lan-mouse is started
activate_on_startup = true
# optional list of (known) ip addresses
ips = ["192.168.178.156"]

# define a client on the left side with IP address 192.168.178.189
[left]
# The hostname is optional: When no hostname is specified,
# at least one ip address needs to be specified.
hostname = "thorium"
# ips for ethernet and wifi
ips = ["192.168.178.189", "192.168.178.172"]
# optional port
port = 4242

Where left can be either left, right, top or bottom.

Roadmap

• Graphical frontend (gtk + libadwaita)

• respect xdg-config-home for config file location.

• IP Address switching

• Liveness tracking Automatically ungrab mouse when client unreachable

• Liveness tracking: Automatically release keys, when server offline

• MacOS KeyCode Translation

• Libei Input Capture

• MacOS Input Capture

• Windows Input Capture

• Encryption (WIP)

• X11 Input Capture

• Latency measurement and visualization

• Bandwidth usage measurement and visualization

• Clipboard support

Detailed OS Support

In order to use a device for sending events, an input-capture backend is required, while receiving events requires a supported input-emulation and input-capture backend.

A suitable backend is chosen automatically based on the active desktop environment / compositor.

The following sections detail the emulation and capture backends provided by lan-mouse and their support in desktop environments / operating systems.

Input Emulation Support

• wlroots: This backend makes use of the wlr-virtual-pointer-unstable-v1 and virtual-keyboard-unstable-v1 protocols and is supported by most wlroots based compositors.

• libei: This backend uses libei and is supported by GNOME >= 45 or KDE Plasma >= 6.1.

• xdp: This backend uses the freedesktop remote-desktop-portal and is supported on GNOME and Plasma.

• x11: Backend for X11 sessions.

• windows: Backend for Windows.

• macos: Backend for MacOS.

Input Capture Support

• layer-shell: This backend creates a single pixel wide window on the edges of Displays to capture the cursor using the layer-shell protocol.

• libei: This backend uses libei and is supported by GNOME >= 45 or KDE Plasma >= 6.1.

• windows: Backend for input capture on Windows.

• macos: Backend for input capture on MacOS.

• x11: TODO (not yet supported)