At this time it's not possible to disable a peer, you can only disable individual tunnels.
Sometimes there are way too many tunnels (in the case that prompted me to write this, there is over a dozen of them).
Even if there are just a few, going through all of them is not exactly handy either.
Description
Description
Details
Details
- Version
- -
- Is it a breaking change?
- Unspecified (possibly destroys the router)
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | sarthurdev | T2816 Rewrite IPsec scripts with the new XML/Python approach | |||
Resolved | ENHANCEMENT | sarthurdev | T57 Make it possible to disable the entire IPsec peer |
Event Timeline
Comment Actions
+1
During restructuring my IPsec HUB/SPOKES I would have liked this possibility, too.
Maybe it's super trivial, if peer x.x.x.x { disabled } node exists, just skip the generation of this config file entry.