Site2Site Not Quite Working

Ximulate

As mentioned, check the OpenVPN log on the server to find out if the CSO is applied properly.

The above mentioned settings were input into CSO, and saved. Not sure what else to do. I don't see anything in the log to confirm CSO is applied

server OpenVPN log shows the following, repeatedly:

Firewall Rules on both server and client for OpenVPN:

Pass IPv4 Source: * Destination: *

On server, firewall rules for LAN include:

Pass IPv4 Source: *, Destination 192.168.12.0/24 Port:* Gateway: *

Ximulate

Some more information on this in the log?

I don't see anymore information regarding this in the log.

viragomann

@ximulate
Okay, even noticed that the CSO part is not logged with default log level.
So I changed the log level in the server setting to 3, then I got the info:

Ximulate

@viragomann
Client side OpenVPN log, at verbosity 3:
client OpenVPN Logs.jpg

two things stand out to me:

Error: FreeBSD rout add command failed

I see this warning on the server side OpenVPN logs also:

Verify Warning: unable to get certificate

viragomann

@ximulate said in Site2Site Not Quite Working:

Client side OpenVPN log, at verbosity 3:

The server log is way more of interesting here. The CSO part can only be found in the server log.

Error: FreeBSD rout add command failed

This is due the server is pushing a route for the clients LAN network, which cannot be added naturally.
That's why I don't like this setup method as mentioned above. I'd rather add the remote networks in the client config.
However, it should work anyway.

Verify Warning: unable to get certificate

The whole warning says "Verify Warning: unable to get certificate CRL" (Certificate Revocation List).
This is normal. The client complains that he cannot pull the CRL, since it is not provided in the internet.

Ximulate

@viragomann
One the Server side verbosity 3, I'm now see this:

viragomann

@ximulate
Need to see the section, when the client establishes the connection.

Ximulate

@viragomann

Server side logs (after reboot of client router)...
server_logs.j (pg

At

Jul 20 10:17:04, MANAGEMENT: .......

Those management messages repeat as shown in previous post

viragomann

@ximulate
So there is no note of the CSO in the log. Hence the route within OpenVPN won't work.

As mentioned above in post #8 check if the common name in the CSO and server settings are correct.

Ximulate

@viragomann
That was it! Its now working. Thank you for your help and patience