wireguard-docs VS drago

I can’t find info about this in the quickstart guide. Are these the docs you’re talking about?

I think the official documentation is clear enough on the settings, and I don’t think the project can necessarily be blamed for others misinterpreting it. True, the AllowedIPs label can lead to some confusion for those who don’t read the docs. I think of it as those destination IPs that can be reached through the peer, and those source IPs that are accepted from the peer. See also this site: https://docs.sweeting.me/s/wireguard

You prolly should give a /32 on your interface ips. Here is this as well https://github.com/pirate/wireguard-docs. I don't understand exactly what you are trying to do, but if you are trying to pass traffic anywhere you need to enable packet forwarding at the Kernal level.

By the way, look at https://github.com/pirate/wireguard-docs

Thanks for the reply. I'm not sure which missing lines you're referring to though? According to this documentation, PostUp is used to run a command after the interface is initialised (same for PostDown, which apparently runs a command after the interface is deleted), but I'm not sure what commands exactly I'd need to run PostUp or PostDown for?

Find more example commands for inspecting the interface at https://github.com/pirate/wireguard-docs#inspect.

Great list, I'd add Drago as well, though it may be for more advanced use.

Yes, the plan is to add meshing as a plugin. Does this make sense to you? For a list of other plugin ideas, see https://github.com/seashell/drago/issues/43. Feel free to add your own :)

Cool! How does it compare to drago?