When configuring a Site-to-Site VPN tunnel in SonicOS Enhanced firmware using Main Mode both the SonicWall appliances and Cisco ASA firewall (Site A and Site B) must have a routable Static WAN IP address.
Network Setup
Site A | Site B |
SonicWall | Cisco ASA |
WAN IP: 116.6.209.250 LAN Subnet: 10.9.0.0/16 | WAN IP: 121.12.156.162 LAN Subnet: 192.168.0.0/16 |
Deployment Steps
Creating Address Objects for VPN subnets
Configuring a VPN policy on Site A SonicWall
Configuring a VPN policy on Site B Cisco ASA
ip address 121.12.156.162 255.255.255.248
ip address 192.168.1.254 255.255.255.0
access-list HBMTDG-VPN extended permit ip 192.168.0.0 255.255.0.0 10.9.0.0
nat (inside) 0 access-list HBMTDG-VPN
nat (inside) 1 192.168.1.0 255.255.255.0
crypto ipsec transform-set hbmtvpn esp-des esp-md5-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto map HBMTJM 20 match address HBMTDG-VPN
crypto map HBMTJM 20 set peer 116.6.209.250
crypto map HBMTJM 20 set transform-set hbmtvpn
crypto map HBMTJM 20 set security-association lifetime seconds 28800
crypto map HBMTJM 20 set security-association lifetime kilobytes 4608000
crypto map HBMTJM interface outside
crypto isakmp identity address
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption des
hash md5
group 2
lifetime 28800
telnet timeout 5
ssh timeout 5
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
tunnel-group 116.6.209.250 type ipsec-l2l
tunnel-group 116.6.209.250 ipsec-attributes
pre-shared-key *
How to test this scenario