github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #578] Where to find info on what options like "auto config" do? #455

New issue

Open

opened 2026-05-05 06:27:14 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 06:27:14 -06:00

Owner

Originally created by @nixoye on GitHub (Mar 2, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/578

I can't find any information on what certain settings like auto config do.

Originally created by @nixoye on GitHub (Mar 2, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/578 I can't find any information on what certain settings like auto config do.

gitea-mirror commented

2026-05-05 06:27:18 -06:00

Author

Owner

@akostikov92 commented on GitHub (Mar 3, 2020):

https://github.com/symless/synergy-core/wiki
It's pretty well documented.

I know for me auto config was assigning an ip address that couldn't communicate with my server ip. If you look at the command line section at the link above you will see all the options and flags that could be set when the process starts. Hope that helps.

@akostikov92 commented on GitHub (Mar 3, 2020): https://github.com/symless/synergy-core/wiki It's pretty well documented. I know for me auto config was assigning an ip address that couldn't communicate with my server ip. If you look at the command line section at the link above you will see all the options and flags that could be set when the process starts. Hope that helps.

gitea-mirror commented

2026-05-05 06:27:21 -06:00

Author

Owner

@nixoye commented on GitHub (Mar 9, 2020):

@akostikov92 is there no documentation for Barrier though? Some sections in that wiki link you to the symless website which requires an account to read whats posted. I can't find auto config information

@nixoye commented on GitHub (Mar 9, 2020): @akostikov92 is there no documentation for Barrier though? Some sections in that wiki link you to the symless website which requires an account to read whats posted. I can't find auto config information

gitea-mirror commented

2026-05-05 06:27:24 -06:00

Author

Owner

@akostikov92 commented on GitHub (Mar 11, 2020):

If on Linux from command line...
ps aux | grep -i barrier

You should see something like...
ak 2422 0.0 0.5 673092 72176 tty2 Sl+ 10:46 0:03 barrier ak 2668 0.3 0.2 155336 33480 tty2 Sl+ 10:47 1:18 /snap/barrier/83/usr/bin/barrierc -f --no-tray --debug ERROR --name ubuntu18-ws --enable-crypto [10.17.0.100]:24800

Notice the second line...

usr/bin/barrierc
barrierc --> client
barriers --> server
barrierd --> daemon

auto-config setting is only applicable to client configuration though, so if you start / restart barrier with auto-config enabled, you can run the "ps aux | grep -i barrier" command and see which flags are set. Each of the flags represents a configuration setting that can be set manually. I was able to find a complete list of flags by running barrierc --help, from a manual installation on Fedora, but not from my current Snap installation.

My output above shows

-f--no-tray (maps to minimize to tray)
--debug (debug level)
--name (hostname)
--enable-crypto (ssl enabled)
[10.17.0.100]:24800 (server [ip address] :port)

If you're running it on windows. From command line...

regedit

There will be two entries:
The will show the value of different configuration settings that are set.
Computer\HKEY_CURRENT_USER\Software\Debauchee\Barrier

The second will show the command used to start the process and which flags are set:
Note: I am using Windows as my server "barriers.exe" so some of the settings shown won't be relevant / available to client auto-config.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Barrier
C:/Barrier/barriers.exe -f --no-tray --debug ERROR --name akMSI --ipc --stop-on-desk-switch --enable-drag-drop --enable-crypto --profile-dir "\AppData\Local\Barrier" -c "/AppData/Local/Temp/Barrier.gyTGqD" --address :24800

Final thing, I'll say is... I think it's best to not use auto-config. Maybe even set the server to ignore auto-config requests. Set things up manually so you know what's enabled.

Running Ubuntu 18. The Snap installation ran out of the box, but a different build from Ubuntu Software wouldn't connect.

@akostikov92 commented on GitHub (Mar 11, 2020): If on Linux from command line... `ps aux | grep -i barrier` You should see something like... `ak 2422 0.0 0.5 673092 72176 tty2 Sl+ 10:46 0:03 barrier ak 2668 0.3 0.2 155336 33480 tty2 Sl+ 10:47 1:18 /snap/barrier/83/usr/bin/barrierc -f --no-tray --debug ERROR --name ubuntu18-ws --enable-crypto [10.17.0.100]:24800 ` Notice the second line... > usr/bin/barrierc barrierc --> client barriers --> server barrierd --> daemon auto-config setting is only applicable to client configuration though, so if you start / restart barrier with auto-config enabled, you can run the "ps aux | grep -i barrier" command and see which flags are set. Each of the flags represents a configuration setting that can be set manually. I was able to find a complete list of flags by running `barrierc --help`, from a manual installation on Fedora, but not from my current Snap installation. My output above shows -f--no-tray (maps to minimize to tray) --debug (debug level) --name (hostname) --enable-crypto (ssl enabled) [10.17.0.100]:24800 (server [ip address] :port) If you're running it on windows. From command line... `regedit` There will be two entries: The will show the value of different configuration settings that are set. Computer\HKEY_CURRENT_USER\Software\Debauchee\Barrier The second will show the command used to start the process and which flags are set: Note: I am using Windows as my server "barriers.exe" so some of the settings shown won't be relevant / available to client auto-config. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Barrier `C:/Barrier/barriers.exe -f --no-tray --debug ERROR --name akMSI --ipc --stop-on-desk-switch --enable-drag-drop --enable-crypto --profile-dir "\AppData\Local\Barrier" -c "/AppData/Local/Temp/Barrier.gyTGqD" --address :24800` Final thing, I'll say is... I think it's best to not use auto-config. Maybe even set the server to ignore auto-config requests. Set things up manually so you know what's enabled. Running Ubuntu 18. The Snap installation ran out of the box, but a different build from Ubuntu Software wouldn't connect.

gitea-mirror commented

2026-05-05 06:27:26 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 28, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 28, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:27:28 -06:00

Author

Owner

@mirh commented on GitHub (Oct 7, 2021):

https://github.com/symless/synergy-core/wiki/Core-User-FAQ#what-is-bonjour-and-why-do-i-care
fc045fc793/src/gui/src/MainWindow.cpp (L1252-L1254)

@mirh commented on GitHub (Oct 7, 2021): https://github.com/symless/synergy-core/wiki/Core-User-FAQ#what-is-bonjour-and-why-do-i-care https://github.com/debauchee/barrier/blob/fc045fc79326cef966405b1cc578e8f062ae5294/src/gui/src/MainWindow.cpp#L1252-L1254