this is my network and I something for allow me connecting from 10.88.88.1 to 10.88.88.3

on netmaker I can only connect to 10.88.88.254

I thought that any Wireguard can do this

When you have a relay server and netmaker switches to use the relay. Will netmaker automatically fall back to peer to peer? If works again? Or does this not happen automatically

I see nobody know

knows

[demanu@fedora ~]$ ping 10.88.88.254 PING 10.88.88.254 (10.88.88.254) 56(84) bytes of data. 64 bytes from 10.88.88.254: icmp_seq=1 ttl=64 time=102 ms 64 bytes from 10.88.88.254: icmp_seq=2 ttl=64 time=70.1 ms ^C --- 10.88.88.254 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 70.096/85.823/101.550/15.727 ms [demanu@fedora ~]$ ping 10.88.88.3 PING 10.88.88.3 (10.88.88.3) 56(84) bytes of data. ^C --- 10.88.88.3 ping statistics --- 8 packets transmitted, 0 received, 100% packet loss, time 7156ms

now Tailscale ping to the same server

[demanu@fedora ~]$ ping 100.96.169.58 PING 100.96.169.58 (100.96.169.58) 56(84) bytes of data. 64 bytes from 100.96.169.58: icmp_seq=1 ttl=64 time=232 ms 64 bytes from 100.96.169.58: icmp_seq=2 ttl=64 time=59.5 ms 64 bytes from 100.96.169.58: icmp_seq=3 ttl=64 time=57.1 ms

why Netmaker is blocking connection between nodes in the same network while Tailscale works like a charm?

is there a bug or just tailscale works like this and netmaker doesnt have this option?

Automatic Peer-to-Peer Reset from Relay

Connection issues

where is the problem with connection?

connection between 10.88.88.1 and 10.88.88.2

soooo. I've finally gotten to deploying the maker of nets and I appear to be having trouble getting my meshes to work in anything but the hub spoke model

also what is the recommended way to get routing to different local subnets

both sets of networks I would like to accomplish this in have distinct non conflicting ipv4 and native ipv6

Ever since I upgraded to 1.16.2 my broker broke (heh), with this error when a client tries to connect: Client disconnected due to protocol error.

(not the internal ones that use port 1883 though)

Any ideas what might be causing this?

As fas as i know i correctly setup the broker in my nginx reverse proxy, using the stream() block

What version did you upgrade from?

Lack of Connectivity outside of Hub spoke model

From 1.16.0,but i did follow the upgrade instructions

Do another pull from each of your clients

For the fist tests, I have installed netmaker on one server and an ingress/egress gateway on the second. The reason is the limited IPv6 support inside docker. Is it secure to install netclient on the docker host to provide ingress and egress functionality and leave netmaker-1 docker for pure management? - If yes, is that something the project will keep supporting?

I also tried that, I even both recreated the docker clients and installed on the OS (Ubuntu) itself and connected with a join token

I am trying to start a netmaker instance using the guided install here: https://docs.netmaker.org/quick-start.html I have my own domain, so wanted to use that. I created the needed DNS entries. But I keep getting an error indicating that traefik cannot get a certificate. `traefik | time="2022-10-21T08:21:00Z" level=error msg="Unable to obtain ACME certificate for domains \"broker.netmaker.kri.st\": unable to generate a certificate for the domains [broker.netmaker.kri.st]: error: one or more domains had a problem:\n[broker.netmaker.kri.st] acme: error: 400 :: urn:ietf:params:acme:error:connection :: 94.130.105.201: Error getting validation data\n" providerName=http.acme ACME CA="https://acme-v02.api.letsencrypt.org/directory" routerName=mqtt@docker rule="HostSNI(

broker.netmaker.kri.st

)"` Why is this? And how do I fix it?

Address-Conflict when using multiple netclient-server-nodes when joining clients quickly