You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was trying to understand if kilo can handle routing in a partially meshed network of nodes.
I have configured kilo with mesh granularity set to full.
However, what happens if Wireguard fails to establish connections between some of the nodes?
E.g. due to UDP blocking corporate firewalls?
Does kilo manage to route the traffic through other peers?
The text was updated successfully, but these errors were encountered:
Kilo will not route traffic over other peers. Kilo cannot detect by itself if connections between nodes are blocked due to a firewall.
However, when you are not using a symmetric firewall or symmetric NAT, #146 makes it possible to establish a connection between nodes that are in different NATs or behind firewalls with UDP whole punching. For this to work, at least one node needs to have a routable endpoint (eg. the API server).
Thanks @leonnicolas for the explanation. This confirms my own understanding after digging into the code.
I could be a nice idea to extend Kilo with some sort of dead-peer detection.
This would allow us to detect nodes which are located behind symmetrics firewalls/NATs.
In such a case #189 could be used as a fall-back.
Hi, I was trying to understand if kilo can handle routing in a partially meshed network of nodes.
I have configured kilo with mesh granularity set to full.
However, what happens if Wireguard fails to establish connections between some of the nodes?
E.g. due to UDP blocking corporate firewalls?
Does kilo manage to route the traffic through other peers?
The text was updated successfully, but these errors were encountered: