nebula
nebula copied to clipboard
slackhq
make default route via nebula node (full subnet routing, 0.0.0.0/0, etc.)
Wireguard do someting magic while settting
AllowedIPs = 0.0.0.0/0, ::/0
And all traffic will route by that wireguard peer.
But if set nebula's unsafe_route 0.0.0.0/0, it will failed to start:
level=fatal msg="failed to set mtu 1300 on route 0.0.0.0/0; file exists"
In fact, the routing of wireguard is also done through system routing. It can also be realized by system routing！
This is something we are interested in supported and I'll try to find time for it this year.
Hi @mrbluecoat (and other readers) - please show your support for this issue by adding a 👍 to the original post, which allows us to sort by votes. Commenting with a bump just creates noise for the maintainers. Thanks for understanding!
In the meantime, there's a bit of additional context here: https://github.com/slackhq/nebula/issues/307#issuecomment-1194547903
I ran a test, I might be totally wrong , however I think the issue with adding 0.0.0.0/0 via nebula IP, is that the handshake times out to reach the actual nebula server " at least this is what I think happens " so what I did was using https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator/ to exclude the nebula exit node IP , that gave me few routes to add, did that, reload my client and it works... I am sure there is a better way and maybe a correct way, but thought to put this here
I ran a test, I might be totally wrong , however I think the issue with adding 0.0.0.0/0 via nebula IP, is that the handshake times out to reach the actual nebula server " at least this is what I think happens " so what I did was using https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator/ to exclude the nebula exit node IP , that gave me few routes to add, did that, reload my client and it works... I am sure there is a better way and maybe a correct way, but thought to put this here
Did you add the routes under unsafe_routes? or did you add them on OS/System level (e.g. ip route add)?
I ran a test, I might be totally wrong , however I think the issue with adding 0.0.0.0/0 via nebula IP, is that the handshake times out to reach the actual nebula server " at least this is what I think happens " so what I did was using https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator/ to exclude the nebula exit node IP , that gave me few routes to add, did that, reload my client and it works... I am sure there is a better way and maybe a correct way, but thought to put this here
Did you add the routes under unsafe_routes? or did you add them on OS/System level (e.g. ip route add)?
via unsafe_router within nebula configs
