Skip to content

fix no broadcast after disconnect#491

Merged
Eirenliel merged 1 commit intoSlimeVR:mainfrom
unlogisch04:fix_boardcast_afterdc
Nov 27, 2025
Merged

fix no broadcast after disconnect#491
Eirenliel merged 1 commit intoSlimeVR:mainfrom
unlogisch04:fix_boardcast_afterdc

Conversation

@unlogisch04
Copy link
Contributor

After a disconnect the trackers did not send a broadcast to discover the server but did directly try to send it to the server. So if for some reason the server did change its IP address the tracker had to be rebooted.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unrelated changes?

Copy link
Contributor Author

@unlogisch04 unlogisch04 Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh agree but also fixes upload speed to the board if you use vscode
should i change it back?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i would make it a separate pr. All tho its prob fine even rn who cares

Copy link
Contributor Author

@unlogisch04 unlogisch04 Nov 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now two PR

… not send a broadcast to discover the server but did directly try to send it to the server. So if for some reason the server did change its ip address the tracker had to be rebooted.
@unlogisch04 unlogisch04 force-pushed the fix_boardcast_afterdc branch from 1092eda to 504bf15 Compare November 17, 2025 22:33
@Eirenliel Eirenliel merged commit cc42ad0 into SlimeVR:main Nov 27, 2025
2 checks passed
@unlogisch04 unlogisch04 deleted the fix_boardcast_afterdc branch November 27, 2025 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants