| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
This makes the interface name available as an environment variable for
the pre/post hooks.
|
| | |
|
| |
|
|
|
|
|
| |
Sometimes (especially in the default route case) it is required to NOT
add routes for all allowed IP ranges. One might run it's own custom
routing on-top of wireguard and only use the wireguard addresses to
exchange prefixes with the remote host.
|
| |
|
| |
Do the right thing, and use multiple interfaces for policy routing. For example, WireGuard interfaces do not allow multiple routes for the same CIDR range.
|
| |
|
| |
Most users will be served well by the default "table" setting ("main").
|
| |
|
| |
This adds a convenient per-peer option to set the routing table that associated routes are added to. This functionality is very useful for isolating interfaces from the kernel's global routing and forcing all traffic of a virtual interface (or a group of processes, via e.g. "ip rule add uidrange 10000-10009 lookup 42") through Wireguard.
|
| |
|
|
| |
use replace to make it succeed
|
| |
|
| |
* wireguard: allow not storing private keys in world-readable /nix/store
|
| |
|
|
| |
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
|
| | |
|
| |
|
|
|
|
|
| |
It was deprecated and removed from all modules in the tree by #18319.
The wireguard module PR (#17933) was still in the review at the time and
the deprecated usage managed to slip inside.
|
|
|
fixes #17933
|