| Knowledge Base ID: | KB6699 |
| Version: | 4.0 |
| Published: | 07 Oct 2008 |
| Updated: | 07 Oct 2008 |
| Categories: |
Firewall/IPSec_VPN IPSec ScreenOS |
- XAuth client
- LAN to LAN VPN
- Untrust IP obtained via DHCP

|
Site |
A |
B |
|
Untrust IP of Firewall |
Dynamic IP |
172.16.20.1 |
|
Trust Network |
192.168.10.0/24 |
192.168.20.0/24 |
|
Local ID |
ns5xt.netscreen.com |
N/A |
|
Peer ID |
ns5xt.netscreen.com |
|
|
Preshared Key |
support |
support |
|
Phase 1 Proposal |
pre-g2-3des-sha |
pre-g2-3des-sha |
|
Phase 2 Proposal |
g2-esp-3des-sha |
g2-esp-3des-sha |
Building a VPN using a Juniper Firewall as an XAuth client requires you to create an XAuth user account on the remote gateway, or have the remote gateway look up a radius server, for purposes of authenticating the XAuth user during phase 1 IKE negotiation. In this example, we will create an XAuth user account on Juniper Firewall-B.
Configuration of Juniper Firewall-B:
Create the XAuth User on Juniper Firewall-B:
- Click Objects > Users > Local
- Click New
- User Name: XAuth
- Click XAuth User
- User Password:netscreen
- Confirm Password:netscreen
- Click OK
Phase 1 on Juniper Firewall-B:
- Click VPNs > AutoKey Advanced > Gateway
- Click New
- Gateway Name: XAuth GW
- Remote Gateway Type
- Click Dynamic IP Address
- Peer ID: ns5xt.netscreen.com
- Preshared Key: support
- Click Advanced
- Security Level: User Defined
- Phase 1 Proposal: pre-g2-3des-sha
- Mode (Initiator): Aggressive
- Click XAuth Server
- Click Return
- Click OK
Phase 2 on Juniper Firewall-B:
- Click VPNs > Auto Key IKE
- Click New
- VPN Name: XAuth VPN
- Remote Gateway
- Predefined
- XAuth GW
- Click Advanced
- Security Level: User Defined
- g2-esp-3des-sha
- Click Return
- Click OK
VPN Policy on Juniper Firewall-B;
- Click Policies
- Select From Trust to Untrust Zone and click New
- Source Address:
- Click New Address: 192.168.20.0 / 24
- Destination Address:
- Click New Address: 192.168.10.0 / 24
- Service: ANY
- Action: Tunnel
- Tunnel VPN: XAuth VPN
- Click Modify matching bidirectional VPN policy
- Click Position at Top
- Click OK
- Source Address:
Configuration of Juniper Firewall-A:
Phase 1 on Juniper Firewall-A:
- Click VPNs > AutoKey Advanced > Gateway
- Click New
- Gateway Name: XAuth GW B
- Remote Gateway Type:
- Click Static IP Address
- 172.16.20.1
- Preshared Key: support
- Local ID: ns5xt.netscreen.com
- Click Advanced
- Security Level: User Defined
- Phase 1 Proposal: pre-g2-3des-sha
- Mode (Initiator): Aggressive
- Click XAuth Client
- Username: XAuth
- Password: netscreen
- Click Return
- Click OK
Phase 2 on Juniper Firewall-A:
- Click VPNs > Auto Key IKE
- Click New
- VPN Name: XAuth VPN B
- Remote Gateway
- Predefined
- XAuth GW B
- Click Advanced
- Security Level: User Defined
- g2-esp-3des-sha
- Click Return
- Click OK
VPN Policy on Juniper Firewall-A:
- Click Policies
- Select From Trust to Untrust Zone and click New
- Source Address:
- Click New Address: 192.168.10.0 / 24
- Destination Address:
- Click New Address: 192.168.20.0 / 24
- Service: ANY
- Action: Tunnel
- Tunnel VPN: XAuth VPN B
- Click Modify matching bidirectional VPN policy
- Click Position at Top
- Click OK
- Source Address:
The VPN tunnel has to be initiated from Juniper Firewall-A, the XAuth client. Behind the scenes, Juniper Firewall-A will be challenged for an XAuth login/password, and Juniper Firewall-A will send the XAuth credentials as defined in Phase 1.
.