Bug 11777 (GEOIPDIFFER)

Summary: GeoIP information in WebUI and firewall rulesets differ
Product: IPFire Reporter: Peter Müller <peter.mueller>
Component: ---Assignee: Peter Müller <peter.mueller>
Status: CLOSED FIXED QA Contact: Peter Müller <peter.mueller>
Severity: Major Usability    
Priority: Will affect most users CC: alexander.marx, michael.tremer, stefan.schantl
Version: 2   
Hardware: all   
OS: All   

Description Peter Müller 2018-06-29 22:50:16 UTC 
Tested with:
(a) 185.233.106.XXX
    -> native GeoIP country: DE
    -> firewall rule seems to treat it as DE
    -> WebUI shows: unknown country

(b) 195.201.26.XXX
    -> native GeoIP country: DE
    -> firewall rule seems to treat it as DE
    -> WebUI shows: RU

Since this makes GeoIP related firewall rules extremly unreliable, I consider it quite critical. Occurred on a system running Core Update 120, with current GeoIP database (triggered manually) installed.
Comment 1 Peter Müller 2018-06-30 16:34:54 UTC 
Michael mentioned this is caused by two different GeoIP databases. :-|
Comment 2 Peter Müller 2018-06-30 17:10:49 UTC 
https://patchwork.ipfire.org/patch/1850/
Comment 3 Peter Müller 2018-07-17 20:40:53 UTC 
Patch has been accepted.

However, since MaxMind announced EOL for GeoLite databases at 1st January 2019, we need to think about moving to libloc until then.