This is to confirm that your OpenVPN client is working with the .ovpn profile you posted a week ago? If any different than your 1st post, please update. Trying this through StarLink. Thanks for your insight.

  @RF_Dude my current, working profile (with sanitized WAN IP):

client
dev tun
proto udp
float
nobind
cipher AES-128-CBC
comp-lzo no
resolv-retry infinite
remote-cert-tls server
persist-key
auth-user-pass
explicit-exit-notify
remote 80.x.x.x 1194
<ca>

a bit different, I believe difference is connected to upgrade of my ER done in between. As a result - currently works with actual openvpn client (before I had to use older version).

If your issue is also caused by change of WAN IP, try to use my method: 

- remove all the tunnels created on the router (I think it can be important for removing "tunnel" interface used in the route table)

- reboot router, maybe upgrade the software

- create needed tunnel from the scratch.

  @JarekPrzybyl Your parameters, like others that I've tried, work and show VPN Active under Insight > VPN Status. I'm using Private Internet Access provider (PIA).  Seems an address is assigned. This "remote local ip" changes once in a while.... curiously, the 2nd octet changes.    

 

Important to note that the Default WAN remains without VPN for all traffic, and there is only WAN3 in use over DSL (dynamic public IP).  I've created a new Interface for the VPN with a PVID 9 and exposed it on a spare LAN port.  .  

 

NO traffic flows.  This seems like a common complaint of many looking for OpenVPN support.  in the least, VPN handshaking should be accumulating bytes of traffic.

 

A local university has a /16 block of public IP's assigned to them.  I'm testing the VPN by creating a STATIC ROUTE to 141.117.126.20 via VPN_Austria which is my VPN test case, sending the traffic overseas to make it obviously different than locally routed.  Using Tools >  Network Test > traceroute to ping via Gateway > Interface VPN_Austria to 141.117.126.20 I get 1 10.5.121.1 (10.5.121.1) 2997.976 ms !H 2998.364 ms !H 2999.680 ms !H Host is Unreachable.  This could be due to it being a different VLAN, and perhaps I have to physically access the port it is untagged at to use it, not available via Tools?  My router located 3 hours away, so I'll check this when I go there. 

 

That is where I'm at and from what I understand from this forum...  many others experiencing the same.  Many seem to get the VPN status UP, but a route out is missing, meaning no data flow.    Thanking anyone for their insight or potential solution vectors to try.  

 

Omada Router is ER7212PC v1.0 / 1.3.1  / 5.14.34.4.