[BUG] Autoconnect to group not working

[Eugeniusz]

Steps to reproduce:

• allow automatic reconnect on startup
• create a connection to a specific group in GUI. Connect to it
• exit application "abnormally" - e.g. reboot a PC, kill it, whatever
• next startup - no automatic connection to the group. If exited "normally" - via "disconnect" and quit app - no issues.
  Expected behaviour: the application should auto-connect to the last group

Platforms where tested and the bug was reproducible:

• Windows 11
• Linux Debian (Raspbian)
• Not verified on MacOS

Sonobus version afffected:

• SonoBus version 1.6.2

[Gianluca Baù]

Also i confirm that this bug exists.

Do you have a solution?

Thanks

[Eugeniusz]

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)

[Gianluca Baù]

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?
I was thinking to check some packets with tcpdump periodically.

Thanks

[Eugeniusz]

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?
I was thinking to check some packets with tcpdump periodically.

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.
Oh, by the way, I've got an idea. If using not the "original" server for managing connections but your own server - I do use my own, so probably I can test it as well (there are instuctions on how to install it) - then probably there may be a way to get the information from it. I don't know right now how to get it exactly - investigation needed, however this might be easier than tcpdump.

[Eugeniusz]

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?
I was thinking to check some packets with tcpdump periodically.
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. Oh, by the way, I've got an idea. If using not the "original" server for managing connections but your own server - I do use my own, so probably I can test it as well (there are instuctions on how to install it) - then probably there may be a way to get the information from it. I don't know right now how to get it exactly - investigation needed, however this might be easier than tcpdump.

@lilok , I have figured out one interesting point:

aooserver -l|--logdir logdirectory Enables logging to file

So basically that AOO server logs can be analyzed - maybe. there will be connection information stored as well.

[Gianluca Baù]

@Eugeniusz-Gienek

This is my temporary workaround to check group (server) connection:

CHECK_CONNECTION=$((netstat -tapn 2> /dev/null) | grep sonobus | grep 10998)

if empty, else...

:)

[Eugeniusz]

@Eugeniusz-Gienek

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! :)