T5329 : priority: tunnel config is committed before wireguard #2063
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
Having a wireguard interface as the source interface on a GRE tunnel causes a configuration error on boot. Wireguard is not yet exists in the system when tun is already exists due to priority, that's why error is received
Types of changes
Related Task(s)
Component(s) name
wireguard
Proposed changes
How to test
Configuration:
set interfaces tunnel tun0 address '10.68.1.17/30'
set interfaces tunnel tun0 encapsulation 'gre'
set interfaces tunnel tun0 remote '10.68.0.2'
set interfaces tunnel tun0 source-address '10.68.0.9'
set interfaces tunnel tun0 source-interface 'wg0'
set interfaces wireguard wg0 address '20.68.0.9/30'
set interfaces wireguard wg0 peer FR address '192.168.11.1'
set interfaces wireguard wg0 peer FR allowed-ips '0.0.0.0/0'
set interfaces wireguard wg0 peer FR port '51820'
set interfaces wireguard wg0 peer FR public-key 'gbse3gHYt90wDXoGCUClbwKf3DWFVPpSNEebI8RkIhg='
set interfaces wireguard wg0 private-key 'enfaVowlSURdQqvRDNjFrztz1+cUTlQXHQSDTl9OGDs='
Checklist: