Layer 2 support is include in 8.0.1 beta 2!
You can enable Layer 2 by clicking the “?” icon on the right hand side of “PepVPN Settings”.
[image]
Some quick guides:
Layer 2 is supported in non-VRF and VRF.
If FusionHub has both LAN and WAN interfaces, LAN interface will be bridged to the non-VRF domain. If you don’t want LAN interface included in the bridge, define Layer 2 in VRF.
If FusionHub only has WAN interface, WAN interface is not bridged.

Baseline:
Remote access using L2TP with IPsec.
Two are leaves in a hub, one with “send all traffic to the hub” on, the other being off. The third is a stand-alone (no SpeedFusion connections)
They function just fine (mostly - see below).
The connections used to be somewhat unstable, but with 8.0.1b2 the L2TP connection stability has improved significantly.

OpenVPN Connect client fails:
Change the remote access server from L2TP to OpenVPN.
Download the “route_all_traffic” profile
MacOS client/Tunnelblick:
The connection is established and works well

MacOS client/OpenVPN Connect v 2.1.3.110:
The connection does not get established. Times out and dies.

iOS OpenVPN Connect client: The connection does not get established.

Sanity check:
Enabled OpenVPN on a Balance One FW 8.0.0 with a SpeedFusion connection.
MacOS client/Tunnelblick:
The connection is established and works well

OpenVPN clients (iOS and MacOS):
The connection does not get established.

OpenVPN Connect clients on iOS and MacOS do connect to other OpenVPN servers.

Baseline:
Remote access using L2TP with IPsec.
Two are leaves in a hub, one with “send all traffic to the hub” on, the other being off. The third is a stand-alone (no SpeedFusion connections)
They function just fine (mostly - see below).
The connections used to be somewhat unstable, but with 8.0.1b2 the L2TP connection stability has improved significantly.

OpenVPN fails - #1 - SpeedFusion-connected FusionHubs:
Change the remote access server from L2TP to OpenVPN.
Download the “route_all_traffic” profile
MacOS clients (OpenVPN and Tunnelblick):
The connection seems to be established but there is no traffic passed through. At first blush it seems to stop at the DNS lookup stage (no response from the DNS server).

iOS OpenVPN Connect client: Simply does not establish the connection.

OpenVPN fails - #2 - stand-alone FusionHub:
MacOS client/Tunnelblick:
The connection is established and works well

MacOS client/OpenVPN Connect v 2.1.3.110:
The connection does not get established.

iOS OpenVPN Connect client:
The connection does not get established.

Sanity check:
Enabled OpenVPN on a Balance One FW 8.0.0 with a SpeedFusion connection.
MacOS client/Tunnelblick:
The connection is established and works well

OpenVPN clients (iOS and MacOS):
The connection does not get established.

OpenVPN iOS and MacOS do connect to other OpenVPN servers.

Done. Ticket # 9080579
[With a slightly modified diagnostic - I was able to get Tunnelblick to work on iOS after a bit of tidying up on the Mac side. The OpenVPN Connect client still refuses to work, on both MacOS and iOS]