Sonicwall firewall question

You will need to have 192.168.123 defined on your IPsec selectors for phase 2 on both ends.  Route statements won't be required on the VPN termination points. The Cisco or anything else downstream will definitely need a route statement.

"You will need to have 192.168.123 defined on your IPsec selectors for phase 2 on both ends"

? I don't follow.  Phase 2 only has settings for Protocol, encryption, and authentication for ipsec.

This is why I have GUI based firewalls.....

So, phase 2 of IPsec includes the negotiation of what networks will be allowed to pass across the tunnel.  If the two ends don't have a match setting of network rules then the tunnel will fail to establish.  This is an IPSec thing and doesn't matter brand, make or model.

On a Sonicwall you typically to go Networks--Zones and create a zone for the VPN connection.  You then have to go to Firewall--Access Rules and set the allow/deny conditions for that zone.  This is were you will need to define the 192.168.123 range.

I am not nearly as familiar with Sonicwall as I am with Cisco and Adtran, but ipsec conditions are standards based and always the same.

So you're saying this is an access rule and not a route?

i'm having a hard time picturing your network config.  what i think i'm seeing is your have your sonicwall as the firewall with a public IP on the WAN interface.  then, you have a cisco with a LAN interface on the same network as your sonicwall LAN interface.  the cisco is routing intranet traffic to remote sites, right?  what's establishing the VPN, the cisco or the sonicwall?  i think if i understood this, the answer would be more clear.

digittap - We have a cisco router actiing as the 'core' router.  It''s responsible for routing all traffic between the main and remote branches  (MPLS cloud).  It takes any data destined for the internet and passes through the Sonicwall (firewall).  We have a Pro2040 at our office (we are the IT support staff) and have a site to site VPN to the main office.  I am able to see the main office's local network but not the networks the cisco router knows about (the remote sites).  There is a route to pass all traffic going to 192.168.200.x (our local network - IT staff) to the sonicwall.

I figured it out.  If this is what Rick was saying - I apologize because I did not get this from his posts.

I had to create an access group and add all of the remote network (address object) to this group along with the X0 (local lan interface).  Then, when modifying the VPN connection from the NSA 240 - I changed the 'local network object from X0 (LAN) to this new new group.  I then modified the Pro2040 VPN connection (its running standard OS) to include the destination networks of the remote offices.

Works perfectly.

yup...that's it.  thanks for clarifying the question for me and glad it's working!

one more thing, you'll want to add routes to the sonicwall for the networks that the cisco knows about that the sonicwall does not.  using the cisco as the gateway for those MPLS networks.

digitap - I had site to site VPN's to these remote sites before so they were part of the VPN group.  What I did was just simply change to them to the LAN group and added them to an access group called <company name local subnet> along with X0 and then added that to the VPN tunnel as the primary local network.  I didn't have to add any routes.  The cisco router was already configured to pass all (my company) traffic to the sonicwall so it's all working.

@GDavis :: thanks for the extra info...glad it's working!

not 100% right on but pointing in the correct direction./