u/KaleidoscopeNo9726

I deployed the Proxmox Backup Server as a VM a while back. It has been working great. I noticed that the backup size is larger than the LXC or VMs. For instance, my OPNsense VM is 32GB, but in PBS, it shows as 34.36GB. My Jellyfin LXC is set to 10GB, but only taking 5.26GB according to the Proxmox Summary page. In PBS, the backups are 17.58 GB in size.

Does any one know why the backups are larger in size than the LXC or VM?

What can I do to optimize the backup?

My backup mode is snapshot and the compression is ZSTD.

I have two sites and they are connected via a site-to-site Wireguard VPN. I am using OPNsense on both sites. I have a rules that is allowing port 53/udp between sites.

The issue that I am having is the remote Technitium is able to resolve any hosts belongs to .example.lan (main site) domain. The main site (where am at) could not resolve any hosts belong to the .remote.example.lan remote site domain.

At the main site, when I ran host pc1.remote.example.lan, I received Host pc1.remote.example.lan not found: 3(NXDOMAIN). When I checked the logs at the remote Technitium, I see the request from the main Technitium. Now, when I ran host pc1.remote.example.lan 10.2.7.53, it resolves it.

Here is the response from the remote Technitium.

# Timestamp Client IP Address Protocol Response Type RCODE Domain Type Class Answer
48  2026-09-19 13:33:39 10.0.7.53 Udp Authoritative NoError pc1.remote.example.lan A IN A 10.2.5.15

The logs from the main Technitium has no Answer.

I inherited a VXLAN EVPN network and it has been pretty stable until recently. From time to time, the layer3 or at least the inter-vlan drops for a few seconds. It happened last week, yesterday and today.

For what I can tell, the layer2 is fine. The VLANs gateway is on the service leafs (vPC pair). We are using ePBR to force the inter-vlan to the firewall, which is connected to the service leafs, the firewall will route the traffic back to the service leafs.

This has been stable for several months and no network changes. At this point, I'm not sure if the Nexus pair (where the SVI with ePBR) is causing the network downtime or the firewall.

We recently migrated to OpenShift for virtualization and containers. This was a month or two ago.

The firewall has a static route to the 172.16.0.0/16 with the next-hop of the HSRP VIP of the vPC pair. The service leafs are learning the 172.16/16 from a Catalyst leaf. All the VLANs are stretched to the service leafs via L2VNI.

```

[Fw]---/29---[service leafs pair]---[spines]---[cat9k leaf]

```

I know the layer2 (or L2VNI) didn't fail because Zabbix is not reporting any ICMPloss between it and the hosts in the same VLAN. However, any subnets within the same VRF drops for a few seconds.

The leafs CPU utilization history is basically idle 1% - 3%. The firewall is the same thing. Network utilization wise, we are using less than 800Mbps of traffic and the network is 40Gbps links.

I'm trying to get some ideas what I should look for to identity the issue and what is causing it.

My nexus version is 10.5.4 and the Catalyst is 17.15.4b. The Palo Alto firewalls (active/passive) are version 11.14.0.

Thanks.

I am trying to update my Cyclone 2 firmware from v3.2.6 to v3.5.2. This is the steps to try to update the firmware.

1. Plugged the controller via the GameSir USB cable
2. GameSir Connect (v1.13.6) sees the controller
3. I clicked the firmware update
4. The controller turned off and the GameSir Connect says the update failed

The only way for me to turn on the controller was to reset pin button for 5 secs.

I tried the same way with the dongle from v1.1.2 to v1.2.1. The moment I clicked update, the light turned off then the GameSir Connect says the update failed.

The PC is Windows 11 and the firewall and Virus & Threat protection settings disabled. How can I update the Cyclone 2 firmware and its dongle?

I have a question to the folks who use interface groups and floating rules. When I was using the old way of rulesets, I only created floating rules. This worked wonderfully for me.

However, the new rules totally messed up the ordering of my rules. I now have floating, group and interface rules. The folks who only use interface rules probably not affect by the new OPNsense rules logic. The worse part is a old floating rules became group rules and got place below of my "internet only" rule:

Interface: all-zones (all SVIs, but WAN)
Action: pass
Direction: in
Source: any
Destination: !rfc1918
Destination Port: any
Gateway: WAN_DHCP

The "internet only" rule remained floating because of the OPNsense logic of multiple interfaces automatically a floating rule. I have a deny rule applied to the WAN such as:

Interface: surveillance (firewall group only member is SVI 5)
Action: block
Direction: in
Source: any
Destination: !rfc1918
Destination Port: any
Gateway: none

This rule used to be a floating rule and became a group rule; therefore, it got placed below the internet rule. There is no way for me to move this rule above the "internet only" rule. Now, the IP cameras are able to access the internet. This is one example.

Does this mean that instead of writing a single rule for the interface, I have now to create a rule per interface? I have 28 VLANs. If I follow the OPNsense login, I have to create 28 rules so that I put these rules at the bottom of the list. Is that right?