On first boot the firewall print some ugly errors: Stopping system log daemon... [ OK ] Bringing up the loopback interface... [ OK ] Setting hostname to ipfire.localdomain... [ OK ] Setting up firewall Bad argument `geoip' Try `iptables -h' or 'iptables --help' for more information. Bad argument `geoip' Try `iptables -h' or 'iptables --help' for more information. Bad argument `geoip' Try `iptables -h' or 'iptables --help' for more information. Bad argument `geoip' Try `iptables -h' or 'iptables --help' for more information.
I suppose this is best with Peter and I assume this breaks the entire feature.
Yes, I observed that, too, and will take care about this.
This is because the geoip kernel module is not loaded on the first boot, yet. Is there any particular reason for this, or can we load it on first boot as well?
The iptables command should automatically load this module.
Hm, apparently, it does not do so on the first boot. Would loading it explicitly (like we did before: https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/initscripts/system/firewall;h=75ea8abdfecb86c33d18aed087665ab5de2d6fad;hb=HEAD#l43) be OK for everyone?
https://patchwork.ipfire.org/project/ipfire/patch/3bbbc672-74d6-37b2-b122-aac537faa9ac@ipfire.org/
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=816b0e08c68a63d61bb98adf0b6236b6578115d2
The patch doesn't help. I still got these messages at first boot.
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=5b0eca95280d4eca42d54b007f4fd41c33a82152
https://blog.ipfire.org/post/ipfire-2-27-core-update-164-is-available-for-testing
https://blog.ipfire.org/post/ipfire-2-27-core-update-164-released