Search results

Honestly - is this thread meant as a joke? If you already had tried out PVE and followed the forum for a while, you would realize how strange this thread is. The Proxmox guys and the community are very helpful, and I'm not even talking about the quality of the products here, which is...

Thank you Fabian, this made it work. I first had to clean/reinitiate all mounts and datastores, but then it worked.

@t.lamprecht datastore creation works indeed flawlessly with cli. But I still have the problems backupping (the same CT) to a completely newly created NFS store (so no old "junk" sticking around). Btw, backuping to another local (ext4) datastore on the PBS works without problems. PVE error:

@t.lamprecht Ok, thank you.

First of all I would like to thank you for your enormous efforts to create PBS. Btw, I'm not sure if you anticipated Rust maybe getting integrated into the Linux kernel https://hackaday.com/ :) I'm having problems with backing up to a Datastore residing on a NFS share. Beta2 installed from .iso...

Thanks @spirit , I've followed this thread for the past days in the background :) Great job! What's the ETA for these updates in no-sub repo?

I have as well a problem booting the newest kernel 5.4.41-1-pve. As a guess, maybe it's related to the encrpted LVM2 disk - It hangs even before being asked to enter the crypt passphrase. Booting the previous kernel 5.4.34-1-pve then works as expected again. PVE had been installed over Debian...

@spirit We worked it out, great. Sorry, it was my bad, having on exactly that node with this specific VM still the older ifupdown2 version from May 16th. It's when you realize there's a .deb.1 file around ;) With the CT it worked, because on that node where the CT resides, the updated...

Mail with log is sent. Ok, thanks for the info.

Exactly the same happens with "ifreload -a". Debuglog is prepared, I'll send you a "Laissez nous un message" on your website for further email contact, ok? edit: In the meantime, here some "not founds" as a log extract: info: loading builtin modules from ['/usr/share/ifupdown2/addons'] info...

Hi @pieteras.meyer , did you see the bug only now , because otherwise you don't use the FW, or was it a typo and you "can't" confirm it? :)

Hi @spirit , OS is Debian 9.x Unfortunately it's still not working, even with e1000 1. Changed nic (live) from virtio to E1000 # ping ok 2. Enabled Firewall on e1000 nic # ping ok 3. Applyied SDN (without other changes) # ping not ok 4. Rebooted VM # ping ok 5. Again applied SDN (without other...

@spirit There is no change in the output of "ovs-vsctl show" before and after simply because I only "Apply" SDN without any changes made to config of Zones, Vnets or VM nic VLAN. This is the situation: VM-01: - no VLAN configured, NIC attached directly to vmrb0 - FW flag on VM nic active...

Getting closer: For CTs with enabled FW flag it works now, but still not for VMs. So after "Apply" to SDN, then on the VM-nic the Firewall flag has to be disabled for the VM to regain network. Then the FW flag can be enabled again and network keeps running.

@spirit This patch seems to partially work, almost there.. If a CT or VM has "firewall" activated in its network settings, on "applying" SDN it loses network again and must be rebooted OR the firewall flag has to be set to disabled (without reapplying SDN, and then no reboot is required).

I see. Are you using the mysql database? Maybe a helper table with zone/vnet/VMs assignments could do the job, so you don't have to "scan" the interfaces. But there being a same possible race-condition case, this would mean checking the helper table again, when pressing the "Add" button in the...

"SDN over/in parallel to OVS" mainly because I've already got a bunch of VLANs configured with OVS, and switching them all over to SDN means work, especially before being sure everything works as expected. But honestly, now I become a bit insecure about OVS: @spirit , I thought OVS is needed and...

Ok, I see. Maybe an additional hint on the "Vnet remove" confirmation popup could already help.

Yes, this is default - and apparently will remain default, and that's ok, it's how most of firewalls do it as well

Some feature request for the UI: - Do not allow Vnet to be deleted if in use, analog to not being able to delete Zones, if in use by a Vnet.