Project

General

Profile

Actions

Bug #8533

closed

OpenVPN with 2 site to site tunnels adds routes to first OpenVPN interface only

Added by Jonathan Trott almost 6 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
05/22/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.6
Affected Architecture:
i386

Description

We had setup a single OpenVPN site to site connection to a remote Sophos XG firewall with no issues. pfSense being the client in the connection.
When we added a second OpenVPN site to site tunnel to a second Sophos XG firewall in a different location with a different remote subnet, the route for the second connection remote subnet was added to the OpenVPN interface of the first connection (ovpnc3 instead of ovpnc4).
We could see the incorrect route in the routing table and verified it with packet captures.
Restarting the OpenVPN service didn't fix the issue.
We had to revert to using IPSEC for the second tunnel.

Actions #1

Updated by Jim Pingle almost 6 years ago

  • Status changed from New to Rejected

Highly unlikely there is a bug here, it's most likely a configuration issue. Please post on the forum (when it comes back online) or the pfSense subreddit.

Also, 2.2.6 is very, very old. Bug reports are only valid against the current supported version (2.3.4-p1 at this time)

Actions #2

Updated by Jonathan Trott almost 6 years ago

My apologies, the update information on the firewall was telling me I was already on the latest version, will investigate how to upgrade to the latest version and retest.

Actions

Also available in: Atom PDF