wag: No such file or directory

Edited config.json and added an IP address to a policy - 10.0.4.125/32 then tried to use reload.

            "group:infrastructure": {
                "Mfa": [
                    "10.0.4.24/32",
                    "10.0.4.125/32"
                ]
            },

sudo ./wag reload

2022/09/08 18:59:10 Unable to reload config:  Unable to load configuration file from : open : no such file or directory

Stop and start wag and if fires up as it should with the new rule.

Have to say I’m rather impressed by this so far. I was expecting it to add in lots of iptables rules that I could see happening, but I see it uses xdp ebpf - which must be where the cleverness hides.

If you have a mind for future expansion, I’d consider further authentication modules, maybe as plugins. LDAP, OpenIDC, maybe SAML, even a simple database auth.

Keep up the excellent work

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 16 (9 by maintainers)

Most upvoted comments

Should look like this on multiple config reloads now:

2022/09/09 07:43:38 Wag started successfully, Ctrl + C to stop
2022/09/09 07:43:41 Config reloaded
2022/09/09 07:45:32 Config reloaded
2022/09/09 07:45:33 Config reloaded
2022/09/09 07:45:33 Config reloaded

Have you rerun go build?

I did also do a binary release here: https://github.com/NHAS/wag/releases/tag/v1.0.4

NHAS on Sep 8, 2022

Ahhh, actually I see. On reload its wiping the path it tries to read. So then on the subsequent reload it has no path.

Sweet. latest commits should fix that.

NHAS on Sep 8, 2022