Messages

I also just updated. 25.7.11_9 to 26.1_4 and all seems good. I migrated my rules to Rules(New) and it seems ok. I use Proxmox Virtual Environment 9.1.4. I was worried when it took awhile to reboot, but made a cup of tea and it had rebooted when I returned.

Thank you OPNsense Team for all your work!

Upgraded 25.1.12 to 25.7 smooth.
Great work!

Thank you for your explanation. Again not using ISC-DHCPv4, but it was configured with vlans just disabled. I just converted to DNSMasq the day before. Great work to all.

Just updated from 25.1.11 and everything seems good. I use CrowdSec,Dnsmasq,os-chrony,os-cpu-microcode-intel,os-nut,os-udpbroadcastrelay and os-wol . I did notice ISC DHCPv4 was configured on 25.1.11, but nothing is in the GUI now. I,m not using ISC DHCPv4,but did want to mention it. I will see if anything comes up.

Hello. So I just upgraded to 24.7.5 on a Proxmox VM with crowdsec and all went well. Reboot VM at end of upgrade. Its a little N5105 box.

I'm also getting the same error.
I have never had any errors in a upgrade before.

So I'm on OPNsense 23.1.3_4-amd64. I have been running with "schnerring" guide since it was posted. I substitute in Surfshark Wireguard. I followed "pmhausen" advice initially and that seem to work. I did try the above procedure and everything seems to work great (touch wood).
Thank you for the hard work on developing OPNsense. Thank you "schnerring" for the guide.

So I installed OPNsense 23.1 with Wireguard onto Proxmox 7.3-4 using a config.xml backup. I passthrough nics and the usb stick.I used pmhausen suggestion. I installed the Plugins (even the wireguard plugin,  just the missing one) rebooted and all is good. os-wireguard-go shows as installable, so I think I'm using wireguard-kmod. I installed patch # opnsense-patch -c plugins 2ed1f987eb97d, don't know if i needed to. As it stands all is working great (touch wood). Thank you for the assistance and thank you for another great release!

I'm using Wireguard. I install the os-wireguard plugin and then "pkg install wireguard-kmod".
To test 23.1 would I "# opnsense-update -ur 23.1.r1" then remove the plug-in or remove it from 22.7.10_2 before the update.

Hello, I run OPNsense 22.7_4-amd64 on Proxmox 7.2-7 with three Intel nics passthrough. If I add "iommu=pt" to my boot command line, it reduces my nics to 100TX from 1000TX.

I add only "quiet intel_iommu=on"

/etc/modules
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd

I dont know if this helps you, but it work for me. No idea way.
I played around with VYOS and had the same problem. So i dont think its a OPNsense problem. For me anyway.

Hello.
It's probably me over thinking this or just being a little daft.
I want to restart my openVPN (Surfshark) connection when it goes down.
It never has the same ip. I have searched the forum and found some information, but find myself really confused right now.
Is their not a simple straight forward way of implementing this.
I'm running OPNsense 22.1.9-amd64.

Everything seems to be good with:

# opnsense-update -bkzr 22.7.b
# opnsense-shell reboot

##Proxmox 7.2

# Intel Corporation I350 Gigabit Network Connection two port passthrough
Port One = WAN
Port Two = Vlan parent (4 vlan in total)

# Intel Corporation 82574L Gigabit Network Connection passthrough
LAN

No parent interface enabled

openVPN to Surfshark

Used this Guide:
https://schnerring.net/blog/opnsense-baseline-guide-with-vpn-guest-and-vlan-support/
Substituted OpenVPN for Wineguard

OPNsense 22.1.8_1-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1o 3 May 2022

os-api-backup (installed)   1.0_1   2.35KiB   OPNsense
os-chrony (installed)   1.5   20.6KiB   OPNsense
os-firewall (installed)   1.1   56.4KiB   OPNsense
os-qemu-guest-agent (installed)   1.1   19.2KiB   OPNsense
os-theme-rebellion (installed)   1.8.8   5.20MiB   OPNsense
os-udpbroadcastrelay (installed)   1.0_2   44.8KiB   OPNsense
os-wol (installed)

I've been using OPNsense on a Bare Metal box, so will post any problems I encounter with this VM.

Hello:
I have OPNsense 22.1.1_3 on Proxmox 7-1.10 with 3 Intel nics passed through, I have Surfshark VPN and 4 vlans. I setup with this guide (https://schnerring.net/blog/opnsense-baseline-guide-with-vpn-guest-and-vlan-support/).

In the past I had a problem with VMs and vlan connections, but it was my Proxmox setup that was the problem.
Everything is running rock solid as of this writing. ( touch wood. )
Went everything is running good I don't update for a week or so. I let small bugs work their way out. If it's not broke don't fix it syndrome.

Again, try to look at your Proxmox network setup. I know I'm not really giving you a solution, but I know its possible.
Try rolling back to 22.1.1_3.

Brian

Hello I know it's a little late, but this is what I use on a Proxmox VM with intel cards passed through.

dev.igb.0.eee_control    Disable Energy Efficient Ethernet    runtime    0    
dev.igb.0.fc                    Flow Control                                    runtime    0    
dev.igb.1.eee_control    Disable Energy Efficient Ethernet    runtime    0    
dev.igb.1.fc                    Flow Control                                    runtime    0

I have also used this on a bare metal install.

On Proxmox:
igb.0 is WAN
igb.1 is parent for VLAN's
Also have em0 on LAN in Proxmox ,but don't do anything for it.
Hope this helps.

Well done. Thank you.