-
-
Notifications
You must be signed in to change notification settings - Fork 593
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
fix(networkmonitor): false engine restarts #3355
base: main
Are you sure you want to change the base?
fix(networkmonitor): false engine restarts #3355
Conversation
Please do not merge until go-netroute gets updated and merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this change RTM_CHANGE
could also make sense. Would you mind testing that with route change ...
?
Can you also add some comments why we're doing this differently on bsd (multiple 0.0.0.0/0
etc)
Network monitor should only trigger engine restarts when `route get` actually changes. There are many other instances when unspecified address get added to the system without actually affecting the real default route. fixes netbirdio#3352
a238f3e
to
91dd571
Compare
With the newest changes, this is the log when I pull out my usb-c wired connection
|
|
Once the go-netroute PR is merge I can update the go.mod file |
Describe your changes
Network monitor should only trigger engine restarts when
route get
actually changes. There are many other instances when unspecified address get added to the system without actually affecting the real default route.** change depends on **
netbirdio/go-netroute#5
Issue ticket number and link
fixes #3352
Checklist