[GH-ISSUE #269] Can't get it to work on latest git (or stable version on arch) from arch to arch. Different errors for Desktop and Laptop

gitea-mirror commented

2026-05-05 22:11:11 -06:00

Owner

Originally created by @Froidoh on GitHub (Feb 21, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/269

Hello!

I use lan-mouse git on both of my machines (same commit). Using arch with niri as the environment

❯ lan-mouse --version
lan-mouse 0.10.0
tag:latest
commit_hash:89684e14
build_time:2025-02-21 13:07:10 +00:00
build_env:rustc 1.84.1 (e71f9a9a9 2025-01-27),stable-x86_64-unknown-linux-gnu

Now, I used lan-mouse in the past with sway, no problem. It does not work with sway either, currently!

Note that I switched the port, but, well... it doesn't work with the default port either.

From my desktop, when I try to go to my laptop, I get this:

[2025-02-21T13:22:37Z INFO  lan_mouse::connect] client 0 connecting ...
[2025-02-21T13:22:37Z INFO  lan_mouse::connect] client (0) connecting ... (ips: [192.168.1.161:4243])
[2025-02-21T13:22:37Z INFO  lan_mouse::connect] connecting to 192.168.1.161:4243 ...
[2025-02-21T13:22:42Z WARN  lan_mouse::connect] failed to connect to 192.168.1.161:4243: `Connection timed out`

While the other way around I get this:

[2025-02-21T13:23:50Z INFO  lan_mouse::connect] client 0 connecting ...
[2025-02-21T13:23:50Z INFO  lan_mouse::connect] client (0) connecting ... (ips: [192.168.1.217:4243])
[2025-02-21T13:23:50Z INFO  lan_mouse::connect] connecting to 192.168.1.217:4243 ...
[2025-02-21T13:23:50Z WARN  lan_mouse::connect] failed to connect to 192.168.1.217:4243: `Alert is Fatal or Close Notify`

What am I doing wrong, what can I do to fix this?

Originally created by @Froidoh on GitHub (Feb 21, 2025). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/269 Hello! I use lan-mouse git on both of my machines (same commit). Using `arch` with `niri` as the environment ``` ❯ lan-mouse --version lan-mouse 0.10.0 tag:latest commit_hash:89684e14 build_time:2025-02-21 13:07:10 +00:00 build_env:rustc 1.84.1 (e71f9a9a9 2025-01-27),stable-x86_64-unknown-linux-gnu ``` Now, I used lan-mouse in the past with sway, no problem. **It does not work with sway either, currently!** Note that I switched the port, but, well... it doesn't work with the default port either. From my desktop, when I try to go to my laptop, I get this: ``` [2025-02-21T13:22:37Z INFO lan_mouse::connect] client 0 connecting ... [2025-02-21T13:22:37Z INFO lan_mouse::connect] client (0) connecting ... (ips: [192.168.1.161:4243]) [2025-02-21T13:22:37Z INFO lan_mouse::connect] connecting to 192.168.1.161:4243 ... [2025-02-21T13:22:42Z WARN lan_mouse::connect] failed to connect to 192.168.1.161:4243: `Connection timed out` ``` While the other way around I get this: ``` [2025-02-21T13:23:50Z INFO lan_mouse::connect] client 0 connecting ... [2025-02-21T13:23:50Z INFO lan_mouse::connect] client (0) connecting ... (ips: [192.168.1.217:4243]) [2025-02-21T13:23:50Z INFO lan_mouse::connect] connecting to 192.168.1.217:4243 ... [2025-02-21T13:23:50Z WARN lan_mouse::connect] failed to connect to 192.168.1.217:4243: `Alert is Fatal or Close Notify` ``` What am I doing wrong, what can I do to fix this?

gitea-mirror closed this issue

2026-05-05 22:11:11 -06:00

gitea-mirror commented

2026-05-05 22:11:13 -06:00

Author

Owner

@feschber commented on GitHub (Feb 21, 2025):

Did you authorize the device you want to use?

Say, you want to control device A using device B, then you have to copy the certificat fingerprint of device B and authorize it on device A using the Authorize button.

It should look something like this on the receiving end:

@feschber commented on GitHub (Feb 21, 2025): Did you authorize the device you want to use? Say, you want to control device `A` using device `B`, then you have to copy the certificat fingerprint of device `B` and authorize it on device `A` using the `Authorize` button. It should look something like this on the receiving end: ![Image](https://github.com/user-attachments/assets/9b9d068c-d979-4dde-8f3e-d5e9296388c5)

gitea-mirror commented

2026-05-05 22:11:14 -06:00

Author

Owner

@Froidoh commented on GitHub (Feb 21, 2025):

First off: Thank you very much for taking the time to answer!

So this is mandatory now but wasn't before? In any case, I did, while it was running, then disabled the connection again and reenabled it... to no avail.

I have connections configured though... also it didn't save the fingerprints after a restart, so I'll need to manually put them in the config?

@Froidoh commented on GitHub (Feb 21, 2025): First off: Thank you very much for taking the time to answer! So this is mandatory now but wasn't before? In any case, I did, while it was running, then disabled the connection again and reenabled it... to no avail. I have connections configured though... also it didn't save the fingerprints after a restart, so I'll need to manually put them in the config?

gitea-mirror commented

2026-05-05 22:11:15 -06:00

Author

Owner

@feschber commented on GitHub (Feb 21, 2025):

The reason it was not mandatory before is because the traffic was unencrypted.

Yes, you currently need to either enter the fingerprint every time or put it in your config file. (see https://github.com/feschber/lan-mouse?tab=readme-ov-file#example-config)
You now need to configure the connection on the "controling" device only and authorize these devices on the "controlled" devices.

@feschber commented on GitHub (Feb 21, 2025): The reason it was not mandatory before is because the traffic was unencrypted. - Yes, you currently need to either enter the fingerprint every time or put it in your config file. (see https://github.com/feschber/lan-mouse?tab=readme-ov-file#example-config) - You now need to configure the connection on the "controling" device only and authorize these devices on the "controlled" devices.

gitea-mirror commented

2026-05-05 22:11:17 -06:00

Author

Owner

@Froidoh commented on GitHub (Feb 21, 2025):

@feschber thanks a bunch!

It works one way now... I can control the desktop from the laptop, but the other way around it says: "connection timed out"... it's weird.

I copied the config and of course I changed the fingerprint and the name of the controlling device. It's all correct, but no luck in the important direction so far!

Anyway, it's probably a layer 8 problem at this point (pebkac), so feel free to close this!

@Froidoh commented on GitHub (Feb 21, 2025): @feschber thanks a bunch! It works one way now... I can control the desktop from the laptop, but the other way around it says: "connection timed out"... it's weird. I copied the config and of course I changed the fingerprint and the name of the controlling device. It's all correct, but no luck in the important direction so far! Anyway, it's probably a layer 8 problem at this point (pebkac), so feel free to close this!

gitea-mirror commented

2026-05-05 22:11:18 -06:00

Author

Owner

@feschber commented on GitHub (Feb 22, 2025):

Are you using niri on both ends? What does the log say?

@feschber commented on GitHub (Feb 22, 2025): Are you using niri on both ends? What does the log say?

gitea-mirror commented

2026-05-05 22:11:19 -06:00

Author

Owner

@Froidoh commented on GitHub (May 23, 2025):

Are you using niri on both ends? What does the log say?

Yes, on both sides. I need to check the log again... on the desktop it says "connection timed out"

Maybe it's because I have 3 monitors on the desktop... (no weird flex, just a weird guess)

@Froidoh commented on GitHub (May 23, 2025): > Are you using niri on both ends? What does the log say? Yes, on both sides. I need to check the log again... on the desktop it says "connection timed out" Maybe it's because I have 3 monitors on the desktop... (no weird flex, just a weird guess)

gitea-mirror commented

2026-05-05 22:11:20 -06:00

Author

Owner

@Froidoh commented on GitHub (Aug 14, 2025):

So, finally found time to check again.

Latest build:

Desktop says, when I move the mouse over to where the laptop should be:

[2025-08-14T11:47:29Z INFO input_capture::layer_shell] adding capture for position right - using outputs: ["DP-3"] [2025-08-14T11:47:30Z WARN lan_mouse::capture] releasing capture: not connected [2025-08-14T11:47:30Z INFO lan_mouse::connect] client 0 connecting ... [2025-08-14T11:47:30Z INFO lan_mouse::connect] client (0) connecting ... (ips: [192.168.87.232:4243]) [2025-08-14T11:47:30Z INFO lan_mouse::connect] connecting to 192.168.87.232:4243 ... [2025-08-14T11:47:30Z INFO lan_mouse::service] entering client 0 ... [2025-08-14T11:47:35Z WARN lan_mouse::connect] failed to connect to 192.168.87.232:4243: Connection timed out``

Laptop says:

connecting to [fd73:...]
failed to connect to [fd73:...] address family not supported by protocol (os error 97)

@Froidoh commented on GitHub (Aug 14, 2025): So, finally found time to check again. Latest build: Desktop says, when I move the mouse over to where the laptop should be: `[2025-08-14T11:47:29Z INFO input_capture::layer_shell] adding capture for position right - using outputs: ["DP-3"] [2025-08-14T11:47:30Z WARN lan_mouse::capture] releasing capture: not connected [2025-08-14T11:47:30Z INFO lan_mouse::connect] client 0 connecting ... [2025-08-14T11:47:30Z INFO lan_mouse::connect] client (0) connecting ... (ips: [192.168.87.232:4243]) [2025-08-14T11:47:30Z INFO lan_mouse::connect] connecting to 192.168.87.232:4243 ... [2025-08-14T11:47:30Z INFO lan_mouse::service] entering client 0 ... [2025-08-14T11:47:35Z WARN lan_mouse::connect] failed to connect to 192.168.87.232:4243: `Connection timed out`` Laptop says: connecting to [fd73:...] failed to connect to [fd73:...] address family not supported by protocol (os error 97)

gitea-mirror commented

2026-05-05 22:11:20 -06:00

Author

Owner

@feschber commented on GitHub (Feb 7, 2026):

Sorry for the late reply, this somehow got lost.

Seems like your DNS is only resolving IPv6 addresses.
Could you try manually adding an IPv4 and see if that works?

@feschber commented on GitHub (Feb 7, 2026): Sorry for the late reply, this somehow got lost. Seems like your DNS is only resolving IPv6 addresses. Could you try manually adding an IPv4 and see if that works?

gitea-mirror commented

2026-05-05 22:11:21 -06:00

Author

Owner

@Froidoh commented on GitHub (Feb 8, 2026):

Yes, if I use the IP address instead of the hostname, it works. Thanks.

@Froidoh commented on GitHub (Feb 8, 2026): Yes, if I use the IP address instead of the hostname, it works. Thanks.

gitea-mirror commented

2026-05-05 22:11:22 -06:00

Author

Owner

@feschber commented on GitHub (Feb 8, 2026):

Still weird that IPv6 doesn't work though ...

@feschber commented on GitHub (Feb 8, 2026): Still weird that IPv6 doesn't work though ...

Rows
Columns

[GH-ISSUE #269] Can't get it to work on latest git (or stable version on arch) from arch to arch. Different errors for Desktop and Laptop #137