Search results

That is the normal state that a bridge interface goes through (especially when spanning trees are configured) as it starts up. Blocking state: don't forward any traffic to prevent loops Forwarding: This interface doesn't make a loop, or the spanning tree coose it to forward traffic, so enable...

Best advice: Setup a firewall, having all the IPs on it, and then have the firewall route to the LXCs on their own VLANs. Other than that, you will have to create the virtual IP MAC for those IPs, and set the LXC's interfaces to that on the same bridge as the outside IP/interface

yeah, these scripts aren't "guaranteed", the beter/more guaranteed method: reboot the ProxMox whenever there are things changing on openvswitch, or other host network related interface changes

Wht you gain on the swings, you loose on the merry-go-round. One of the "pains" that OpenVZ never made it into the kernel ;(

min.io isn't that difficult... perhaps the redundancy stuff (YEs, ceph + objectstorage is a different kettle of whales) In my case: Some no -- regulatory requirements makes it easier to have it in environments directly controlled by us. The "WORM" case I'd like to use is the cloud archive /...

How I did it: (1) first set all the PBS_.... environment paramters (YEs, I could've done it all with proxmox-backup-debug, I was just reusing already tehre stuff ...) Then created this file as verify-delete #!/bin/bash echo $* echo proxmox-backup-debug api create...

Good day, In the GUI I can select a specific Snapshot to verify, but I can't find an equivalent in the CLI commands? Reason: I've copied the datastore files from a to-be-decommisioned PBS to the new server over the network, but there had been some rsync errors, so I want to run over those with...

Good day, Using PBS and very happy with it, but I'm busy taking over infrastructure with a BorgBackup and I'm wondering about anybody else that did such a replacement of any tips-tricks-a-traps I need to be aware of and if it's a feasible choice, or not? Reason for doing it, would be to...

There are two types of incremental backups: 1. "Dirty" block level incremental 2. "tar"/streaming level incremental 1. is done with QEMU block devices, that have kept a changed/dirty blocklist since the last backup. The rules are the QEMU VM should not have restarted, shutdown-started, nor...

pe Perhaps /etc/hosts still have IPv4? start to remove the IPv4 addresses from the nodes and see if/how they stay up/go-down to see if there isn't a config you missed somewhere?

Hmmm... any plans to make a backported OpenVSwitch 3.x available for this kernel? I'm tracking/seeing strange troubles with 6.1 (like the packets not send up to the IntPort for the VLAN tagged to the IntPort, but the packets do arrive in the bridge) and wonders about kernel interactions

Do not pre-maturely optimize, and a hypervisor is not your firewall, and never should be. When doing the firewall for all, it is easier with the bigger hosting companies that does MAC bindings - been there, got the scarrs - the firewall solved the problems all at once - than to manage it on all...

You might be surprised and if the performance is really the problem, then do it in the LXC/VM's nftables yourself

ZFS: yes, you *can* setup a concatenated VDEV that is then mirrored - not "easy", rather use the mdadm stripe/concat method to creat a single 2TB drive to attacj in the mirror

Wrong thread to ask, as the problem that needs the nesting, is the dbus/systemd

Why not put a firewall (like pfSense) in the path between the internet and the VMs/LXCs ? that way you can even have each VM on it's own VLAN/network, and have a "decent" GUI/WebUI to do the needed filterings PVE's firewall isn't meant for this type of filtering, more like a broad stroke...

I'd advise to have a dedicated (firewall like pfSense?) do the PPPoE

the correct bug/feature request to refer is: https://bugzilla.proxmox.com/show_bug.cgi?id=2943 as # 3177 marked as duplicate of #3169 that's marked as a duplicate of #2943

the correct bug/feature request to refer is: https://bugzilla.proxmox.com/show_bug.cgi?id=2943 as #3169 marked as a duplicate of this one

the correct bug/feature request to refer is: https://bugzilla.proxmox.com/show_bug.cgi?id=2943 as #3169 marked as a duplicate of this one