mirror of
https://github.com/feschber/lan-mouse.git
synced 2026-05-15 14:15:52 -06:00
[GH-ISSUE #295] Please improve documentation/UX #153
Labels
No labels
Xorg
documentation
enhancement
macos
pull-request
question
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/lan-mouse#153
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @satyamjay-iitd on GitHub (May 17, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/295
First of all thank you for creating this software. None of the sofware (barrier, inputleap, deskflow) worked for me for my setup because of the lack of Hyprland support, except lan-mouse. But I had to struggle a lot to get it to work.
I have the following setup:-
Left:- MacOS. (Main machine whose mouse and KB i want use to drive both the machines)
Right:- Hyprland
Following were my pain points:-
@DrYak commented on GitHub (Jul 28, 2025):
This is a bug #261 of the way the Rust crate (that lan-mouse happens to use) resolves name: it always sends everything to the DNS server exclusively and normally DNS servers aren't supposed to resolve
.localnames, those names must always be handled by mDNS which is not handled by that crate.In addition to the IP another work around is to use the domain that is provided by your modem/router (
.home,.fritz.box, etc.) which will be resolved by its DNS and will work in lan-mouse.Third solution is to use tweaks that allow DNS resolvers to forward .local names to mDNS if available (I don't know about Mac OS. On Linux you can tweak your systemd-resolverd to do so, or add avahi2dns downstream of a local resolver)
Technically, you don't have to, but automatically moving back requires that the mouse is correctly captured on the remote.
And some remote only implement emulation (the remote can recieve mouse movements from lan-mouse), not capture (lan-mouse can know what's happening on the remote and knows that the mouse tries to leave the screen). It's partially explained covered in the capture table of the README, but reading that requires to understand how all elements work internally (apparently neither layer-shell nor libei work on Hyprland?).
Some good doc writer should write a simple ELI5 intro to these tables.
It's in this box:
but again requiring to understand internals (your Hyprland doesn't support libei so can't use the default combo to disconnetc?)
Again somebody should ELI5 it.
Do you get different IPs on each interface? (I guess given you example. I suppose you could try deleting the one IP from your Wifi network and keep only the IP from your wired connection):
Though this is not a guarantee that the Mac won't try to do something stupid
(Mac OS ⇒ Wifi connection ⇒ Router/Modem ⇒ Wired connection ⇒Linux machine on fixed IP).
That stupid thing is what literally my laptop does when in my University (tries to contact my workstation's fixed IP over Eduroam despite different networks), in which case the only sane solution is to simply temporarily turn Wifi off(*)
(*): Given how often my Mac-using colleagues need to do this to solve various networking problems (e.g. Zoom), I guess there's a high change you need to do that.
Sadly a limitation of how it works on non-libei backends (it's not getting/sending mouse input event it's trying to guess/send scrollbar motions). Tons of issues are opened around this.