Bug 12075 - assigning static IP address pools for OpenVPN fails: already in use for an IPsec connection
Summary: assigning static IP address pools for OpenVPN fails: already in use for an IP...
Status: CLOSED DUPLICATE of bug 11235
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: all All
: Will affect an average number of users Minor Usability
Assignee: Erik Kapfer
QA Contact: Peter Müller
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-11 09:45 UTC by Peter Müller
Modified: 2019-06-16 16:37 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Müller 2019-05-11 09:45:11 UTC 
The OpenVPN GUI seems to do wrong IP/CIDR calculations when trying to add a new static IP address pool. It always reports a given subnet is already in use by an IPsec N2N connection - however, it is not.

Steps to reproduce:
(a) Set up an IPsec N2N connection with arbitrary remote/local networks (used 10.XXX.XXX.0/24 for both).
(b) Activate the connection.
(c) Add a new OpenVPN static IP address pool with an arbitrary subnet (used 10.XXX.XXX.0/24, with an IP address range not covered by mentioned IPsec connection).

Step (c) fails, no matter which IP address range I choose (it even fails with 192.168.XXX.XXX). It seems like this GUI is miscalculating IP/CIDR stuff.

CIDR notation or /255.255.255.0 does not matter.
Comment 1 Peter Müller 2019-05-11 10:22:45 UTC 
Bug #11823 sounds quite similar...
Comment 2 Peter Müller 2019-06-16 16:37:20 UTC 
I think this is because of IPsec subnet calculation gone wrong.

*** This bug has been marked as a duplicate of bug 11235 ***