@execcr said in OpenVPN in existing enviroment: could only ping clients but not reach other ports, firewall completely opened.:

a Zyxel UTM

Why do you not just run your vpn server there just replace it with pfsense? Running an vpn server that is inside your network is always going to be a asymmetrical mess...

Yes indeed that would be it.
Nice to see it got implemented:
https://forum.netgate.com/topic/120569/oddity-with-viscosity-openvpn

I think his question is already answered here https://forum.netgate.com/topic/136428/setup-multiple-subnets-with-dhcp-question

-Rico

Yes. You have to use an extended query so the authentication fails unless the user is a member of that group.

Those VPN access permissions have nothing to do with OpenVPN.

Did you set Firewall Rules in the OpenVPN Group tab?

-Rico

OK, I've just found the reason.

The hiding of the "IPv4 Local networks(s)" edit box is simply because of the selected option "Force all client-generated IPv4 traffic through the tunnel".

As soon as that option is deselected the elusive edit box is displayed again.

You'll need to provide a bit more info than that. You mentioned an east coast server. Where's the other? Generally load balancing has to be configured at both ends. What precisely did you have in mind?

Or you could just ssh to pfsense and cat the file and then copy paste or use scp ;) or sftp to browse your pfsense box - many many ways to skin that cat ;)

i removed key-direction 1 from my config and its gone.

i guess the provider does not support this functionality

Only traffic able to pass through it is ping, and that's from the road warrior to the gateway. Is there a way to allow any traffic to go through it without redirecting gateway? Just so I can selectively choose programs to go through?
Thank you

Sorry if I’m all over the place in my explanation, aside my setup I’ll just explain the issue I had.
Pfsense LAN 192.168.102.x connected to switch.
Switch connect to NAS and PC, worked perfect.
If I made the PC part of the PrivateInternetAccess alias I would lose the ability to connect to the NAS even though it was on the same network.
If I made the NAS Part of the PIA alias it would work but now the rest of my devices couldn’t connect to NAS.

I did, I also later on stated I've tried my LAN v6 but it never worked. Afterwards I got it to work recreating it using identical configuration.

Thank you both @jimp and @JKnott for the help. My issue has been resolved by itself.

Why did you delete the whole Config only to change the encryption settings? You can just Edit all the settings...
Do you have your Firewall Rules in place in the OpenVPN Tab? For testing just do some any any Rule.

-Rico

I was able to finally figure out my issue. While we have multiple public IP addresses, only one is dedicated to the VPN. While both servers were configured to the WAN interface, one was listening on the correct IP and one was not. After setting both servers to listen on the correct interface, it started working. Odd that it breaks now.

Thank you for the response, all of which makes sense. I must do some reading on iroutes.

The examples would benefit from the inclusion of a "last edited" date as its not evident otherwise just how current they are.

Consider that there is also a static route for 192.168.32.0/24 needed on router A.
However, the interface on B facing to router A a is a DHCP configured. It should have a static IP.