does not fix it, also tried private browser/incognito

that is interesting, I do not see that

It would only do that if the data wasn't cleared from an 11.1 instance database (upgrade), but really the performance won't change if you're worried about that

no biggie though, it is friday and nearly time for some dinner. ill open up an issue later on 🙂

Hmm, still having this issue, I added a mobile/external client through an ingress node (the main server) and also can't ping network devices.

are you using udp punching by any chance?

Yes, I imagine it's needed for devices on UDP

can you try it without? Wireguard always works over UDP, hole punching is mostly used for natted clients, but can sometimes give issues.

Oh, hey, I think that worked

Thanks @User , is UDP hole punching just a bit buggy then? It seems to have completely prevented connections, now the devices seem to be connecting directly, not even touching the Netmaker server.

Hole punching is mostly used for when 2 lan devices need to comminicate

Without they will indeed directly connect on the standard wg port

Well that's pretty sick. You have restored my hope in Netmaker! (Including help from dlrow_olleh and feiszli)

So the only other issue I'm seeing right now is that my external client doesn't seem to be able to connect (ssh) to devices on the network. I'm also not able to ssh to the netmaker server via LAN IP, only public IP. Pings work, and I can use Netmaker IPs for SSHing between the two devices.

ah yeah that is something we still need to solve, for now remove ssh from the port forwarding in your docker file

and put it down and up again, then ssh should work

I was going to say, I just noticed that other traffic via IP is working from an external node

So, what works works well, but I'm seeing inconsistent issues with certain hosts not being able to reach each other. UDP Hole punching, while on by default, is disabled everywhere, though I have tried enabling it to see if it makes a difference. Out of 4 hosts, none can see all other hosts, but most can see one or two of the others. I've tried restarting some of the hosts as well as the Netmaker server itself, and it's all just inconsistent. It feels like NAT stuff, but one time two devices on the same network couldn't see each other but could see outside devices, then after rebooting both they see each other, but not outside devices.

Hmm

@User any idea?

Is the API documentation up to date on 0.12.0? I am running into an issue with using the MAC address of nodes documented in the screenshot. It works with the node ID, but not the mac

Yeah it should be Node ID as of 0.10

Thank you @User Is there an updated doc that I should be using? I am going off the docs.netmaker.org and it says 0.12.0. I can email info@gravitl.com if that is the best route to get this updated?

I think they just need to be updated, we've been busy working on features, but we're starting to get back into stability/refactoring docs and what not

I'm blown away by the progress, and working through building a POC for an enterprise deployment. Happy to provide feedback and document anything I run into like this if it would be valuable to the team

Definitely, we always welcome feedback. We still have a ways to go

If this is for enterprise, you may wanna speak to @jolly-london-20127

@User great, I will document my experience and send any feedback your way. I would be happy to talk with @User. Can we get at clients on gateways through the API (it would be awesome if this was documented and I am happy to help do so)? I do see we can create them but I'm looking for a little more control to sync between internal systems and netmaker

you're looking to create ext clients via API?