I just use a client file for OPNsense.

FYI, just in case anyone finds it handy, here is the ansible for installing netclient on Ubuntu:

# Add repo and install netclient
- name: add netclient apt-key
  apt_key: 
    url: https://apt.netmaker.org/gpg.key
    state: present 

- name: add netclient apt repository
  apt_repository: 
    repo: 'deb https:apt.netmaker.org stable main' 
    state: present 
    filename: netclient
    update_cache: yes

- name: install neclient
  apt: 
    name: netclient
    state: present
    update_cache: yes

https://github.com/gravitl/netmaker/pull/1797 here you go

some of those pointer references are spooky, i understand that maybe you don't think they could be nil now (i believe some of them can anyway) - but one small code regression (or even an otherwise-harmless change) and you've got a potential nil de-reference -> panic DoS bug on your hands

Thoughts on Gorilla possibly going into unmaintained status? https://github.com/gorilla/mux/issues/659

we will be refactoring our http controllers in the future and have taken this into consideration for sure

hello, a few months ago I installed netmaker on DigitalOcean as 1-click app. Now, i need to move it to AWS. How to do it safe? Downtime is OK, but loosing any data is not. Currently, it runs version 0.14.6

Very general steps: - open the required ports specified in the README on repo on new vps - copy your docker-compose.yml from that machine and adjust any traefik or caddy (I forget which proxy we were using at that time) files to point to right domains and ips - ensure you have docker, docker-compose, wireguard and wireguard-tools installed on the machine - migrate your DB, if on DO one click, you'd need to copy the netmaker.db file from the data dir in netmaker (or where it's mounted on the VPS) (while netmaker container is stopped) - copy that file into the dir your netmaker server will mount as it's data dir (see your compose) - then, ensure your domain is pointed to your new VPS in AWS - ensure your compose images for netmaker + netmaker-ui are still on v0.14.6 or look like how it looked on your DO droplet - ensure mosquitto broker is installed with correct mosquitto.conf configuration (copy mosquitto.conf into appropriate dir to be mounted from old machine) - docker-compose up -d (in dir that docker-compose.yml is) - check your dashboard to see if you can login and/or see your nodes - next step may not be necessary, but may speed up re-connecting with server* - restart your netclients (or run netclient pull), if the domains have been updated to new VPS, you should be good to go

Very general steps

Hello, I set up the oidc connection in netmaker and I would like to be able to login with it only, is there a possibility?

Morning, does anyone manage to run the version 0.17 with Traefik? I am having problems with the Broker, getting the message: "Dec 09 12:37:10 osmc netclient[15852]: [netclient] 2022-12-09 12:37:10 [mqpublish.go-252] publish(): could not connect to broker at broker.nm.domain:443"

Is it possible to use netmaker in docker-compose setup as Bastion VPN to access my AWS VPC? As I understand, I should set network_mode: host. But I did not manage to run it correctly.

it's probably better to set a dedicated machine to act as the bastion "node" rather than use the netmaker server, or to deploy an additional "node" on the netmaker server

When using Caddy how can I protect the prometheus from the enterprise stack using an ip allow list?

I assume one could use named matchers, hope this helps: - https://caddyserver.com/docs/caddyfile/matchers#named-matchers community question/answer - https://caddy.community/t/only-allow-certain-ips-to-access-the-server-in-reverse-proxy/11213

Thanks I will give it a try, because I don't want the prometheus to be public

Another question why did you reverted back to caddy instead of traefik?

Caddy has a simpler config

Hey, I just updated to using 0.17.0 with Caddy but now the exporter container from the ee stack can't connect to mq and is always exiting

And the Grafana container needs to be updated 😉 again since version 9.2.0 is old

Ah that will need an update, sorry about that

So community edition is free and then enterprise also has a free tier that I'd imagine is sufficient for most solo home users. So why would anyone do community edition? Just trying to understand the choices

the exporter should be updated

it s probably better to set a dedicated

Thank you the recommendation. It is really the best idea to create new node. Could please help me again? I have vpc in AWS in 10.20.0.0/16 range. I want to create network in netmaker to give access to the vpc for external clients. What I understand - I should create network with this ip range, add node which has real access to whole vpc, then make it ingress node, then create external clients. But there is a problem. When I use 10.20.0.0/16 as range in netmaker, it takes 10.20.0.1, 10.20.0.2 and so on ips. But node has another real ip (10.20.2.129) and 10.20.0.0-10.20.0.4 are reserved in AWS. But anyway, I have no access to vpc. Ideally, I should use 2 ip ranges - Virtual for nodes and real to access to vpc. For example, there is and option in pritunl for this. It has virtual networks (picture) How can I do the same in netmaker? Version is 0.14.6

Hi, since I installed the netclient on ubuntu val I keep getting the following error message in syslog : netclient mqhandler.go-258 UpdatePeers(): network Vpn error updating /etc/hosts file is locked … aborting. Any ideas about what my cause this issue ?

Hi since I installed the netclient on

It seems like after the 0.17.0 updates external clients are not working any more 😦 my iPhone using the Wireguard app can‘t connect and ping to the netmaker server also does not work when the vpn is on

Welp, this single comment answered one part I wanted to know 2nd part would be, how does netmaker work with NAT restricted stuff