From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rymes To: development@lists.ipfire.org Subject: Core 122: Odd issue with many IPSec Subnets defined Date: Fri, 10 Aug 2018 11:19:19 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8131838908881968732==" List-Id: --===============8131838908881968732== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit I posted this up on the forum, but should probably post it up here. We have one tunnel on a machine upgraded to Core 122, and it has five individual hosts defined in the "Local Subnet" field: 192.169.1.2/32,192.168.1.3/32,192.168.1.4/32,192.168.1.5/32,192.168.1.6/32 This was working fine on Core 120, but now it will not work unless I define just the one host. I know that there were a few fixes related to multiple subnets and IPSec, so I thought I would ask here if maybe this change is related to those fixes. Is there a limit to how many subnets can be defined for a given tunnel? Tom --===============8131838908881968732==--