Bruce Thompson

I have tried another experiment now. I have connected the same node to a different external network. Now the public IP associated with the node is: 201.191.199.28 I have the...

One more experiment. I have create a new certificate for the node using a new VPN IP (10.27.15.7). Same issue. I have also setup a new node in yet another...

One last piece to the puzzle. I have now put the node back in the original subnet where it was working. It is working fine once again. I guess Nebula...

> Given that the IP address is specified in the creation process, I think cutting a new cert pair would be needed to make this work. I tried that. See...

> AFAIK, The symmetric Nat (both side) cannot be punched by nebula's udp. I guess your host A and host B are both behind a symmetric Nat device, so they...

It would be a good feature/requirement to be able to re-route traffic through the lighthouse. Completely agree. I now have to have a backup VPN mechanism to use if Nebula...

Just thought I would comment about another related issue I am seeing with Nebula. I now have 3 Nebula VPNs running with about 10 nodes in each VPN. Each VPN...

Mike, Cause and effect was pretty clear on this. The second I cleared the NAT table on the router, I had complete connectivity between all node in the Nebula VPN....

The next time it happens, check the output of show nat translations and sudo conntrack -L Will do.                 Bruce T From: Mike Reply-To: slackhq/nebula Date: Monday, April 13, 2020 at...

Mike, It took a while, but I finally got disconnections on one of my Nebula VPNs again. I ran “show nat translations” on the VS Edgemax but can’t really make...