summaryrefslogtreecommitdiffstats
path: root/sys/dev/fdt/sxiccmu_clocks.h
diff options
context:
space:
mode:
authorpatrick <patrick@openbsd.org>2018-01-05 19:06:37 +0000
committerpatrick <patrick@openbsd.org>2018-01-05 19:06:37 +0000
commit750cbd98d3b5aacb8f4b21b57933b7df7fbbdf11 (patch)
tree3f1cb4bc5137c5dfc7aac89a9fa32c5d39c19f8d /sys/dev/fdt/sxiccmu_clocks.h
parentSync with the code in libc (diff)
downloadwireguard-openbsd-750cbd98d3b5aacb8f4b21b57933b7df7fbbdf11.tar.xz
wireguard-openbsd-750cbd98d3b5aacb8f4b21b57933b7df7fbbdf11.zip
When we receive an AUTH or ASSOC event even though we have already
reached the RUN state, this probably means that we have roamed to a different AP. In that case throw us back into SCAN mode and let the stack look for a new AP to connect to. In the future it might be worthwhile to use the ROAM event information to read the new AP information to adjust our stack, but that is further down the road.
Diffstat (limited to 'sys/dev/fdt/sxiccmu_clocks.h')
0 files changed, 0 insertions, 0 deletions