Messages

Hello,

Same behaviour noticed on a 6.7.0 ESXI VM configured with EFI, no issue when moving back to BIOS.

Franco, you're the best.

Thanks a lot!

Hello,

I am currently running 16.7.14 and wanted to perform the upgrade to 17.1 when I figured out that my Hyper-V VMs running Opense are no longer displaying the console.

Other than this, the VMs are running perfectly fine, booting fine except they appear to be stuck during the booting phase on the following screen:



I tried rebooting without any effect. My knowledge of Freebsd being extremely limited, I do not really know what else I can do to get access to the console menu in order to perform the upgrade.

Any idea appreciated.

Thanks!

J.

Hello,

I have a two nodes CARP cluster, each node running OPNSense 16.1.16

The cluster works almost like a charm: the multiple VIPs created are not causing any issue, config is properly replicated from the master node to the backup node.

I however face a strange behaviour with the "WAN" gateway: whenever the two nodes are up, the gateway is only accessible (can be pinged and is seen online) from the master node. As soon as the master node is brought down, the backup node can access the gateway without any issue.

I do not have the same behaviour on other implementations of OPNsense CARP clusters: each and every node can see the gateway online and can access (ping) it any time.

Would any one know what could be causing this?

I'm looking for the exact very same feature.

I'm today trying to replace an oldish TMG that was mostly used as forward proxy, firewall and HTTP web sites publishing RP (the HTTPS workloads were already shifted to MS Web Application proxy).

Replacement solutions that I have shortlisted so far are pfSense and OPNsense, OPNsense being strongly prefered for its team reactivity and short release cycles. However, the lack of Reverse Proxy capabilities remains a major show stopper to its adoption compared to pfSense :(