Project

General

Profile

Actions

Bug #6057

closed

OpenVPN only working after restarting the service after the upgrade to RC

Added by Pol Bettinger over 9 years ago. Updated about 9 years ago.

Status:
Not a Bug
Priority:
Normal
Category:
OpenVPN
Target version:
-
Start date:
04/01/2016
Due date:
% Done:

0%

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

Description

OpenVPN only working after restarting the service after the upgrade to RC


Files

OpenVPN_log_client.txt (5.8 KB) OpenVPN_log_client.txt Client Log Pol Bettinger, 04/01/2016 02:51 PM
OpenVPN_log_Server_pfsense.txt (5.06 KB) OpenVPN_log_Server_pfsense.txt Server PfSense Log Pol Bettinger, 04/01/2016 02:51 PM
Actions #1

Updated by Chris Buechler over 9 years ago

  • Category changed from VPN (Multiple Types) to OpenVPN
  • Status changed from New to Feedback

Client or server? What type of OpenVPN config? What was in the OpenVPN logs post-boot?

Actions #2

Updated by Pol Bettinger over 9 years ago

Server

Server Mode: Peer2Peer (SSL/TLS)
Protocol UDP

Actions #3

Updated by Chris Buechler over 9 years ago

this is the issue:

WARNING: Bad encapsulated packet length from peer (5635), which must be > 0 and <= 1574 -- please ensure that --tun-mtu or --link-mtu is equal on both peers -- this condition could also indicate a possible active attack on the TCP link -- [Attempting restart...]

which is probably config-related if you search on that. Wouldn't have changed from upgrading unless it's related to a change in behavior between OpenVPN versions. Is it reproducible?

Actions #4

Updated by Jim Thompson about 9 years ago

  • Assignee set to Chris Buechler
Actions #5

Updated by Chris Buechler about 9 years ago

  • Status changed from Feedback to Not a Bug
  • Affected Version deleted (2.3)

no other reports of same, it's likely along the lines of any number of other reports of same issue with OpenVPN itself, which all seem to come down to a config problem.

Actions

Also available in: Atom PDF