Add NSL Mesh Router to Network Configuration Management

[BookJJun-IJ]

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

• Your additions are Free software
• Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
• Submit one item per pull request. This eases reviewing and speeds up inclusion.
• Format your submission as follows, where Demo and Clients are optional.
  Do not add a duplicate Source code link if it is the same as the main link.
  Keep the short description under 80 characters and use sentence case
  for it, even if the project's webpage or readme uses another capitalisation.
  Demo links should only be used for interactive demos, i.e. not video demonstrations.
  - [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
• Additions are inserted preserving alphabetical order.
• Additions are not already listed at awesome-selfhosted
• The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
• You have searched the repository for any relevant issues or PRs, including closed ones.
• Any category you are creating has the minimum requirement of 3 items.
• Any software project you are adding to the list is actively maintained.
• The pull request title is informative, unlike "Update README.md".
  Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
  "Remove aaa from bbb" for removing, "Fix license for aaa", etc.

---

Please take some time to answer the following questions as best you can:

• Why is it awesome?
  WireGuard-based mesh networking that provides automatic subdomain routing for Docker containers without manual configuration. Combines VPN security with container-native service discovery through Caddy Docker Proxy labels.

• Have you used it? For how long?
  Yes. Approximately 7-8 months since June 2025 release.

• Is this in a personal or professional setup?
  Both. Professional development for Yundera platform (pre-launch) and used in guest lectures on Docker networking at computer science departments in South Korea.

• How many devices/users/services/... do you manage with it?
  Multiple Docker Compose application deployments across development and educational environments. Used in workshops with groups of 20-30 students learning container networking.

• Biggest pros/cons compared to other solutions?
  Pros: Zero-configuration automatic routing via Docker labels, NAT-friendly (works behind firewalls), built-in health monitoring with auto-reconnection.
  Cons: Requires WireGuard kernel support and NET_ADMIN capability, needs public provider infrastructure (or self-host).

• Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
  Excellent provider-requester architecture for multi-user platforms with automatic subdomain allocation. Hot-reloadable YAML config for multi-provider setups. The {{upstreams}} template in Caddy labels makes container networking seamless.

[Technetium1]

The language should be Docker, and the license should be MIT