Messages

Thank you, here's the update log..

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.10_1 at Wed Oct 30 14:17:37 UTC 2024
Fetching subscription information, please wait... done
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 856 packages processed.
Updating repo-mihak repository catalogue...
No CRL was provided for /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=repo.mihak.link
No CRL was provided for /C=US/O=DigiCert Inc/CN=DigiCert TLS RSA SHA256 2020 CA1
No CRL was provided for /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA
Fetching meta.conf: . done
No CRL was provided for /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=repo.mihak.link
No CRL was provided for /C=US/O=DigiCert Inc/CN=DigiCert TLS RSA SHA256 2020 CA1
No CRL was provided for /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA
Fetching packagesite.pkg: ... done
Processing entries:
pkg: wrong architecture: FreeBSD:13:amd64 instead of FreeBSD:14:amd64
pkg: repository repo-mihak contains packages with wrong ABI: FreeBSD:13:amd64
Processing entries... done
Unable to update repository repo-mihak
Error updating repositories!
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

It's October now, I'm on 24.10_1 business..

The matching OPNsense 24.10 series does not yet exist. Images are available to switch this installation to the latest business edition.

I have menu items, status + Log File with version: 24.4.3-amd64

2024-10-10T10:47:54   Notice   wireguard   wireguard instance WG_XXXXX (wg1) started   
2024-10-10T10:47:54   Notice   wireguard   /usr/local/opnsense/scripts/Wireguard/wg-service
2024-10-10T10:47:54   Notice   wireguard   /usr/local/opnsense/scripts/Wireguard/wg-service-control.php: plugins_configure monitor (,WG_XXX)   
2024-10-10T10:47:54   Notice   wireguard   /usr/local/opnsense/scripts/Wireguard/wg-service-control.php: ROUTING: keeping inet default route to

Allright, got this working to one side by adding a gateway, adding rules directing to this gateway and some NAT. All based on https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html and some info from this forum.

Surprises me there's no how-to since this is a very standard setup.

Hi All,

I have two sites with OPNSense latest business edition. Sites A and B are connected via a wireguard tunnel. This tunnel is running fine from LAN, I can reach A from B and visa versa  8)

Now the issue is, both sites have wireguard road warrior setup, they are working and can access LAN and even tunnel all networking when using 0.0.0.0/0. But I cannot reach the other site's LAN ...

I've used the site2site and road warrior setup from the official docs, IP setup is quite similar to the examples.
https://docs.opnsense.org/manual/how-tos/wireguard-s2s.html
https://docs.opnsense.org/manual/how-tos/wireguard-client.html

I've spend several days and tried all kind of different settings (with/without interfaces, extra NAT) but for the life of me cannot get it to work..

What also puzzles me is that one of the sites has got a legacy IPSec s2s connection and this is accessible from the road warrior  ???

Obviously I'm missing something but what?? anyone can guide me into the right direction?

Thanks in advance....