0
Today, I installed some updates with dnf update
.
After that I cant set some basic iptables rules.
$ iptables -A INPUT --match state --state ESTABLISHED,RELATED --jump ACCEPT`
iptables: No chain/target/match by that name.
This command runnig forever
$ modprobe iptable_nat
and also this run forever
$ iptables -t nat -L
Other rules working nice.
Has anybody a tip to solve this issue?
Info of dnf-update
Transaction performed with:
Installed dnf-2.7.5-2.fc27.noarch @updates
Installed rpm-4.14.2-1.fc27.x86_64 @updates
Packages Altered:
Erase kernel-4.18.13-100.fc27.x86_64 @updates
Install kernel-4.18.16-100.fc27.x86_64 @updates
Erase kernel-core-4.18.13-100.fc27.x86_64 @updates
Install kernel-core-4.18.16-100.fc27.x86_64 @updates
Erase kernel-devel-4.18.12-100.fc27.x86_64 @updates
Install kernel-devel-4.18.16-100.fc27.x86_64 @updates
Upgraded kernel-headers-4.18.15-100.fc27.x86_64 @updates
Upgrade 4.18.16-100.fc27.x86_64 @updates
Erase kernel-modules-4.18.13-100.fc27.x86_64 @updates
Install kernel-modules-4.18.16-100.fc27.x86_64 @updates
Upgraded vim-minimal-2:8.1.450-1.fc27.x86_64 @updates
Upgrade 2:8.1.483-1.fc27.x86_64 @updates
Scriptlet output:
1 warning: file /lib/modules/4.18.13-100.fc27.x86_64/updates: remove failed: No such file or directory
2 cat: write error: Broken pipe
3 Running as unit: run-ra5568fc978d4459eb86c989526d8c755.service
4 Running as unit: run-rfcb91a7b68a94775bb87bf88d9608331.service
First rule the ACCEPT has an apostrophe after the T. Also you could try -j ACCEPT Also you could try this iptables -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT – cybernard – 2018-10-31T12:50:33.970
Same error like
iptables -A INPUT --match state --state ESTABLISHED,RELATED --jump ACCEPT
– akop – 2018-10-31T12:54:27.423what version of iptables are you using? – cybernard – 2018-10-31T13:02:31.647
iptables v1.6.2
– akop – 2018-10-31T13:18:46.580iptables v.1.8.1 is current I would try updating first. – cybernard – 2018-10-31T14:21:40.787
How can I update to 1.8.1? 1.6.2 is the newest in the repo. – akop – 2018-10-31T14:46:43.747
Let us continue this discussion in chat.
– cybernard – 2018-10-31T18:55:38.287Same issue with
iptables v1.8.0
and fedora 29. – akop – 2018-10-31T22:57:08.160