@squeezy .... bump please.....

I have same issue.

Thanks

@bingo600 said in How to send email after openvpn has connected successfully:

https://forum.netgate.com/post/950706

Tks for the reply bingo, I'll take a look at the topic

and yes, it is already configured to send email from pfsense

I forgot to mention: We are using SG-4860 appliances and did not have the problem with 21.02.1 or older versions.
Maximum number of simultaneously connected oVPN clients is around 150 to 170, but problem also occurs with ~30 clients only.

We use 500MBit fiber for our ISP connection and are far from reaching its limits:

eafc80f5-c45a-4cd5-8af6-a4c770f3ccd5-image.png

System is also not too busy:

48fbaaf1-d4f7-4c49-9940-d0d507bb331a-image.png

@dementian I started with 2.4 and upgraded to 2.5 with the same problem. Then did a fresh install of 2.5 (lost wirguard!) and still got the same problem..

After a lot of research, I was able to find the error after a long time.

It was because my password was too long.
The login on the website worked, but not via openVPN.

I am currently still unclear why it did not work. However, I can already confirm that it works without errors with a slightly shorter one.

@ddbnj
Nice to have "helped" ... Or NOT 😊
Glad i'm still on 2.4.5-p1 , and not chasing "ghosts"

/Bingo

@huskerdu
The difference is, when you copy it, you have two rules, the original one and one on the new tab. When you move it, there is only the rule on the new tab, but the original one no longer exists.

Fixed by creating another LDAP auth server and entering the same config as before ...

I will diff that in detail, for now: works!

@dannyr1992 We have managed to get the Firewalls to communicate. Turns out it was compressions settings which is madness.

Even thought the firewalls are communicating and the routing table is correct the LANS cannot communicate with each other.

Does anyone have any ideas

Does anyone else face this issue, or has an idea where to start solving this issue?

@viragomann Thanks a lot :)

@zabi

Hi,

my output,

[2.5.1-RELEASE][admin@pfSense.home.arpa]/root: grep scrub /tmp/rules.debug scrub on $WAN inet all fragment reassemble scrub on $WAN inet6 all fragment reassemble [2.5.1-RELEASE][admin@pfSense.home.arpa]/root: grep vpn_networks /tmp/rules.debug table <vpn_networks> { 192.168.77.0/24 }

My connection to RDP after authentication to Windows, the screen blank..
After that my ping will be timed out..
If i close my RDP Windows, the connection will be back after 30 seconds..
I can access to HTTPS, HTTP, SSH without any issues..

Just wonder is it the version 2.5.1 bugs..
I will deploy version 2.5.0 to try it out again..

@divsys You were right. I was missing the Client Specific Override entry.

I created a CSO on the server side, selecting the correct OpenVPN server,
with the Common Name from the client certificate certificate,
my IPv4 Tunnel Network set to 10.0.9.0/24
my IPv4 Local Network/s set to 192.168.1.0/24
my IPv4 Remote Network/s set to 192.168.10.0/24
and my routing fired right up.

You are the man.

@peterzy It seems that the pre release "2.6.0"corrects the Mult iWAN bug.
See the forum post related to that issue.

nevermind, found the issue. i had specified an IP address reservation for the pfsense firewall on the openvpn server, and had the subnet wrong. it was set to the vpn tunnel gateway, instead of 255.255.255.0, so pfsense had some issues with it. changed appropriately and it works now... RTFM.....