Narrowing & split tunnelling

What you asked for and what you got

Lesson 10 of 20 · 12 min · Module 3: Real networks

In IKEv2 a selector is a request. The other gateway may grant less than you asked for, and it does so without an error.

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…

  • Explain narrowing of traffic selectors
  • Tell a split tunnel from a full tunnel
  • Make the configuration state what is really installed

The idea

When the two selectors overlap but are not identical, IKEv2 narrows them to the part both sides allow. The tunnel comes up, and the installed selector is smaller than the configured one. A configuration that says "everything goes to the branch" can therefore be running as "only the branch network", and nothing in it tells the next administrator so.

# configured:  selector 10.0.1.0/24 0.0.0.0/0
# branch has:  selector 10.1.0.0/24 10.0.1.0/24
# installed:   10.0.1.0/24 <-> 10.1.0.0/24   (narrowed)

01Split tunnel and full tunnel

A split tunnel protects only the traffic between the two sites; everything else goes straight to the internet. A full tunnel sends all traffic from a site through the other one, with the remote network written as 0.0.0.0/0. Both are legitimate designs, but they are different decisions.

02Read what was installed

The Output tab of this lab marks a narrowed selector. On real devices, the SA shows the installed selectors, which may be smaller than the ones you typed. With IKEv1 there is no narrowing: selectors that differ simply fail.

03Keep the configuration honest

If the design is a split tunnel, write the split-tunnel selector. A configuration that relies on the peer to trim it works until the day the peer is replaced or reconfigured, and then all internet traffic of the site disappears into the tunnel.

Your turn

Someone configured this tunnel with the remote network 0.0.0.0/0, intending "the branch and everything behind it". The branch accepts only its own network, so the selector is silently narrowed. Make the configuration say what is actually protected: 10.0.1.0/24 to 10.1.0.0/24.

What the checks look for

  • The tunnel carries the traffic between the offices
  • The installed selector is the configured one, not a narrowed one
  • The configuration describes a split tunnel
  • Internet traffic stays outside the tunnel
Try it in the editor →

Take this with you

Configure the selector you mean. Narrowing can make a wrong configuration work, and hides the difference until something changes.

Go a little further

Think about what a full tunnel would need at the branch besides the selector: the branch would have to forward and translate the head office's internet traffic.

Learn VPN & IPsec Foundations for free

20 short lessons with real code and instant checks.

See the whole course →