Every traffic reset re-enabled its clients unconditionally, in the client record and in the traffic row a master treats as the client's state. A master forwards an inbound's scheduled reset and "reset all" to its nodes through the per-client reset calls, so a client disabled by hand on a node inbound came back on at the next scheduled reset. Each reset now decides, before it zeroes the counters, which of its clients the quota switched off, counting cross-panel usage, and re-enables only those; a client disabled below its quota keeps its record and traffic row off. The reset API docs say so. |
||
|---|---|---|
| .. | ||
| amneziawg | ||
| amneziawgkern | ||
| amneziawgnet | ||
| config | ||
| crypto/nodetoken | ||
| database | ||
| eventbus | ||
| logger | ||
| mtproto | ||
| nodee2e | ||
| pia | ||
| sub | ||
| testpg | ||
| tuic | ||
| tunnelmonitor | ||
| util | ||
| web | ||
| xray | ||