johnmaguire
commented
2 months ago Hi @diogotcorreia
time="2024-06-13T11:14:48Z" level=info msg="Handshake timed out" durationNs=22911866345 handshake="map[stage:1 style:ix_psk0]" initiatorIndex=42024764 localIndex=42024764 remoteIndex=0 udpAddrs="[[XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:e593]:58425 [XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:5e5c]:58425 94.XXX.XXX.XXX:58425 172.17.0.1:58425 192.168.1.2:58425]" vpnIp=192.168.100.2
This log line indicates that Nebula has sent handshakes to every host listed in udpAddrs and received no replies.
If you look above the "error" log lines, you'll see the following:
time="2024-06-13T11:14:25Z" level=info msg="Handshake message sent" handshake="map[stage:1 style:ix_psk0]" initiatorIndex=42024764 localIndex=42024764 remoteIndex=0 udpAddrs="[94.XXX.XXX.XXX:58425 172.17.0.1:58425 192.168.1.2:58425]" vpnIp=192.168.100.2
The errors regarding IPv6 addresses occur because you're on a network that doesn't support IPv6. When we try to "write" these packets, we receive an error, and log it. When writing the IPv4 packets, no such error occurs. These errors can be safely ignored. This may be addressed in a future version of Nebula / Mobile Nebula.
I have two lighthouses, 192.168.100.1 and 192.168.100.7. The latter has IPv6 connectivity while the former is IPv4-only.
Just FYI, it is advisiable to always use an IPv4 address in the static_host_map for Lighthouses as it gives the Lighthouse a chance to learn the public IPv4 address for a node. (i.e. Most IPv4 networks are NAT'd, so a laptop/phone/server on the network doesn't know the public IPv4 address and can't self-report it to the Lighthouse. The lighthouse learns the address via the "source" part of the handshake packet.) I see you are already doing this.
diogotcorreia
Logs:
I have two lighthouses, 192.168.100.1 and 192.168.100.7. The latter has IPv6 connectivity while the former is IPv4-only.
I'm trying to connect to 192.168.100.2 (Linux, with IPv6 connectivity), from an Android device 192.168.100.6 (without IPv4 connectivity).
It appears that the Nebula app is trying to do the handshake using only the two IPv6 addresses, and not the public IPv4 that is also known to the app (see last line of log).