-
Notifications
You must be signed in to change notification settings - Fork 110
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
Backup path? #47
Comments
Hi, |
Awesome, thanks! |
Great! :) waiting for the feature to come back! :) nice software! keep up the good work :) |
Thanks! I just commited the new backup code in mud -> angt/mud@e56abf5 |
This is an iperf3 with one 20mbit path and one 10mbit backup path.
|
nice! is it possible to bind each server path to a interface? |
Not yet, see #44. |
Merged in master, confirmed for the next release. |
I see paths can be added with a state of up, backup, and down. I added a path in the backup state, thinking it would only pass traffic when the path in the up state became degraded. This does not seem to be the case though... the backup path seems to act just like the up path. Is this by design? Is there a way to have a backup path that only passe traffic when the path(s) in the up state are degraded?
The text was updated successfully, but these errors were encountered: