Change requests
Add a network to a working tunnel
Lesson 18 of 20 · 11 min · Module 6: Put it together
A tunnel that carries a company's traffic is changed in small steps, during working hours, by someone who did not build it.
Start this lesson →Free. No installation: you write and run the code in your browser, and it is checked automatically.
By the end, you’ll be able to…
- Make a single, minimal change to a working tunnel
- Coordinate a selector change with the other side
- Verify old and new traffic after the change
The idea
A safe change adds one thing and leaves the rest alone. For a new network that means one more selector, agreed with the other side, and a check afterwards that the existing traffic still passes and the tunnel is still stable.
selector 10.0.1.0/24 10.1.0.0/24 # existing, untouched
selector 10.0.7.0/24 10.1.0.0/24 # the change
01Read before you write
Look at what the tunnel does today: its proposals, lifetimes, PFS and DPD. None of them is part of this change, so none of them should look different afterwards.
02Both sides, same moment
A selector that exists on one gateway only is refused. Agree the change with the other administrator and apply both halves in the same window, then test from both networks.
03Verify like a change
Three things must hold: the new network reaches the branch, the existing network still does, and the tunnel is still stable over a rekey. The checks in this lesson test all three.
Your turn
What the checks look for
- The finance network reaches the branch, in both directions
- The existing network still reaches the branch
- Two selectors are installed exactly as configured
- Nothing else was changed
Take this with you
Change one thing, on both sides, and verify the old traffic as carefully as the new.
Go a little further
Summarise the two local networks into one wider selector and run the lab, then decide whether you would ever put that into a change request.