[macOS] Unable to ping its own IP about nebula HOT 6 CLOSED

I think this is a peculiarity of utun and the mode we have to use for nebula on osx, which is actually "Point-to-Point" mode. I think you can do the workaround here to make local traffic work:

https://superuser.com/questions/1283421/cant-ping-localhost-from-utun-interface

from nebula.

If we need to set pf redirect rule

rdr on utun0 from any to 192.168.100.2-> lo0

then we may need to know utun interface name in advance (for shell script files).
On my macOS Catalina, when I start nebula, it brings up utun4 (after the last utun) even I configured dev: neb0 or dev: utun6. Is there any way to fix the utun name?

from nebula.

utun does not have a way to set the device name sadly. You could use nebula-cert to print the ip address from the certificate and target the tun device that has been allocated that ip.

from nebula.

utun does not have a way to set the device name sadly.

It does, but water does not. There is a pull request that adds the functionality to water, but it's been sitting since august. Water in general seems to be neglected at the moment.

I've tested with the patched version of water and a modified tun_darwin.go, it works. Caveat is the device name must be of the form utun[0-9]+, basically you can pick the number. It's still useful to have a predictable interface name.

from nebula.

Does anyone else have an issue with reaching any other node than the lighthouse from a macOS (M1 chips w/ latest OS version - 11.4)? I cannot ping it's own nebula IP nor any other node that's connected to the same lighthouse.

from nebula.

Fixed in #501
Released in Nebula 1.6.0

from nebula.