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 - Quin

#1
I think the main issue is not the re-install of the package, but the segfaults created by pkg.
When I manually install the package after the update, pkg segfaults during the post-install steps. Here is a picture of my current pkg status.

I think what's happening is pkg gets upgraded, breaks and is unable to continue with the remaining steps.
My firewall-01 without update has pkg version 1.19.2
#2
Same problem here. I upgraded my secondary cluster node to 25.7.6 and the update broke everything.
I had to recover the node as described in the other thread, but now a lot of things seem to be broken. For example, Firmware > Plugins does no longer list available plugins and pkg segfaults every single run. I assume the node is lost and needs to be reinstalled.

For testing I upgraded a different vm based on an older snapshot and it also broke with the same issue. I wonder why a obviously broken update is not reverted and still available for download.
#3
Hi!

Are there any downsides to this?

I just wonder why every guide takes the first approach.
#4
Hi,

I would like to run a OPNsense Firewall as a virtual guest on a Linux KVM Hypervisor.
The Hypervisor is connected with 2x 10G Fiber to a Switch.

Now the question is how to best configure VLANs:


  • My first idea was to have a network bridge for each VLAN on the Hypervisor and this seems to work fine. But adding each VLAN to the firewall with a own interface creates a lot of interfaces. Also it will require to reboot the firewall guest and I would like to avoid this.
    Example: Interface A+B (eth0/1) -> Team (team0) -> VLAN (team0.100) -> Bridge (br.team0.100) added to the VM for each VLAN

  • ChatGPT suggested to create a single bridge on the hypervisor and connect this bridge (without any VLANs)
    Example: Interface A+B (eth0/1) -> Team (team0) -> Bridge (br.team0) added to the VM, VLANs configured in OPNsense

I couldn't find many guides about the second approach, but it sounds better, because a new VLAN would not require a guest reboot and it doesn't create lots of interfaces on the hypervisor. So I wonder if there is any best practices for this?

Thanks.