-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Autoconnect to group not working #210
Comments
Also i confirm that this bug exists. Do you have a solution? Thanks |
Unfortunately not at the moment. I tried the command line params, however they for some reason are ignored - and headless mode doesn't want to work either (I reported another bug here as well) |
Hello, i also tried with cli params but the result is the same. Is there in your opinion any way to check if the software is connected to a group? Thanks |
Well, that's an interesting idea - didn't think about it tbh. Right now I understand if the connection happened by visually looking at another Sonobus - if the list is complete, e.g. all the clients are there. Not automated :) but does the job. Maybe some reverse engineering to understand what is going on would be good. |
@lilok , I have figured out one interesting point:
So basically that AOO server logs can be analyzed - maybe. there will be connection information stored as well. |
This is my temporary workaround to check group (server) connection: CHECK_CONNECTION=$((netstat -tapn 2> /dev/null) | grep sonobus | grep 10998) if empty, else... :) |
Awesome, thanks a lot! :) |
Steps to reproduce:
Expected behaviour: the application should auto-connect to the last group
Platforms where tested and the bug was reproducible:
Sonobus version afffected:
The text was updated successfully, but these errors were encountered: