Search results

I think I can chock this up to my inexperience working with iptables: I've removed the source port settings from my rules and I think it's working now :-) Testing continues... EDIT: I still get different behavior when connecting directly on the local LAN versus remotely via NAT onto the local...

In fact the situation is more problematic than I thought - if I add an In->DROP rule I can't connect using Security Group rules no matter if the In->DROP rule is before or after the Security Group rule in the GUI. [EDIT] So I removed this catch-all DROP rule and further experimented. I get...

As noted in another thread (can't post links yet: forum.proxmox.com/threads/22923-pve-Firewall-Default-policy-on-node-and-VM-level-And-how-to-make-it-works-with-CT?p=117671#post117671), I concur that the default firewall rule set in Datacenter->Firewall->Options as Input policy->DROP does not...

Re: pve-Firewall - Default policy on node and VM level / And how to make it works wit Not knowing this fact had me scratching my head for hours today! This seems like a bug in the Proxmox firewall GUI implementation: this option should be removed from the GUI or should cause the expected...