public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: IPSec Roadwarrior Configuration
Date: Mon, 29 Jan 2018 12:50:04 -0500	[thread overview]
Message-ID: <884f8e86-30ee-47d6-0ca4-4ce32ca56b66@rymes.com> (raw)
In-Reply-To: <3b16015a-cbc5-83a0-2d07-cf78b858000f@rymes.com>

[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]

Regarding the issue with display of subnets on the index.cgi page, I 
think I have (in our case) narrowed it down to tunnels with multiple 
subents defined in a comma separated list.

A tunnel with remote subnet "10.7.0.0/24,10.7.1.0/24" displayed on 
index.cgi as "10.7.0.0/3". When changed to "10.7.0.0/23", it displays 
properly on index.cgi.

I suspect that the code to display the subnet pre-dates the change to 
allow multiple subnets in one tunnel and needs to be modified?

I have opened bug 11604 for this issue. 
https://bugzilla.ipfire.org/show_bug.cgi?id=11604

Tom

PS: My output below was wrong, the index.cgi page showed 10.253.0.0/3, 
not "10.6.0.0/3". I fixed that in the bug description.

On 01/29/2018 12:26 PM, Tom Rymes wrote:

>> Generally, it seems that quite some bugs are related to IPsec: For 
>> example,
>> even though a N2N connection is using /24 remote networks, it says it 
>> uses
>> a /3 (virtually _everything_) at the main WebUI page...
> 
> We have around 20 tunnels between IPFire hosts, and I had never noticed 
> that before, but I just went and looked, and sure as ****, it's there. 
> Perhaps this is the source of the bugs saying that an address is part of 
> an existing IPSec scope?
> 
> The index.cgi page shows:
> 
> "tunnelname    10.6.1.0/3    CONNECTED"
> 
> while the output of "ipsec status tunnelname" shows:
> 
> Routed Connections:
>        tunnelname{102}:  ROUTED, TUNNEL, reqid 17
>        tunnelname{102}:   10.254.0.0/23 === 10.253.1.0/24 10.253.2.0/24
> Security Associations (26 up, 0 connecting):
>        tunnelname[348]: ESTABLISHED 119 seconds ago, x.x.x.x[C=US, 
> ST=NH, O=MyOrg, OU=Engineering Dept., 
> CN=host1.myorg.dom]...y.y.y.y[C=US, ST=NH, O=MyOrg - tunnelname, 
> OU=Engineering, CN=host2.myorg.dom]
>        tunnelname{5022}:  INSTALLED, TUNNEL, reqid 17, ESP SPIs: 
> cdbada31_i c4e24e27_o, IPCOMP CPIs: 5431_i 6977_o
>        tunnelname{5022}:   10.254.0.0/23 === 10.253.1.0/24 10.253.2.0/24
>        tunnelname{5023}:  INSTALLED, TUNNEL, reqid 17, ESP SPIs: 
> cfdce8b8_i c1d1780e_o, IPCOMP CPIs: 6d81_i cbd4_o
>        tunnelname{5023}:   10.254.0.0/23 === 10.253.1.0/24 10.253.2.0/24


      reply	other threads:[~2018-01-29 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 20:33 Tom Rymes
2018-01-29 14:58 ` Peter Müller
2018-01-29 17:26   ` Tom Rymes
2018-01-29 17:50     ` Tom Rymes [this message]

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=884f8e86-30ee-47d6-0ca4-4ce32ca56b66@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