I question the configuration of DHCP in what you have posted. In particular I believe there is a problem in your definition of the default router IP address. For DHCP clients their default router address should be a router interface in their subnet. Given what you have posted it would logically be 192.168.30.1 rather than 184.108.40.206.
As far as the static routes that you have listed:
- route 1 is the correct static default route.
- route 2 is a route to the router interface connected to the DSL modem. You do not need static routes to connected interfaces. delete this route.
- route 3 puzzles me. It starts off just like route 2 but the forwarding address is a surprise. Where and what is 192.168.10.1? delete this route.
- routes 4 and 5 also puzzle me. They seem to indicate that 192.168.10.0 and 192.168.11.0 are reached out the interface connected to the DSL modem. If that is the case then do not specify the outbound interface but specify the next hop address.
as you have default route on 1841 to DSL 220.127.116.11 no other routes are required. delete them except the default route, Also as suggest by other NP expert change the default router in DHCP to 1841's LAN side interface's IP address. I believe that NAT is performed on 1841
Again Remote site VPN addresses are covered under default route, no need to have separate routes for them.
I am puzzled - you say typo and then seem to repeat the same as the original post.
My point is that most clients of DHCP expect the default router to be an address in the local subnet. This way they can ARP for the address of the default router. If the DHCP client addresses are in 192.168.30.0 and the default router is 18.104.22.168 then most clients will have a problem. You comment that if you make the default router 192.168.30.1 there is no Internet connectivity. Are you saying that with the default router set to 22.214.171.124 that clients do have Internet connectivity?
You do want 126.96.36.199 as the next hop for the routers default route but it does not seem right to me for it to be the default for the clients.
Perhaps I do not understand what you are trying to describe in route 3 or 4 or 5. What I see is a description of a destination 188.8.131.52 with a next hop of 192.168.10.1 which makes no sense. The destination is in a locally connected subnet and the next hop is a remote address.
Destination Network Prefix: 184.108.40.206
Destination Network Mask: 255.255.255.255
Forwarding: 192.168.10.1 - Remote Site Local Address
From what I see I think that you do not need either route 3 or 4 or 5. Having a correct default route will get you to the remote addresses and you do not need special static routes for them.
If you are having problems in establishing a VPN I suspect that the problem is something other than your static routes.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...