Container IPFilter

Apr 18, 2023
20
6
3
After experimenting with the IPfilter option in the firewall, it seems (perhaps I'm entirely wrong) that using the default setup in the GUI it loses network connectivity over IPv4 (not tried V6) if the V4 address was configured via DHCP, but works perfectly fine if the interface was configured using a Static IP. Is this intentional ? Is there a way to still have it function with DHCPV4?
 
This really shouldn't be the case, could you share your firewall rules and options?
 
Screenshot 2024-06-10 at 10.12.20 AM.png
So with the interface set as a static IP I can update the container with no issue but without a static IP set on the interface (using DHCP) I have to remove the ipfilter option for the container to be able to reach out and contact the update servers, or just any server/ip at all.
 
Last edited:
Sorry I misunderstood and thought you just enabled the Firewall.
You're indeed correct, if you set container IPs in the GUI, the IP address is implicitly allowed to communicate with the network, however if it's distributed by DHCP, you have to manually enable the IP address in the Firewall.

This is also mentioned in the documentation:
https://pve.proxmox.com/wiki/Firewall#_configuration_files
 

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!