I know that there were a handful of IPSec related changes for core 122, specifically with regard to multiple defined subnets. I am having issues with one of my tunnels, and was hoping to find if the issue is on my end or if there is a problem with the newly introduced changes. I have one tunnel that specifies the local subnet as:
Code: Select all
The far side reports that, after the 122 upgrade, they cannot reach 192.168.1.4. They can reach the other hosts, and they can reach .4 if I remove the other hosts from the configuration.
IPSec status reports nothing amiss, and I’m wondering where I can look to find the problem. I’m guessing that it might lie with IPTables, but that nothing is hitting the log.
Any help pinpointing this would be appreciated.