Bug 12767

Summary: geoip errors with core164
Product: IPFire Reporter: Arne.F <arne.fitzenreiter>
Component: ---Assignee: Peter Müller <peter.mueller>
Status: CLOSED FIXED QA Contact:
Severity: Crash    
Priority: Will affect all users CC: michael.tremer, peter.mueller
Version: 2   
Hardware: unspecified   
OS: Unspecified   

Description Arne.F 2022-01-27 10:55:49 UTC 
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.
Comment 1 Michael Tremer 2022-01-27 13:26:43 UTC 
I suppose this is best with Peter and I assume this breaks the entire feature.
Comment 2 Peter Müller 2022-01-27 21:42:08 UTC 
Yes, I observed that, too, and will take care about this.
Comment 3 Peter Müller 2022-01-29 15:24:50 UTC 
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?
Comment 4 Michael Tremer 2022-01-29 15:25:39 UTC 
The iptables command should automatically load this module.
Comment 5 Peter Müller 2022-01-29 15:30:50 UTC 
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?
Comment 8 Arne.F 2022-02-11 10:55:40 UTC 
The patch doesn't help. I still got these messages at first boot.