YoungReckless4 35e09191de feat(amneziawg): support persistent keepalive ranges (#6881) ...

AmneziaWG clients accept a randomised PersistentKeepalive range such as 15-25,
which makes keepalive timing harder to fingerprint; the panel only stored a
single number. A client's keepalive may now be a range, validated the way
AmneziaWG parses it. The downloadable .conf and vpn:// profile carry the range,
Clash/Mihomo output gets its lower bound, and plain WireGuard stays scalar-only.
The range lives in an additive wg_keep_alive_range column, so the integer
column and an older panel binary keep working after a rollback.

2026-10-24 06:36:49 +02:00

..

emit_examples.go

feat(amneziawg): support persistent keepalive ranges (#6881)

2026-10-24 06:36:49 +02:00

emit_jsonschema_test.go

fix(api): preserve 64-bit integer schema formats (#5908)

2026-07-12 10:58:02 +02:00

emit_jsonschema.go

feat(amneziawg): support persistent keepalive ranges (#6881)

2026-10-24 06:36:49 +02:00

emit_types.go

feat(amneziawg): support persistent keepalive ranges (#6881)

2026-10-24 06:36:49 +02:00

emit_zod.go

feat(amneziawg): support persistent keepalive ranges (#6881)

2026-10-24 06:36:49 +02:00

main.go

feat(amneziawg): support persistent keepalive ranges (#6881)

2026-10-24 06:36:49 +02:00

schema.go

feat(amneziawg): support persistent keepalive ranges (#6881)

2026-10-24 06:36:49 +02:00

walker_test.go

feat(amneziawg): support persistent keepalive ranges (#6881)

2026-10-24 06:36:49 +02:00

walker.go

feat(amneziawg): support persistent keepalive ranges (#6881)

2026-10-24 06:36:49 +02:00