From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Core 122: Odd issue with many IPSec Subnets defined
Date: Fri, 10 Aug 2018 11:19:19 -0400 [thread overview]
Message-ID: <e27dcbc4-897b-119e-96bf-9440bd75f1b9@rymes.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
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
reply other threads:[~2018-08-10 15:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e27dcbc4-897b-119e-96bf-9440bd75f1b9@rymes.com \
--to=trymes@rymes.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox