A per-client reset the node never accepted stopped the delivery loop: resets queued before it were re-sent on every sync, each time wiping the usage made since, and those after it were never sent. Each reset now settles by itself, a refused one moves to the back of the queue, and the loop goes on until the context is spent. A node also delivered its master's reset to its own sub-nodes inline, so one silent sub-node held the master's request until it timed out and was replayed; the inline attempt now waits at most a second and the rest finishes, or stays queued, in the background. |
||
|---|---|---|
| .. | ||
| amneziawg | ||
| amneziawgkern | ||
| amneziawgnet | ||
| config | ||
| crypto/nodetoken | ||
| database | ||
| eventbus | ||
| logger | ||
| mtproto | ||
| nodee2e | ||
| pia | ||
| sub | ||
| testpg | ||
| tuic | ||
| tunnelmonitor | ||
| util | ||
| web | ||
| xray | ||