summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authordlg <dlg@openbsd.org>2019-07-18 07:51:47 +0000
committerdlg <dlg@openbsd.org>2019-07-18 07:51:47 +0000
commit2e56b663b6a6f60e2c28bbbd4c6010817a9755dc (patch)
tree9623a58b0519efb457d134b4a0639a17e04836f3 /lib
parentbulk up the debug output around selection logic (diff)
downloadwireguard-openbsd-2e56b663b6a6f60e2c28bbbd4c6010817a9755dc.tar.xz
wireguard-openbsd-2e56b663b6a6f60e2c28bbbd4c6010817a9755dc.zip
run the selection logic from the rxm current state if the port is unselected
previously it would only run the selection logic if the peer information changed, but it is possible to be in the current state with stale partner info. that can happen if the port becomes disabled/disconnected, which unwinds the mux machine, but doesnt clear the partner info. when the link is enabled again we re-enter the current state, but because the partner info is the same we didn't run the selection logic, which in turn didn't let the mux machine move forward again.
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions