Quote from: Akruidenberg on September 25, 2026, 06:40:37 PMI cant update to the latest release.
pkg clean -ay && pkg update -fQuote from: AlpAne on September 25, 2026, 12:07:07 PMHave anyone actually verified that this solution works for multiple PC/Xbox clients connecting through UPnP at the same time.Like I said before in this topic : Forget OPEN NAT and keep things simple at a nice and comfortable Moderate NAT level with STRICT-PORT Enabled for your Gaming Clients :)
Quote from: erwinvanlonden on September 25, 2026, 04:07:41 AMBy default when you instantiate a VM in a somewhat older Proxmox version, it will attach a x86_64 processor (depending on the underlying hardware). This will become incompatible with some of the later Python libraries such as NumPy which seem to require some fancy processor features that are exposed with newer processor architectures. Therefore when I changed the underlying virtual cpu to x86-64-v2 in Proxmox and rebooted the VM, that problem went away.There are more of those : https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels
Quote from: nero355 on September 25, 2026, 10:01:47 PMWhat kind of issues were you having ?
Quote from: GCustom on September 24, 2026, 09:10:05 AMI'd really like to see multiple monitor targets per gateway, with some simple quorum/weighting logic, e.g. if one target stops answering but two others are healthy, don't declare the connection down. Those same few well-known targets could be reused across gateways while each gateway probes them through its own connection.I suggest mentioning this @ https://github.com/opnsense/core/issues because it simply makes sense! :)