L48
Client-to-site, site-to-site and split/full tunnels
Cram this first — memory hook
Client-to-site = one person enters; site-to-site = two offices connect. Split/full = which traffic uses the path.
Exam trap
Full tunnel is not the same term as Internet Protocol Security tunnel mode. One concerns traffic selection; the other packet encapsulation.
The slide facts
Client-to-site connects an individual remote device; site-to-site connects networks through gateways. The client diagram contrasts split and full tunneling.
If you have time — extra
A client-to-site Virtual Private Network lets one remote device connect to an organization's gateway. A site-to-site links networks, such as Cape Town and Johannesburg offices, through their gateways; ordinary users may not run a separate client for each cross-site connection. Full tunneling routes the configured general traffic through the organization's path, enabling centralized controls but increasing gateway/link load. Split tunneling sends only selected destinations through the while other traffic uses another path, such as the local internet connection. This can improve efficiency but needs deliberate security and routing policy. Neither label alone tells you that all devices are authorized or all Domain Name System behavior is correct. The split/full distinction is separate from transport/tunnel mode: they answer different questions.
Walkthrough
Identify whether the endpoint is a user device or network gateway, decide which destinations should use the , apply routes//access policy, and test both protected and intentionally unprotected paths.