Project

General

Profile

Actions
Copy link

Bug #15917

closed

In OpenVPN export package, the option Automagic Multi-WAN IPs (port forward targets) does not working as expected

Added by aleksei prokofiev about 1 month ago. Updated 18 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
OpenVPN Client Export
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
24.11
Affected Architecture:

Description

When use Multi WAN setup with OpenVPN server and port forward with localhost, and export config with select option Automagic Multi-WAN IPs (port forward targets), in the client config there is no remote IP att all.
Doc say
Automagic Multi-WAN IPs (port forward targets):
Adds a remote statement for each port forward found targeting the interface binding and port used by this VPN, uses the IP address of each WAN as-is.

Actions
Copy link
 #1

Updated by Kris Phillips about 1 month ago

  • Status changed from New to Incomplete

I tested this and am unable to recreate this problem on 25.03. Please provide specific steps to reproduce.

Actions
Copy link
 #2

Updated by Danilo Zrenjanin 24 days ago

  • Status changed from Incomplete to Confirmed

I can duplicate that behavior.

Tested against 24.11

Steps to reproduce.

  1. Define the OpenVPN server on a system with two WAN connections.
  2. During the OpenVPN server setup select localhost as Interface
  3. Define two port forwarding rules for both WAN IPs and OpenVPN ports to the localhost.
  4. Navigate to the OpenVPN/Client Export Utility and select Automagic Multi-WAN IPs (port forward targets) and export the client config file.
  5. The client config file won't contain the remote directives for the two public IPs that contain port-forwarding rules.
Actions
Copy link
 #3

Updated by Jim Pingle 18 days ago

  • Status changed from Confirmed to Rejected

I can't reproduce this here. The exported configuration correctly ends up with two remote lines, one for each WAN.

Usually when this happens something doesn't match, like the destination address, protocol, or port on the port forward entries, or something isn't properly defined or compatible in the OpenVPN config, like using the wrong protocol in the VPN (e.g. one that sets "multihome") or the WANs having private IP addresses.

Actions
Copy link

Also available in: Atom PDF