Promote WireGuard from usermod to a core feature?
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 22/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Da chiarire
- Stato di attività
- Tranquilla
- Stack tecnologico
- cpp
- Ambito
- embedded-iot
Direzione di ricerca
This issue is a design discussion about compiling the existing WireGuard usermod into default ESP32 firmware (inactive until configured), not a scoped code change. Read the full thread and the current WireGuard usermod before any work; there is no named file, test, or acceptance criterion. Do not start until maintainers agree on scope, size, and defaults. The one-line restart-on-key-change note is a separate follow-up, not this issue.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Overview
Context: I work on and operate wled.online, a hosted WireGuard control plane for managing your WLED devices. It can proxy and provide other cool integrations. I'm trying to make WLED dead-simple to operate when you're away from home. But, what I'm proposing below benefits anyone running their own WireGuard gateway (home server, VPS, etc.), not just my service. WireGuard is a fantastic, self-hostable protocol.
Since most of us are running ESP32 boards, WireGuard is pretty much the only practical way to get an encrypted tunnel to a remote service. TLS's handshake and buffer requirements eat too much working memory. WireGuard's footprint is small. That's why wled.online is WireGuard-only.
The downside today: using the WireGuard usermod means building your own firmware. I set up a GitHub project to make prebuilt binaries with WireGuard available to everyone, but traction is low. I also see sign-ups where users clearly expect WireGuard to "just work" and give up when they discover it requires custom firmware.
So I wanted to gauge interest in promoting WireGuard from usermod to an official core feature.
To be specific about scope: compiled in by default for ESP32 boards, but inactive until configured. Happy to provide any data on the two controllers I manage via wled.online almost daily.
Describe alternatives you've considered
The MQTT integration is quite limited and is being reworked, which is great to see, but it will still run into the encrypted-connection problem. TLS will be heavy in both code size and working memory. MQTT will remain useful for homelab users or anyone with a local gateway, but WireGuard handles the remote case much better and doesn't require a second set of APIs.
Additional context
I mentioned the controllers I manage via WireGuard usermod. I just wanted to report that it's been very stable. The one bug I've hit: the interface doesn't restart when a public key changes, so a gateway config change requires a controller restart. I think it's a one-line change to fix this. I'm writing this to remind myself to open a PR to fix it 😅 .
If there's appetite for this, I will happily volunteer to do the work!
Are there any major red flags or blockers here? Would love to hear concerns before I start on anything.
- Lingua principale
- C++
- Stelle
- 18.8k
- Fork
- 4.4k
- Merge medio
- 4g 6h
- PR unite (30g)
- 12
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di wled/WLED
-
Gravimeter: bars turn black at full volume (uint8_t(segmentSampleAvg*8) overflows)Forse già presa @DedeHai l’ha presa 1 giorno fa. Apertabug confirmed
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
bug cannot reproduce
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
wled/WLED#5840 · 12 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
backburner enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
wled/WLED#4132 · 5 commenti · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
discussion enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
wled/WLED#3478 · 13 commenti ·
I maintainer di solito rispondono entro 1 giorno
Issue simili
-
Component: Python API
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
Vector35/binaryninja-api#8649 ·
I maintainer di solito rispondono entro 3 giorni
-
ai_p2 comp-parquet-reader-v3
Difficoltà 2/5 Mezza giornata Idoneità per principianti 66/100
ClickHouse/ClickHouse#124986 ·
I maintainer di solito rispondono entro 1 giorno
-
bug product: very_good_flutter_plugin
Difficoltà 1/5 1-3 ore Idoneità per principianti 78/100
VeryGoodOpenSource/very_good_templates#654 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
AcademySoftwareFoundation/OpenImageIO#5550 ·
I maintainer di solito rispondono entro 2 giorni