Related Documentation
- J Series
- Understanding Route-Based IPsec VPNs in the Junos OS Security Configuration Guide

- SRX Series
- Understanding Route-Based IPsec VPNs in the Junos OS Security Configuration Guide

- User Logical System Configuration Overview
- Example: Configuring IKE and IPsec SAs for a VPN Tunnel
- Example: Configuring a Route-Based VPN Tunnel in a User Logical System
Understanding Route-Based VPN Tunnels in Logical Systems
A VPN connection can secure traffic that passes between a logical system and a remote site across a WAN. With route-based VPNs, you configure one or more security policies in a logical system to regulate the traffic flowing through a single IP Security (IPsec) tunnel. For each IPsec tunnel, there is one set of IKE and IPsec security associations (SAs) that must be configured at the root level by the master administrator.
![]() | Note: Only route-based VPNs are supported for logical systems. Policy-based VPNs are not supported. |
In addition to configuring IKE and IPsec SAs for each VPN, the master administrator must also assign a secure tunnel (st0) interface to a user logical system. An st0 interface can only be assigned to a single user logical system. However, multiple user logical systems can each be assigned their own st0 interface.
![]() | Note: The st0 unit 0 interface should not be assigned to a logical system, as an SA cannot be set up for this interface. |
The user logical system administrator can configure the IP address and other attributes of the st0 interface assigned to the user logical system. The user logical system administrator cannot delete an st0 interface assigned to their user logical system.
For route-based VPNs, a security policy refers to a destination address and not a specific VPN tunnel. For cleartext traffic in a user logical system to be sent to the VPN tunnel for encapsulation, the user logical system administrator must make the following configurations:
- Security policy that permits traffic to a specified destination.
- Static route to the destination with the st0 interface as the next hop.
When Junos OS looks up routes in the user logical system to find the interface to use to send traffic to the destination address, it finds a static route through the st0 interface. Traffic is routed to the VPN tunnel as long as the security policy action is permit.
The master logical system and a user logical system can share a route-based VPN tunnel. An st0 interface assigned to a user logical system can also be used by the master logical system. For the master logical system, the master administrator configures a security policy that permits traffic to the remote destination and a static route to the remote destination with the st0 interface as the next hop.
VPN monitoring is configured by the master administrator in the master logical system. For the VPN monitor source interface, the master administrator must specify the st0 interface; a physical interface for a user logical system cannot be specified.
Related Documentation
- J Series
- Understanding Route-Based IPsec VPNs in the Junos OS Security Configuration Guide

- SRX Series
- Understanding Route-Based IPsec VPNs in the Junos OS Security Configuration Guide

- User Logical System Configuration Overview
- Example: Configuring IKE and IPsec SAs for a VPN Tunnel
- Example: Configuring a Route-Based VPN Tunnel in a User Logical System


