- This topic has 2 replies, 2 voices, and was last updated 2 days, 14 hours ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
Is it possible to add Wireguard into the deployment and accessible through the web interface? I’m planning on providing internet at my repeater and it would be nice to be able to have WireGuard pre-installed so I can have the repeater controller tunnel back to my home network so I can easily access the controller from home?
I’ve used various VPN setups in the past (pptp, lpt2, and so on) and recently had WireGuard recommended to me. WireGuard is factory installed on the routers I use and is easy to setup. It would be nice to not have to dig into the OpenRepeater OS to add the package and keep it updated.
A possible solution might be to use a small travel route. I have used GL-iNet routers and they support Wireguard profiles. I do the opposite and have a VPN profile setup on my devices and I can VPN back into my home router (Unifi UDMP) and access anything on my network like it was local including my ORP test setup. I can use any number of options once in my network like file sharing, remote desktop/VNC, SSH, etc. I find this vastly more flexible and sure to do at the router level.
OpenRepeater is offered free of charge. Find out how you can support us.
My current plan is to have one of the T-Mobile home internet modules at the controller and just plug the Pi directly into it, without a router. Trying to keep the amount of equipment at a site reduced to a minimum. I’ve got WireGuard installed on my laptops and cell phones and it works great for a single device connecting back to my home network.
That is my thought process, but I’m sure I can scrounge up a spare mikrotik and set it between the T-mobile and the Pi.