Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Toggling peers on Ubiquiti Edgerouter fails
See original GitHub issueDescribe The Problem
The good news is that with some slight tweaks to the dashboard.py file (as the default conf_location is not in /etc/wireguard), I was able to bring up the dashboard on a Ubiquiti Edgerouter running Wireguard. The bad news is that the toggles are not working – which appears due to the fact that the wg-quick script is not installed in this flavor of Wireguard.
I realize this this is more of an issue with the implementation of Wireguard on the EdgeOS of Ubiquiti’s routers, but wanted to call attention to the issue in case others are trying to get it running.
Expected Error / Traceback
[…]
10.10.10.10 - - [24/Apr/2021 20:01:52] "GET / HTTP/1.1" 200 -
/bin/sh: wg-quick: command not found
10.10.10.10 - - [24/Apr/2021 20:01:55] "GET /switch/iPhone HTTP/1.1" 302 -
[…]
To Reproduce
- Download the appropriate EdgeOS release of Wireguard from Github.
- Follow instructions to install on Edgerouter.
- Set up Wireguard as usual.
- Download & install wireguard-dashboard.
- Update
dashboard.pylines 8 & 51 to point to the folder containing the Wireguard config file (or, create /etc/wireguard and move the Wireguard config file there). - Start wireguard-dashboard and navigate to dashboard in browser.
- Try toggling a peer on.
OS Information:
- OS: EdgeOS v2.0.9-hotfix.1
- Python Version: 3.5.3
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
WireGuard on edgerouter is maintained and configured through the vyatta configuration system. Changes must be pushed to that (removing or adding peers) and committed. Interfacing with it is reasonably straightforward. Here is an example: https://github.com/whiskerz007/ubnt_get_wireguard/blob/master/get_wireguard.sh
Thank you for providing this, since I don’t own an edgerouter so I can’t do any testing on the OS. I will keep open this issue and hope come across this issue and could solve this issue 😃