mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #684] only tcp v6 listen port #542
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#542
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 @antonio-irarrazaval on GitHub (May 22, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/684
Operating Systems
Server: Linux Mint 19
Client: Windows 10
Barrier Version
2.3.2
Steps to reproduce bug
1- open barrier on linux, start as server and the windows 10, claims with connection refuse. Its try to connect to 192.168.0.26:24800 (linux server)

2- in linux server, get the listen tcp port:
the process running was:
/usr/bin/barriers -f --no-tray --debug INFO --name ant1-MS-7A70 --enable-crypto -c /tmp/Barrier.TJ4947 --address :24800There's no tcpv4 listen port. To solves, need to explicit the binding tcp v4 ip .... change the barrier config and lunch as:
/usr/bin/barriers -f --no-tray --debug INFO --name ant1-MS-7A70 --enable-crypto -c /homne/ant1/barrier.conf --address 0.0.0.0:24800the change was , and then, the listening port with tcp v4 its ok.

the barrier client immeadiatle connect the the server with success at the first try.
theres another way to change the binding ip? Every server reboot, need to stop de barrier startup and the lunch manually the new script.
Best regads!
@antonio-irarrazaval commented on GitHub (May 22, 2020):
I forgot to mention:
best regard
@github-actions[bot] commented on GitHub (Sep 22, 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.
@p12tic commented on GitHub (Jan 10, 2021):
Let's not close valid bug reports.