-
Notifications
You must be signed in to change notification settings - Fork 14
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
used wireguard port are not properly reported on testnet #556
Comments
I think one of the problem is here: Lines 445 to 453 in 328df45
If something goes wrong when we try to delete the network resource, the port is already been marked as free while it might be not. |
The way we keep track of the reserved port on the node is still not correct. |
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch
…tart (#570) * networkd: make reserved wireguard port persistant on disk fixes #556 Before this commit networkd would loose all the reserved port after a restart and thus publish a wrong list of reserved ports on BCDB. We now keep this list of reserved port on cache disk so it survive a restart. We still do clean up after a reboot since all the network resources are also going to be re-created so the list of reserved port will be rebuild from scratch * add cache package it allow to create a directory that is persistant or temporary in memory
This is an output of all the wireguard port marked as used for all the nodes from testnet.
While when I check the amount of network resource deployed on some nodes there should be more wireguard port marked as used.
This also make new provision of network fails cause user doesn't know which port is used or not. Which make there reservation failed with
The text was updated successfully, but these errors were encountered: