also : do you use english language ? some languages just dont have the wireguard gui ...
WireGuard was enabled for select small target builds a year ago. It seems strange to me that it would have been enabled for this select group of small target devices without an intention of it actually working.
I don't actually need WireGuard support in the GUI as in theory it's configurable from the command line -- and maybe that was the intention for these devices from the start. But with the filesystem being read-only and USB support also not appearing to work, it's not clear how I could actually configure WireGuard when I can't even create the keys.
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Wed Feb 28, 2024 22:38 Post subject:
Reiteration of what I mentioned earlier, the config file has config EOP_TUNNEL commented out, however, the commits that fixed the one issue say that WireGuard requires it:
I haven't chased further down the rabbit hole to see if the other platform configs mentioned in the device config file are the issue or if the commented out config EOP_TUNNEL is culprit. I am replying to BrainSlayer's previous reply for further information. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I'd like to ask for some guidance here from those of you who better know how things work around here, being fully aware this is probably a low priority device and issue (though it begs the question of why WireGuard was added to this selection of 4MB devices). Should I be patient and hope this gets fixed? Or give up and explore a workaround?
As I see it, for a workaround I'd have to find a way to save WireGuard key and configuration by means of 1 of 3 ways:
- Get USB storage working (so far no luck)
- Use a startup script to setup WireGuard keys/config on each boot (currently not possible, as clicking any of the Edit buttons on the Commands page does nothing in either Firefox or Chrome)
- Find a way to save WG config and keys to the device from terminal. Is this possible through NVRAM set, perhaps?
