From systemctl -a status shorewall.service Sep 01 12:16:52 localhost shorewall[1371]: ERROR: Your kernel/iptables do not include state match support. No version of Shorewall will run on this system Sep 01 12:16:52 localhost systemd[1]: shorewall.service: main process exited, code=exited, status=3/NOTIMPLEMENTED Using 4alpha2 kde i586 live cd, in live mode. Message was different in gnome, but as gnome won't start, can't copy/paste the message. IIRC, it was ERROR TC_ENABLED=Internel requires Packet Mangling in your kernel and iptables. Reproducible: Steps to Reproduce:
I think this bug is a blocker for alpha2
CC: (none) => eeeemail, ennael1Whiteboard: (none) => 4alpha2
CC'ing Oden who updated the iptables package.
CC: (none) => oe
blino just fixed something in iptables. I'm not sure if it was meant to address this issue.
CC: (none) => mageia
Do you still get this error? If so please attach your shorewall config to this bugreport.
Created attachment 4313 [details] Compressed contents of /etc/shorewall Note that this is a live cd, running in live mode, so any config changes were done by /usr/sbin/finish-install.
Note that this only occurs in live mode. Once installed on the vb hard drive, and the network configured, shorewall does start ok.
This is really strange. I just booted the live cd again, and this time shorewall started ok. As it only seems to affect live mode, and it's inconsistent, I'm lowering the priority.
Severity: critical => minor
Created attachment 4319 [details] Debugging output It's a timing problem. Happened on first boot after installing from the gnome live cd (2nd build). Starting shorewall works after system is running. Attached is the output of journalctl -a -b |grep -e finish -e eth0 -e enp0s3 -e shorewall -e iptables
Created attachment 4320 [details] Compressed output of journalctl -a
Created attachment 4321 [details] Compressed output of journalctl -b from 2nd boot after install Doesn't just affect live mode and 1st boot after install. Here's the output of journalctl -b from the 2nd (or 3rd) boot, after install.
Raising the severity again, as it isn't as limited as it appeared before.
Severity: minor => major
Confirmed here. shorewall fails to start 4alpha2 DVD 64
is this really a timing issue? can this be fixed by systemd "after=" stuff? perhaps systemd-analyze plot in those cases where it happens and where it doesn't happen could be used... what is the chance that NetworkManager is re-reloading the kernel modules to be used in iptables/ip6tables?
CC: (none) => alien
@davidwhodgins IMHO this bug is old. If you could close it: it is also listed in the errata ? Thanks !
CC: (none) => dvgevers
Can somebody please provide a more precise description for the Errata, or remove it from Errata when it doesn't happen anymore with final? Otherwise we get questions like https://forums.mageia.org/en/viewtopic.php?f=7&t=6857
CC: (none) => doktor5000
AFAIK it's fixed. Removing from Erratas, please add back with explanations if still valid.
CC: (none) => stormi
Appears to be fixed so closed
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => FIXED