I’m not able to send a message to user @Clive_A. Could you possibly notify him about the issue? It might be good for him to be aware of it as well, especially if it turns out to be a firmware bug.

  @lukg20 

 

He is tagged so you will probably hear from him soon 

 

  @MR.S 

 

The issue has been clarified. Access to network resources via OpenVPN is being blocked by rule 6, which blocks all ports from WAN to LAN. I've always had this rule, and it wasn’t a problem with the previous firmware. I created a test rule allowing WAN > LAN on the OpenVPN port, but unfortunately, that doesn't help. I have no idea how to solve the problem while keeping my ALL rule.

 

  @lukg20 

 

I see you have some ACL rules, I'm almost 100% sure that's what the problem is. You've blocked some from lan/wan, it's possible that it's blocking responding back to OpenVPN. So my suggestion is to disable all ACL rules, or create some new ACL rules that you put at the very top of your ACL list that allow all traffic from OpenVPN in and out
two new rules one WAN/In and one LAN/WAN that allows all traffic both ways in the OpenVPN IP Pool

 

 

  @lukg20 

 

Good thing you got it working then :-) I don't really have any idea why it worked before, I'm not that familiar with how to configure in stand alone, but as I mentioned earlier, ACL can really trick you so that's why I disable ACL if I get into a situation where things don't work. I've spent hours troubleshooting and it turns out that ACL is messing it up :-)

 

 

  @lukg20 

A basic test for VPN is to ping the gateway. If the gateway is pingable, that means the tunnel is effective. Just FYI.

There are no other reports about the OVPN issue like this.

ACL can be super tricky when you have so many rules there already. It would spend hours or days to fine tune them.

 

I do not receive messages unless I find it necessary for privacy when it comes to public IP and MAC address. Otherwise, any case will be openly discussed.