brad-defined
brad-defined
Nebula 1.6.0 is released with a Relay feature, to cover cases like a Symmetric NAT. https://github.com/slackhq/nebula/pull/678 Check out the example config to see how to configure a Nebula node to...
@michaelr524 The static_host_map is reloadable (with a HUP signal to the running Nebula process) starting with Nebula 1.6.0.
``` % go install github.com/pion/stun/cmd/[email protected] % stun-nat-behaviour 2>&1 | grep "NAT mapping" ``` NAT's come in many flavors, and Nebula works great even with both peers behind many types of...
Nebula 1.6.0 is released with a Relay feature, to cover cases like a Symmetric NAT. https://github.com/slackhq/nebula/pull/678 Check out the example config to see how to configure a Nebula node to...
You can update the rest of your nodes to 1.6 without waiting for the mobile update, which will take a couple weeks to push out. But, you may have access...
Nebula 1.6.0 is released with a Relay feature, to cover cases like a Symmetric NAT. https://github.com/slackhq/nebula/pull/678 Check out the example config to see how to configure a Nebula node to...
Nebula 1.6.0 is released with a Relay feature, to cover cases like a Symmetric NAT. https://github.com/slackhq/nebula/pull/678 Check out the example config to see how to configure a Nebula node to...
Can you use IPv6, released in Nebula 1.4.0, to solve your NAT issues? If both Nebula hosts support IPv6, the NAT problems ought to go away.
Nebula 1.6.0 is released with a Relay feature, to cover cases like a Symmetric NAT. https://github.com/slackhq/nebula/pull/678 Check out the example config to see how to configure a Nebula node to...
@faicker Nebula will try everything it can (as directed by its configuration) to connect to a host. So, if punchy is configured, it'll punchy. If relay is configured too, it'll...