Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Broomstick

#1
Yes thank you I did all that.

To avoid wasting time for everyone I am going to try with a new instance to see if I missed a step... I am more inclined to think it is a Nat or firewall problem.

Is there any good tutorial up to date with the new interface in mind about it ? So that I can retrace the steps and not miss anything?
#2
there is no LAN IP.
as I said. The goal is to be able to access synology webdav and other services from the opnsense generated subnet through the openvpn link generated by the synology.
The opnsense which is the endpoint so the client of the synology server can't ping the gateway inside the openvpn tunnel.
And yes the openvpn connection status is "connected".
The PIA connection I used as a test/training is working fine and i can ping the gateway from that openvpn link for example.

Also it is working fine on Linux and windows
#3
Hi,

As in the title say, I am trying to link up one of my opnsense instance to my nas openvpn server from synology .
The topology is not subnet.
I have used the same tutorials than to connect to Pia openvpn commercial VPN.

It is connecting. But I can't ping the gateway (so the synology) and can't access any services.

The goal was to make available the synology through the openvpn link for the WebDAV and other services capabilities to the rest of the subnet behind the opnsense instance
Any ideas what could be wrong here ?
#4
24.1, 24.4 Legacy Series / do we need new cert?
February 05, 2024, 09:42:32 PM
Hi,

with the new OpenSSL3 integration should we redo the certs created under openSSL 1.1.1w ?