Search results

to solve the problem i moved transparent firewall outside Proxmox VE on dedicated hardware...

I don't know....i think the problem is all layer 2 related...bridge...vlan....bridge of virtual interface tagged on vlan

you don't undestand what i'm doing... On Proxmox i have one VLAN aware bridge (vmbr0) with all my vlan i need a pfsense VM with inside a bridge composed of two interface if i use vmbr0 with for example vlan 200 and vlan 1000 to create 2 different interfaces and then on pfsense i use them for...

No vmbr0 doesn't have any real interface linked only vm virtual interface

i have some vms linked to a transparent pfsense bridge....if i migrate pfsense vm remains without network... the only solution is to have 2 synced pfsense transparent firewall on two different cluster nodes... I don't know any other solution...

No in my pfsense installation bridge works only if the bridge is composed on different proxmox ve bridge (for example): net0: virtio=AE:D9:1F:2D:B7:8A,bridge=vmbr0,tag=1000 net1: virtio=7E:83:8A:B0:CD:C4,bridge=vmbr100 but in this way i miss migration capabilities...

Hi, i'm exploring the possibility to have a pfsense transparent firewall on a proxmox ve VM but i reach some limitations (or some misunderstanding) I have a 5 nodes proxmox ve cluster configured with a VLAN aware bridge (trunk connected with all my netwokr vlans) Is it possible to have on a...

i've just configured for testing two synced pfsense vms on 2 different cluster nodes and now i can migrate vms between two cluster nodes... my need is to have only one transparent firewall/IDS on proxmox VE and maintain the capabilitie to migrate vm or firewall through all cluster nodes.

Thank you, Well the only way is to have a pfsense vm (synced) on each cluster node? Or moving pfsense outside cluster btw

Yes you are correct, a distributed transparent bridged pfsense firewall

just for info net0: virtio=AE:D9:1F:2D:B7:8A,bridge=vmbr0,tag=1000 net1: virtio=CA:C1:3A:C8:74:7B,bridge=vmbr0,tag=200 net2: virtio=7E:83:8A:B0:CD:C4,bridge=vmbr100 vlan 1000 is my public network on vmbr0 proxmox (vlan aware trunk) vmbr100 is the other bridge i configured to have all working

Hi, i need firewall and all vm linked to itself are able to migrate indipendently on other cluster nodes I have 6 cluster node and for example i could migrate firewall on node 3 and vm on node 5 for example Today all works only on one node.

Hi, i have one pfsense vm on a proxmox ve cluster act as firewall and IDS with snort, net0: virtio=AE:D9:1F:2D:B7:8A,bridge=vmbr0,tag=1000 net1: virtio=CA:C1:3A:C8:74:7B,bridge=vmbr0,tag=200 net2: virtio=7E:83:8A:B0:CD:C4,bridge=vmbr100 i configured a bridge of two interface (each one on...

Solved with proxmox-backup-file-restore update

on /var/log/proxmox-backup/file-restore [2021-04-28T16:51:04+02:00] PBS file restore VM log [init-shim] beginning user space setup [init-shim] reached daemon start after 0.46s [2021-04-28T14:51:05Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda'...

on PBS appear But on cluster interface i have: proxmox-file-restore failed: Error: given image 'drive-virtio0.img.fidx' not found (500)

Hi, i have an error if i try file restore functionality: obviously i have backup on pbs and i have tried on all backupped vm i have. Some suggestion?

No resources added to HA but we have two groups configured (an old test) Gw and Cluster are on different switches and i think Cluster network works fine during GW reboot (but i have to test...) Testing is difficult...

Hi, i don't know if it's an issue or my fault: We have a 5 node Proxmox VE 6.3 cluster and when we make some update on our firewall/gw (when gateway for some time isn't available for example) , proxmox ve nodes reboots (all nodes on the same subnet obviously) is this a normal behavior? do we...

just upgraded a 6-node cluster with shared iSCSI storage, all seems works fine, just a warning during upgrade on all nodes: Installing new version of config file /etc/frr/daemons ... Installing new version of config file /etc/frr/support_bundle_commands.conf ... Installing new version of...