-
### Describe the bug
*After lxd init on a bullseye, iptables rules are not created. @Kayou proposed a solution*
*Not sure it's still the case*
------
```
#!/bin/bash
iptables -w -A INPUT…
-
OS: Ubuntu 22.04
When restarting apf, the previously existing iptables rules are not cleaned and causing the rules to multiply.
```
root@db09-2:~# iptables -S | wc -l
17
root@db09-2:~# servic…
-
```bash
sudo vi /etc/iptables/rules.v4
sudo iptables-restore
-
**The 'ping' command is blocked**
I was trying to ping another computer on my LAN with the following command:
ping 192.168.1.2
Which gave this output:
PING 192.168.1.2 (192.168.1.2) 56(84) bytes o…
-
### What would you like to be added
Podman has the ability to run containers with ports forwarded to them (e.g. `podman run -p 8080:80 ...` starts a container with port 8080 on the host forwarded to …
mheon updated
4 weeks ago
-
*Version of the collection:* 0.1.2.
*Steps to reproduce.* Run the following commands:
```sh
cd extensions
TEST_IMAGE="geerlingguy/docker-debian12-ansible:latest" molecule test
```
*The ex…
-
Hello,
I’m using weave CNI in a K8S cluster, on Rocky Linux 8 (RHEL8 based) with firewalld enabled.
I noticed that on firewalld reload/restart, iptables are flushed. This is the expected behavio…
-
enhancement
## What you expected to happen?
Persistent firewall settings, even after firewalld reload
## What happened?
Weave chains & rules in IPTABLES (on a specific node) disappear when reloa…
-
I tried below code to create iptables rule. Puppet succeeded but iptables rule was neither created in iptables nor in firewalld chain. What's wrong with it?
firewalld_direct_passthrough {'loopback …
-
atm (podman-4.5.0-1.fc38.x86_64), netavark calls rules with unpredictable names in standard iptables rules. E.g.
```
Chain POSTROUTING (policy ACCEPT)
...
NETAVARK-1D8721804F16F all -- 10.88…