Project

General

Profile

Actions
Copy link

Bug #6664

closed

It's impossible to use HE.NET tunnel iface as a parent for OpenVPN instances

Added by Dmitriy K over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
OpenVPN
Target version:
2.4.0
Start date:
07/30/2016
Due date:
% Done:

0%

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

Description

Setup:
  • HE.NET tunnel iface [for example, WAN_HE]
Steps to reproduce:
  • Create an IPv6 OpenVPN instance on parent iface WAN_HE [for example, OVPN_AMS]
  • Go to dashboard. OVPN_AMS is down.
Expected:
  • OVPN_AMS is up
Actual:
  • "Status -> System Logs -> OpenVPN" has a string "Options error: --local and --nobind don't make sense when used together"
Workaround:
  • Edit /var/etc/openvpn/client?.ovpn file by removing nobind option
  • Restart openvpn service
Actions
Copy link
 #1

Updated by Dmitriy K over 7 years ago

Yet another workaround: Specify a local port instead of empty/0. Looks like $iface_ip is not properly initialized when he.net iface is chosen.

Actions
Copy link
 #2

Updated by Jim Pingle over 7 years ago

  • Target version changed from 2.3.2-p1 to 2.4.0
Actions
Copy link
 #3

Updated by Jim Pingle about 7 years ago

  • Status changed from New to Resolved
  • Assignee set to Jim Pingle
Actions
Copy link

Also available in: Atom PDF