Skip to content

Allow re-resolve script to work with systemd netdev #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jisakiel
Copy link

Trivial changes that enable parsing the slightly modified systemd netdev format, as documented on https://www.freedesktop.org/software/systemd/man/systemd.netdev.html

Tested in my box against /etc/systemd/network/wg0.netdev with bash -x

Trivial changes that enable parsing the slightly modified systemd netdev format, as documented on https://www.freedesktop.org/software/systemd/man/systemd.netdev.html
@zx2c4-bot zx2c4-bot force-pushed the master branch 6 times, most recently from d171082 to 26683f6 Compare August 6, 2020 15:49
@zx2c4-bot zx2c4-bot force-pushed the master branch 9 times, most recently from 542b7c0 to 4ad6d0d Compare June 25, 2021 20:54
@zx2c4-bot zx2c4-bot force-pushed the master branch 3 times, most recently from c39c2ea to ab264f7 Compare July 13, 2021 10:26
iTrooz added a commit to iTrooz/wireguard-tools that referenced this pull request Apr 6, 2025
…k for routing

rationale: Using an Endpoint that is part of a network in AllowedIPs
(e.g. Endpoint=162.12.13.1 and AllowedIPs=162.12.13.0/24) will cause a
looping route when enabling a wireguard connection, because of the
routes created by AllowedIPs values. This could be solved using the
more advanced fwmark-based routing (that you describe as "Improved
Rule-based Routing"), but it only takes effect when AllowedIPs contains
0.0.0.0/0. This patch allow users to override that behaviour in a
simply way.

This patch does not fix the root problem, which could be addressed in
one of the following ways:
- Finding Endpoints that are part of networks present in AllowedIPs,
and only enabling fwmark routing for them
- Always use fwmark routing, even if we don't need it
I do not have enough knowledge to choose which option to implement
(although I prefer WireGuard#2 because of implementation simplicity). I would
like to submit another patch for this, but I will need guidance on what
option to choose.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant