A new problem for me with version 0.14.1. I have two computers, one plugged in ethernet, another with Wi-Fi. They are in the same local network, with different VLANs, and the firewall prevents communications between them. back in 0.14.0, I forced them to be relayed by the server node. And that worked for me. But in version 0.14.1, it seems that Netmaker makes them communicate with each other directly even if they're relayed by the server node, and they won't connect. How should I prevent this?

We noticed some bugs in 0.14.1 that could be causing this, but it sounds like in this scenario it may just be the design. Our thinking was if there are multiple peers behind a relay on the same local network, they should communicate directly rather than over relay. I'm not sure if there is a good solution to this currently but will have a look

Thanks. Maybe it's a bug in version 0.14.0 that became a feature for me.😃 I know it's a edge case, but if there can be a real feature/toggle for this scenario, that will be great.

Yeah it might become a little complicated, we’ll need to think it through a bit

For now, I just make the one with the Wi-Fi connection to be an external client. Also, I find a bug that unattached external nodes can't be deleted. I have to directly modify the SQLite database.

@shy-family-23356 if you have any recreation steps for that bug, it would be extremely helpful. Several users have reported this but it's very difficult to recreate internally. We're having a hard time tracking down what exactly causes it.

It's very easy to reproduce. I just tested it with version 0.14.1. 1. Make a node as Ingress Gateway. 2. Add an external client from that node. 3. The Ingress Gateway node leaves the network (netclient leave -n **) 4. You can test it now that the newly added external client is attached to none & won't be able to be deleted.

Thanks for this info. We'll look to have a fix in the next release