?
Solved

Sonicwall firewall question

Posted on 2011-02-18
12
Medium Priority
?
497 Views
Last Modified: 2012-05-11
Setup:

Site A: 192.168.200.0
Sonicwall Pro 2040 with a site to site VPN to site B (only the 192.168.175.0 network connected)

Site B: 192.168.175.0
Sonicwall NSA 240 (192.168.175.253).  This Sonicwall is only used to scan traffic, all routing is done from a Cisco router (192.168.175.1) sitting behind it.  The router is used to connect to remote branches on different subnets.  I want to make it so that I am able to see those remote subnets from site A: through site B: (ie 192.168.123.0)

I created a route in the site A sonicwall that says 192.168.123.0 traffic point to 192.168.175.1 (its pingable) WAN zone.  I still can't see it.  If I add to connectable networks in the VPN setup, the VPN never establishes.

How can I make 192.168.123.0 reachable?

Hmm... come to think of it, perhaps I need to contact the cisco guy and ask him to add a route that says all traffic from 192.168.200.0 pass to the NSA 240?
0
Comment
Question by:GDavis193
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 3
12 Comments
 
LVL 3

Expert Comment

by:Rick_at_ptscinti
ID: 34928453
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.
0
 

Author Comment

by:GDavis193
ID: 34928486
"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.

0
 
LVL 3

Expert Comment

by:Rick_at_ptscinti
ID: 34930188
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.
0
Four New Appliances. Same Industry-leading Speeds.

But don't take it from us.  The Firebox M370 is Miercom tested and Miercom approved, outperforming its competitors for stateless and stateful traffic throughput scenarios.  Learn more about the M370, M470, M570 and M670 and find the right solution for your organization today!

 

Author Comment

by:GDavis193
ID: 34930389
So you're saying this is an access rule and not a route?
0
 
LVL 33

Expert Comment

by:digitap
ID: 34934865
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.
0
 
LVL 3

Accepted Solution

by:
Rick_at_ptscinti earned 1500 total points
ID: 34935281
"So you're saying this is an access rule and not a route?"

Yes,  You can define routes when doing VPN with SonicWall routers but typically you don't need to.  The router know the route because it is part of the access rule used to establish the VPN tunnel.  It's kind of the same concept as locally connected networks.  You don't have to define routes because the router know about them inherently and therefore route statements aren't needed.  Route statements are only needed for networks that the router is not aware of.
0
 

Author Comment

by:GDavis193
ID: 34935333
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.
0
 
LVL 33

Expert Comment

by:digitap
ID: 34935402
yup...that's it.  thanks for clarifying the question for me and glad it's working!
0
 
LVL 33

Expert Comment

by:digitap
ID: 34935408
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.
0
 

Author Comment

by:GDavis193
ID: 34935746
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.
0
 
LVL 33

Expert Comment

by:digitap
ID: 34935748
@GDavis :: thanks for the extra info...glad it's working!
0
 

Author Closing Comment

by:GDavis193
ID: 35065923
not 100% right on but pointing in the correct direction./
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

During and after that shift to cloud, one area that still poses a struggle for many organizations is what to do with their department file shares.
This article explains the fundamentals of industrial networking which ultimately is the backbone network which is providing communications for process devices like robots and other not so interesting stuff.
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Course of the Month10 days, 10 hours left to enroll

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question