Project

General

Profile

Actions

Bug #3595

closed

OpenVPN TAP/TUN <--> interface bridge not working after reeboot

Added by Marcin Nowak about 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
04/10/2014
Due date:
% Done:

0%

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

Description

After building Tap OpenVPN tunnel with bridged interfaces between 2 sites with pfsense 2.1.1
That looks like :

<   pfsense siteA >         internet          <  pfsense siteB   >
siteA interdaceA < (lan<>ovpntap)> <------Openvpn tunel ------><(opvpntap<>lan ) > interfaceB siteB
< Bridge siteA > < Bridge site B >

problem is timing

for example...
if i reboot siteA pfsense instance , after restart bridged interfaces are not bridged, at least it looks so, but in settings every thing looks ok.
Then i need to go to in GUI Interfaces >(Assign)>Bridges>select my bridge and click edit icon and then save button without changing any value)

I confirmed timing issue by checking ifconfig after reboot. It shows that on bridge0 is only one member that is interface of NIC and I miss ovpnc1 interface
and manualy adding ovpnc1 interface and turning it on helps

commands used to manualy fix after reboot:
------------------------------------------------------------------------
ifconfig bridge0 addm ovpnc1
ifconfig ovpnc1 up
----------------------------------------------------------------------

Actions #1

Updated by Christian Baerike about 10 years ago

Issue confirmed: OpenVPN tap connection is initiated successfully, but no traffic passes through.

Affected versions: 2.1.1, 2.1.2
In both cases, this was an auto-upgrade from 2.1 Release.

Current workaround: manually bridge the VPN and LAN interfaces after a reboot, or add a startup script as suggested by Marcin.

Actions #2

Updated by Ermal Luçi about 10 years ago

  • Status changed from New to Feedback

This has been solved on latest 2.1 cod ein github.
If you gitsync it will solve the issues.

It will be discussed if an errata release will be done moving forward.

Actions #3

Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF