Hello  @Clive_A 

I've asked few month ago about Virtual Interface for OpenVPN/WG client connections.

it was announced in Omada 5.15, but this new firmware is still does not support OpenVPN interface ((

PPTP/L2TP only...

P.S. Can someone help me with the next routing task:

Example: I have OpenVPN Client established

I need 199.188.177.0/24 network to be routed through OpenVPN interface.

It is simply can be done with PPTP/L2TP Client interface. But I can't found/create OpenVPN Client interface.. ((

If it could not be used for the routing -- what the reason for OpenVPN Client existance?? 

P.P.S. 24 hours of testing results:

8411 GREATLY IMPROVED CPU Efficiency!!! Previous firmware had unbelievable LAGS while disconnecting-connecting WAN! All traffic could be freezed fot ~2 minutes! Especially PPPoE reconnecting - it could caused 5 minutes traffic freezing! 1.3.0 fw SOLVED this great problem, THANKS alot to programmers!

8411 poor CPU (algorythm) efficiency is solved!

As the result of improved CPU efficiency is FASTER rebooting. Much more faster NTP (getting Time from inet), Online detection, L2TP connection! enabling Routing Policies - everything is going really faster! All my "disappointing" by 8411 that been slower than old 6120 model are gone now! All I need from the next firmware is OpenVPN client interface for 100% of satisfaction =)

Best Regards.

  @Clive_A Update performed smooth, without any problems. So far working properly for more than one hour without any issues.

  @Clive_A 

Im having MAJOR issues with this

It will not route traffic to and from switch only vlans, with all the same static routes on the switches and router as i had on 1.2.3

EG

Switch SVI 192.168.10.254 (vlan 10)

Switch Static Route 0.0.0.0/0 > 192.168.2.254 (router interface) (vlan 2)

Gateway Static Route 192.168.10.0/24 > 192.168.2.253 (Switch SVI on the router interface) (vlan 2)

NO TRAFFIC ON VLAN 10.  THIS WAS WORKING FINE UP TO 1.2.3

Set client gateways to the router IP - traffic as normal

Setup a test vlan switch only, it seems ALL static routes on the gateway do not function at all.  Routes from the switches get as far as the getway and ann stop there.  From outside via WAN (i opened up NAt to a device) traceroute ends at the gateway.  Also, My Static route for VPN traffic to my VPN server, which is a seperate IP on the main vlan, also did not work.

BONUS
I cannot roll back firmware either in controller or standalone to 1.2.3 - "Upgrade file invalid", even after a factory reset.

EDIT

I was able to roll back to 1.2.3 from the firmware recovery procedure only which was a total pain, but i got there in the end.  All back up and running, and static routes working again

  @Clive_A I'm unable to select WAN Interface for the Virtual WAN even though I have 3 WAN ports configured.

  @GRL 

I did a test here when I saw you were having problems, I can confirm that it is not possible to downgrade, for me everything works as it should so I hope I don't have to downgrade. :-)

  @MR.S 

If you have router interface only VLANs it seems to work fine.  My management vlan was working perfectly.

For me, i found the following issues

Static routes to and from the Switch vlans do not traverse the gateway at all

Static routes form the gateway (for management vlan only) did not reach the VPN server

NOT WORKING routes on gateway

Routes on Switch

From top to bottom

0.0.0.0/0 > transit VLAN interface on ER8411 metric 1

0.0.0.0/0

172.16.0.0/12

10.120.120.0/22 > VPN route for remote site and client vpn pools to VPN server, metric 50 (so its default route doesnt override the main route to gateway, for backup only when main WAN goes down so i can access management vlan through my VPN)

The next two split each half of my /23 user vlans to their respective switches where the gateway SVIs reside for each half of the network (lan,. WiFi)

L2TP client VPNs with IPSec encryption were not working.  The IPsec tunnel established, but the User was unable to connect

This part of the connection was fine

This part was missing

Final Thoughts
Without any config changes on the controller, switches, etc - NOTHING - as soon as i managed to reflash my ER8411 with 1.2.3 through the recovery process, and it got readopted by the OPC200 - everything was working perfectly again

  @GRL 

I tested L2TP here, everything works as it should, both ER8411 as L2TP client and Server, connected Windows 11 pc with L2TP to ER8411 Server.

I can't test routing on LAN but I have some routing to some remote network that I have set up routes so that I can reach these from OpenVPN Sever, these routings worked. so I don't find any errors here with me except one that I can't downgrade.

But I'm still working on finding bugs. I tried to create a virtual WAN interface but I couldn't because I couldn't have more than one untagged VLAN, I don't know if that's wrong or right.

  @MR.S 

Yeah, you have to set every virtual WAN with a different tag - this is how it works on my adapted ER7206 v2 which im not having any issues with

  @GRL 

Ok so you have an ER7206 too :-) have you tested SD-WAN, I only have the ER8411 which has SD-WAN support but need an update to the other routers to test

  @MR.S 

Thants one of the things i wanted to test once my ER8411 had the adapted firmware - but i cannot now, as i had to roll back due to total network breakage!