Replies: 2 comments
-
Hi there! Thanks for this write-up Im sure folk using lxc containers will find this super useful! I personally dont use them myself so I consider them not officially supported. As for PayPal you can send money directly to Keep an eye out, Im about a week out from releasing wag |
Beta Was this translation helpful? Give feedback.
0 replies
-
Oh yeah, if you were looking for an auth provider that you could self host. I cannot recommend keycloak strongly enough, super mature project and well hardened. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
looking for a VPN with MFA i stumbled upon wag.
Already using wireguard, this looked like a practical approach.
As I'm using Proxmox for allmost everything, i started deploying wag in an lxc container.
For using wireguard I added
on the corresponding lxc.conf on the Proxmox host
I was not able to use an unprivileged container as i had later problems with the wag process
I did not get arround it and then used a privileged container with nesting enabled.
( some advice to use it inside an unprivileged container? )
logged in as root
and installed wag inside /opt/wag
and then copy/paste the Full config example and the wag.service data from https://github.com/NHAS/wag inside
to get the service running later.
of course the service does not work at this point, we first have to adjust the config.json for our needs.
for routing to function you have to uncomment in
At home i have a special construct, as i'm using a access-router from my provider to access internet via dsl with pppoe and to use voip services. Behind i use an openwrt router as packet-filter, dns-filter, reverse-proxy and wireguard-vpn to access my private networks.To integrate wag i connected its lxc container with one network interface parallel to openwrt to get the wireguard port forwarded from my access-router. For the seccond interface i created a new vlan and firewall zone on openwrt to access my local networks.
so i edited /etc/network/interfaces to represent my interfaces and routing needs.
The first step with wag is like with a normal wireguard instance, everybody who has a valid configuration can access the endpoint.
To manage and allow access to your networks wag presents 3 services ( configure ports to your needs ).
The admin gui should only be accessible from the intranet and as i'm configuring the devices myself, also the api endpoint could only be accessed from my intranet. the authentication website is only accessible from inside the wireguard tunnel.
I also integrated my lets encrypt wildcard certificate for the three services and realized that it is important to the use the fullchain certificate. otherwise i was not able to access the sites.
Next problem was i could not access the authentication website ( and the external authprovider authelia ) after i established a successfull wireguard connection. I only got TLS handshake errors. Problem here was that i use wag behind my access-router and i had to reduce the wireguard MTU to 1380 , then everything was ok.
It seems to be the same problem like in #85
Now everything worked for me. I experimented with the policy rules and used only the default one *
My mobile is permanently connected to my home and so the internet access. For this 0.0.0.0/0 is inside "public routes" and my intranet networks belong to the "mfa routes" . So i can access intranet only authorized.
at the moment i'm experimenting with authelia, but there i still have problems.
here is my config.json ( ip's and keys are changed )
Thank you for this nice software NHAS!
Is there a possibility to donate with paypal?
Beta Was this translation helpful? Give feedback.
All reactions