Avatar of dougp23
Flag for United States of America asked on

Sonicwall Config and CIsco 3560

So here's the network:

Lots of local users, 192.168.12.x.  Users are given an IP thru DHCP, and their default GW is  The 254 addy is a Cisco 3560G switch.  In the configs of the 3560, we have a line that says

ip route

The 253 is our Cisco ASA 5505.

Now I have setup a Sonicwall to replace the ASA, and am just doing some testing.  I assigned an internal IP to the Sonicwall of  If I set up PCs with a def gw of 12.252, everything is fine, they can surf and all that.  If I reconfigure the Cisco 3560G to say

ip route

No one can go anywhere.

What excatly am I missing here??
NetworkingHardware Firewalls

Avatar of undefined
Last Comment

8/22/2022 - Mon

When you get that issue, are the PCs set with that default GW? Also, how many VLANs are on your network? Also, did you make sure to update the default GW programmed into the switch itself?

The PCs are using the IP of the 3560G as their def gw.
Four VLANs on the net, the ASA and Sonicwall are both configured to reside in the 12 subnet.
I will have to check on the def gw on the switch.  That might be it!

Go ahead and double check, then just let us know!
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy

If you are settings the PC's to a default gateway of 12.252 then you are using PC's on the same vlan as the sonicwall right?

Have you created routes for the other vlans on your network on the sonicwall to point back to the 3560G switch?

Hmm, the only info I see on the 3560 is

Ip address

So it appears that there is no def gw for the switch?  Probably that iproute statement takes it from there.

Yes, both the SW and ASA are on the same VLAN as the PCs.  
I suppose I could just change DHCP to hand out the SW as the def gw, but can't figure out why it works with the ASA and not the SW.  Both are NATing, etc.

The other VLANs are for phones so no real need to set any routes in the SW for them.

Do you have a route on the sonicwall directing routing requests from the 192.168.12.x network to the core switch?

On the sonicwall create a static route.  

Source = Any
Destination = (Assuming this is your internal network)
Service = Any
TOS/Mask = Any
Gateway = (Your core switch IP address)
Interface = x0
Metric= 1
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.


it is starting to look like you are right.  I have a "pro" coming in this AM to solve the issue, but I *do* see routes on the ASA like this

route inside 1
route inside 1
route inside 1

So, I guess I am "network stupid".  Why would I assign my PCs with a def gw of, and when they hit that and want to go somewhere, we push them to the 3560G which then pushes them ASA, which pushes them BACK to the 3560G???
And I *REALLY* thought the statement

ip route

was TOTALLY INCLUSIVE (i.e. I don't care where your from or where you're going, you're going to

If I could understand this, it would be great, lol!
I will award you the points if my "pro" says that is the issue, but in comparing the configs, I do see all those routes in the ASA.

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

I guess I need to re-take Routing 101....
Pretty embarassing

That wasn't my intent and we all tend to overlook things at times. it's a forest, trees scenario so don't beat yourself up. It's why Experts Exchange is here, to provide help for  everyday IT.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.

I am fine with it, and thanks so much for the help.
Sonic wall support was totally useless.