Howdy!
I've done about the stupidest of things....
I've got a customer who has an internal IP scheme of 192.168.168.0/24. He's got a new private WAN going into place where remote locations are subnetted with 192.168.101.0/24 through 192.168.199.0/24. The default route to these other subnets is a Cisco 1700 at
192.168.1.1/24.So setting up the simplest thing for testing purposes for the first remote site, I set up a route in the Sonicwall that directs all traffic destined to the range of 192.168.101.0 through 192.168.199.255 to the Cisco at 192.168.1.1.
So the problem is that the Sonicwall no longer answers at it's LAN IP address of 192.168.168.1. From what I gather (from the route I added), it seems like the Sonicwall is faithfully redirecting the traffic destined for it's LAN interface (and as such, the web GUI) to the Cisco router, which is not forwarding it anywhere yet.
The Sonicwall does not have serial interface. I thought of putting a rule into the Cisco to route the traffic back to the Sonicwall, but that would cause a routing loop and not make the Sonicwall any more likely to answer.
What are my options for recovery? Everything else on the Sonicwall is working without issue.