Firwall rules not deleted

webix

Member
Feb 14, 2015
10
0
21
Hello folks.

I don't know if it's a bug or not...
I have created a LXC container. I maded some firewall rules for that VPS on the panel.
Later i delete the VPS. If i create a new one, the firewall rules of the old one appear on the new VPS.

I maded some tests and noticed that the firewall file is not deleted when proxmox delete the VPS.

Bug or feature? (i am more for a bug!)
 
I don't know if it's a bug or not...
I have created a LXC container. I maded some firewall rules for that VPS on the panel.
Later i delete the VPS. If i create a new one, the firewall rules of the old one appear on the new VPS.

I maded some tests and noticed that the firewall file is not deleted when proxmox delete the VPS.

I cannot confirm this behavior - seems to be a misunderstanding, possibly post an example (.fw file as well as the result of iptables-save)
 
I cannot confirm this behavior - seems to be a misunderstanding, possibly post an example (.fw file as well as the result of iptables-save)
It also happens on a freshly installed proxmox server.
Steps to reproduce the problem (with the firewall enabled on cluster and node):
- Create a container (on my demo, the container got the ID 100).
- Enable the the firewall for the container.
- Set some firewall rules for the container (doesn't matter what rules).
- Delete the container.
- If you go to /etc/pve/firewall folder, the 100.fw file is still there with the firewall rules inside.
- Create a new container (ID 100 again).
- If you check the firewall, It is enabled and the rules we created for on the previous container are still there.

Resuming, when you delete the container, the .fw file is not deleted like it should. Also, i don't understand what .fw file you want i send you. The problem is that the .fw file is not deleted when the container is deleted. It doesn't matter the rules that are inside or the iptables-save result.

The expected behavior is that proxmox delete the .fw file when you delete the VPS. And is not the case.
 
Steps to reproduce the problem (with the firewall enabled on cluster and node):
- Create a container (on my demo, the container got the ID 100).
- Enable the the firewall for the container.
- Set some firewall rules for the container (doesn't matter what rules).
- Delete the container.
- If you go to /etc/pve/firewall folder, the 100.fw file is still there with the firewall rules inside.

The above is not reproducible - which version do you use? Post

Code:
pveversion -v
 
:~# pveversion -v
proxmox-ve: 5.0-20 (running kernel: 4.10.17-2-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.17-1-pve: 4.10.17-18
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-4
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: not correctly installed
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.11-pve17~bpo90
 
Question: When you delete the VPS on the panel, doest the firewall file for that VPS is deleted too?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!