Repository navigation
Conversation
🥷 Ninja i18n – 🛎️ Translations need to be updatedProject
|
| lint rule | new reports | level | link |
|---|---|---|---|
| Missing translation | 5 | warning | contribute (via Fink 🐦) |
| Identical pattern | 154 | warning | contribute (via Fink 🐦) |
|
Thanks for your consideration In the hiddify-core v5.1.0 we have included AWG 3.1 |
AmneziaWG (WireGuard with junk packets and changed headers, so DPI does not see it as WireGuard) as its own protocol next to WireGuard, served by hiddify-core 5.1+ as an "awg" endpoint: nothing else to install. - settings: amneziawg_enable / port / subnet / server keys and the obfuscation values Jc, Jmin, Jmax, S1, S2, H1-H4 (migration _v190 generates them; off by default) - server: the AmneziaWG preset's hiddify-core config is an "awg" endpoint on amneziawg_port with one peer per user (their WireGuard keys, an address in the AmneziaWG subnet). The peer's name is the user's uuid, so hiddify-core's per-user stats count the traffic (usage, limits). Skipped on hiddify-core < 5.1.0. The relay row reaches the same endpoint, so only the direct row serves it. - clients: the Hiddify app 5.1+ gets an "awg" endpoint in its subscription; the AmneziaVPN / AmneziaWG apps get a .conf from /amneziawg (client core "amneziawg") - public ports, translations, admin UI labels Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
ok I send PR |
dbe13c1 to
50a6dc7
Compare
|
Agreed, thanks. I rewrote it on hiddify-core: AmneziaWG is now an One question: the client config is only given to the Hiddify app |
AmneziaWG (WireGuard with junk packets and changed headers, so DPI does not see it as WireGuard) as its own protocol next to WireGuard, served by hiddify-core 5.1+ as an
"type": "awg"endpoint. Nothing else to install (the earlier awg-quick version is replaced).What it does
amneziawg_enable(off by default),amneziawg_port, the subnet (10.91.0.1/fd42:42:91::1), the server key pair, and the obfuscation valuesjc,jmin,jmax,s1,s2,h1–h4. Migration_v190generates valid random values (jmin < jmax,s1 + 56 != s2, distincthvalues above 4) and syncs the presets.endpoint_othershell aroundhiddify-core/server/protocols/amneziawg: anawgendpoint onamneziawg_portwith one peer per user (their WireGuard keys, an address in the AmneziaWG subnet). The peer'snameis the user's uuid, so hiddify-core's per-user stats (metadata.Userfrom the peer) count the traffic for usage and limits. It is skipped on hiddify-core < 5.1.0. The relay row reaches the same endpoint through the relay, so only the direct row serves it (one endpoint per port).awgendpoint in its subscription (hiddify-core/client/presets/amneziawg);.conffrom/amneziawg(client coreamneziawg, one file or a zip, like/wireguard), also listed on the user page;Tested
py_compile; the server and client templates rendered with sample data: the server endpoint, the client endpoint with and withoutfinalmask, and the skips (hiddify-core 5.0.3, Hiddify app 5.0.2, sing-box). Not run on a server.Questions
>= 5.1.0, assuming the app's version is its core's. Is that right?_v190is also used by feat(config-health): option to hide configs that fail the check #130; whichever is merged second needs the next number.🤖 Generated with Claude Code