Messages

Hello List,

thanks to get your attention...I'm managing a OPNsense (v21.1.6) with two external and about 5 internal interfaces let's call them Zones. One internal Zone, connected to a physical internal interface should communicate to Segment: 1.2.3.0/24 (for Example) through the second external interface which works fine, and an other internal Zone which is connected to a VLAN-Interface should communicate, unfortunately, to the identical IP-Range (1.2.3.0/24) through an IPSec-VPN.

So to be clear:
192.168.1.0/24 on Int1 through Ext2 to 1.2.3.0/24
and
192.168.2.0/24 on VLAN2 through an IPSecVPN to 1.2.3.0/24

The destinations (1.2.3.0/24) are different serviceproviders for different purposes.

So i've configured phase2 of the IPSecVPN with the obove source net (192.168.2.0/24) and destination.
First it all worked fine, which was clear to me, because i configured the source (192.168.2.0/24) in phase2, so the IPSecVPN should not be used for source 192.168.1.0/24...but a couple of days later i realized that it did that, the traffic comming from 192.168.1.0/24 was routed through the IPSecVPN to the wrong Serviceprovider.

Maybe this scenario is unsupported, are there any hints what to do in such a case (identical target IP-Ranges with diferent providers)?

any help is welcome...

Hello List,

i updated from 19.1.10_1 to 19.7 a few day ago, so my opnsense should be up to date. But my security-audit looks like this:

***GOT REQUEST TO AUDIT SECURITY***
vulnxml file up-to-date
python37-3.7.3_1 is vulnerable:
python 3.7 -- multiple vulnerabilities
CVE: CVE-2019-9948
CVE: CVE-2019-9740
WWW: https://vuxml.freebsd.org/freebsd/a449c604-a43a-11e9-b422-fcaa147e860e.html

1 problem(s) in the installed packages found.
***DONE***

Can someone confirm that this is normal ?

Thanks