Project

General

Profile

Actions

Bug #1042

closed

CARP VIP Descriptions incorrect on IPsec/OpenVPN

Added by Jim Pingle about 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
VPN (Multiple Types)
Target version:
Start date:
11/24/2010
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

CARP VIPs in the list for use by IPsec and OpenVPN are shown with the interface name (e.g. VIP22) instead of the CARP VIP description.

Actions #1

Updated by Pierre POMES about 11 years ago

Jim P wrote:

CARP VIPs in the list for use by IPsec and OpenVPN are shown with the interface name (e.g. VIP22) instead of the CARP VIP description.

I guess you would like to have the same display as for firewall/nat rules ?
- for firewall nat rules, the display is "carpip (description)"
- actually for IPSec and OVPN, the display is "VIPxx (carpip)"

This difference is probably because for firewall/nat rules, IP is stored in config.xml, but for IPSec and OpenVPN, the interface is stored.

Pierre

Actions #2

Updated by Jim Pingle about 11 years ago

That may explain the difference in why it was coded that way but it's still not optimal for the user. I'd really prefer the firewall rule way "IP (descr)" for both IP alias and CARP VIPs.

Actions #3

Updated by Pierre POMES about 11 years ago

Yes, I agree.

And it would be probably better to store the ip rather than the inferface in config.xml. At least for OVPN, since it could be directly mapped to the "local" directive. However, this will break all running configurations... I do not know if is a good idea since RC1 is coming. What do you think ?

Actions #4

Updated by Chris Buechler about 11 years ago

It's not broken as is, let's not break it. Taking the VIPxx and getting the description is easy enough.

Actions #5

Updated by Pierre POMES almost 11 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Now VIP descriptions should look like in firewall/nat screens.

Actions #6

Updated by Ermal Luçi almost 11 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF