We have a Sonicwall 3600 with the LAN interface configured for 192.168.44.254. This firewall is managed by a third party and that is not going to change anytime soon. Have purchased a second Sonicwall (TZ400) to connect to a new fiber circuit. Intention is to move a group of users to the new Sonicwall which will also give us autonomy in managing what we need in a timely manner. There is one problem - we still need to access resources through a VPN which is configured on the 3600. The third party vendor will not configure a second site to site VPN for us. So this is what they are proposing:
- Configure the new Sonicwall LAN interface to 192.168.44.253 and connect it to existing 192.168.44.0 network. Change the default gateway of the computers to 44.253 and enter a static route to reach the VPN via the 44.254 address. Sounds fine in theory, not sure it's the best way to tackle this problem however.
The problem is when we connect the new Sonicwall to the 44.0 network, all traffic routes through the 3600 via 192.168.44.254. We removed the static route and uplink cable and everything returns to normal routing through 44.253 and out the proper WAN connection.
1)Is it possible that the two Dell PowerConnect switches we are using are providing dynamic routing through 44.254 even though the gateway of the computers are set to 44.253. These are just layer 2 switches.
2)Is there another configuration that would be more preferable?