[lorenzo95]

That sounds intriguing! I'm looking forward to giving it a try. I've checked out the example configurations, and while there’s definitely a learning curve, it seems manageable. I use Babel over WireGuard myself and appreciate the ability to redistribute interfaces through inclusion and exclusion.

I’m curious if Nylon offers similar functionality. Can it redistribute a dummy /32 or a local /24 into the network? Also, how does it handle default route advertising? Would there be a risk of looping, similar to what happens with IPsec tunnels?

I also think this could really benefit from a Docker image to streamline setup.

[chenjq]

Thanks for the enthusiasm! You can definitely advertise a /32 or /24 prefix on a given router, and configure the routing separately. (you just need to turn on `nonetconfigure`)

Currently, there is no special handling for the default route, meaning that if you were to advertise 0.0.0.0/0, there might be a loop. Personally, I never tried it, but I don't think it would work. Do you know of a workaround?

When I get some time, I will try to improve docs a little bit, maybe add a setup script, and docker image like you suggested :)

[lorenzo95]

I believe WireGuard employs a strategy where it announces 0.0.0.0/1 and 128.0.0.0/1 instead of using a complete quad-zero. This allows your local default route to maintain a lower administrative distance. Interestingly, they implement it this way on Android, and it appears to work effectively for daily use.

I was just curious. It doesn't necessarily mean it has to be a supported use case.