News for hackers. Stuff that matters.
Re:WireGuard is now in Linus' tree by fulafel on Wednesday January 29, 2020 @08:55AM (#22180439)
IPsec also supports this - give certs signed by a mutually tusted CA to all nodes and they can all communicate host-to-host in a full mesh without needing to reconfigure when adding a host etc.
Re:WireGuard is now in Linus' tree by LinuxBender on Wednesday January 29, 2020 @11:33AM (#22182391)
What they mean is that with tinc, you can connect from node A to node Z without A and Z being directly connected. Tinc discovers who is connected to whom and will route through nodes to reach one another dynamically in user space.

IPSec by itself can not do this without adding very complex route statements on each node and enabling packet forwarding. Tinc operates in user space and does not require kernel packet forwarding or any destination node specific route statements.

Re:WireGuard is now in Linus' tree by hwh on Wednesday January 29, 2020 @11:08AM (#22182020)
Can you please elaborate? As far as I see it, IPsec is encrypting traffic. IKE is for setup of security associations. What part of IPsec would do routing, and in this case: potentially multi-hop mesh routing?
Re:WireGuard is now in Linus' tree by fulafel on Wednesday January 29, 2020 @11:32AM (#22182382)
IKE obviously does the key management part, it's part of IPsec in this picture.

There is no separate mesh routing in this scenario, everyone just uses normal internet routing and addressing.