[GH-ISSUE #1399] Recognise change in IP on a new network #1081

New issue

Open

opened 2026-05-05 07:27:27 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:27:27 -06:00

Owner

Originally created by @shymega on GitHub (Nov 5, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1399

Discussed in https://github.com/debauchee/barrier/discussions/1325

^{Originally posted by rengolin October 19, 2021}
I use my barrier server (Windows laptop) on both office and home, each of which has a desktop with the client always running.

Whenever I disconnect and reconnect, the client re-connects fine. But when I move from office to home or vice-versa, I can see in the logs that the connects but the kvm sharing doesn't work. When I restart the server (and sometimes the client too), it works fine.

I'm guessing it's because the server is still running with the previous IP, even though it seems to bind 0.0.0.0 (otherwise the client wouldn't be able to connect).

Perhaps this is a configuration issue, perhaps it's a security issue. Regardless, there could be a configuration to say "when I connect to this network, restart the server before accepting client connections".

Or perhaps I'm not doing something right, and I'd be glad if someone has a better solution than having to restart both client and server every time.

Originally created by @shymega on GitHub (Nov 5, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1399 ### Discussed in https://github.com/debauchee/barrier/discussions/1325 <div type='discussions-op-text'> <sup>Originally posted by **rengolin** October 19, 2021</sup> I use my barrier server (Windows laptop) on both office and home, each of which has a desktop with the client always running. Whenever I disconnect and reconnect, the client re-connects fine. But when I move from office to home or vice-versa, I can see in the logs that the connects but the kvm sharing doesn't work. When I restart the server (and sometimes the client too), it works fine. I'm guessing it's because the server is still running with the previous IP, even though it seems to bind 0.0.0.0 (otherwise the client wouldn't be able to connect). Perhaps this is a configuration issue, perhaps it's a security issue. Regardless, there could be a configuration to say "when I connect to this network, restart the server before accepting client connections". Or perhaps I'm not doing something right, and I'd be glad if someone has a better solution than having to restart both client and server every time.</div>

No labels

Rows
Columns