I have an ipsec tunnel set up that connects to an AWS VPC subnet. The subnet has an instance running in it with the ip address 192.168.150.12. I eventually want to configure this instance to route traffic from our office to another AWS subnet, 172.22.0.0/24, but have not done that yet.
If I configure the tunnel from our office to only route traffic for 192.168.150.0/24, it works and I can connect to 192.168.150.12. If I add as a secondary remote network 172.22.0.0/24 to the ipsec tunnel config and restart it, I’m now unable to connect to 192.168.150.12 at all, using the same method (SSH). I’ve triple checked everything on the 192.168.150.12 instance to make sure the routes and firewall aren’t interfering, but really the only difference is the reconfiguration of the ipsec tunnel on the balance router with the secondary remote network.
For the record, this is a Peplink Balance 210, although I don’t know that that matters. Is there any reason I’m seeing this behaviour?