New Vlan's not routing through Sonicwall VPN
Posted on 2011-03-02
The network that I have of 275+ computers and other network equipment was orginally programed by my predecessor on Vlan 1 with a /23. Due to security concerns recently, I have been requested to create vlan's. Internally through out my 26 switches and routers the new vlan's that i have created are routing and communicating perfectly. The problem I have is anyone (especially administrators) connecting to our Sonicwall 4500 through the VPN client, it does not route through the VPN tunnel.
In attempting to find the issue, the remote clients traceroute the path and it appears to route on the ISP's network. I would post the traceroutes if you think you want them, but all of them black hole some where on the ISP network. The only possibility that i can find is that the Sonicwall is not allowing those subnets through. I did create route statements for the subnets to point to my L3 switch that is being used as my default gateway and I am striking out.
Now to start with I want to use a class A (10.x.x.x) private subnet to use and carve out of that a /20 so that I can have room for future growth. I have thought about the class B private subnets as an added option.