[SOLVED] Ntop GEO MAP
-
New version released for PFSENSE. Issue officially fixed.
-
Now let's wait for ntopng 4.0 to arrive on pfsense.
-
Hello Guys,
By me the GeoIP is not really working with the fix on this thread. What am i dooing wrong? i did this one.
mwexec("{$fetchcmd} -o {$output_dir}/GeoLite2-City.tar.gz -T 5 "{$geolite_city}"");
mwexec("{$fetchcmd} -o {$output_dir}/GeoLite2-ASN.tar.gz -T 5 "{$geoip_asnum}"");and:
$geolite_city = "https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-City&license_key=xxxxxhidexxxxxxxxxxxx=tar.gz";
$geoip_asnum = "https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-ASN&license_key=xxxxxxxxhidexxxxxxxxx&suffix=tar.gz"; -
-
@dragoangel Hello i have uninstalled and installed ntopng and put de license back but no success. I see also on the NTOP page that are an update available is 4.0. Do i need that version to install it on pfsense?
-
@erbalo this notification about update in ntopng can't be applied to pfsense, as this update must be done by mainteiner of ntopng pfsense package.
After you entered license and saved config you click on update geoip database button? Doesn't know why you say that is not working when all fine, no issues. You can ssh to pfsense and check files modification dates if you not sure that you have latest databases or provide other details or proofs, not only words 'it not working'. Community can't help in such way.
-
Yes i did also used the update button after install ntopng and license key.
I have tried this command to check the modification but no success. Cheked the file if still there using file editor and it is.
dir /T:W \usr\local\share\ntopng\GeoLite2-City.tar.gz
-
@erbalo said in [SOLVED] Ntop GEO MAP:
Yes i did also used the update button after install ntopng and license key.
I have tried this command to check the modification but no success. Cheked the file if still there using file editor and it is.
dir /T:W \usr\local\share\ntopng\GeoLite2-City.tar.gz
Someone please to help me why my geoip not working in NTOPNG?
-
Is there an current solution/fix for this? The issue still persist
-
@overlord which PfSense version are you using?