Bug #6987
closedntopng needs Google API key for GeoIP map
0%
Description
ntopng needs to be updated to a version that supports use of a Google API key and the ntopng settings page needs a field to enter the API key.
See this issue about adding support for the API key https://github.com/ntop/ntopng/issues/646
The current version fails when you try to look at the GeoIP map with a Google API failure.
Files
Updated by Kill Bill over 7 years ago
- File ntopng.diff ntopng.diff added
Please, test the attached patch and report back. (Would like to submit a PR on GitHub, however the only thing that GitHub produces for me ATM is a nifty HTTP 500.)
Updated by Kill Bill over 7 years ago
- File 98c38351acf58f2ea9987cd42e267e2e80168f99.patch.txt 98c38351acf58f2ea9987cd42e267e2e80168f99.patch.txt added
Well... this additionally need a patch to the ntopng port itself (basically the one from https://github.com/ntop/ntopng/commit/98c38351acf58f2ea9987cd42e267e2e80168f99.patch but the last hunk needs to be modified). Apparently this was never released. A working patch attached, however I frankly think you should take this to https://bugs.freebsd.org/bugzilla/ as this is not a business for pfSense.
Updated by Kill Bill about 7 years ago
Apparently no patching required with ntopng-2.4.2016.10.14 - you can configure the API key in Preferences - Users - Google APIs Browser Key. Can be closed.
Updated by Stuart Wyatt about 7 years ago
The bug referenced the need for ntopng version 2.4 to resolve the problem, so why is it being closed when version 2.2 is still being used?
Shouldn't it be resolved when the package is updated to use version 2.4 and the key can be entered in the WebUI?
Updated by Jim Pingle about 7 years ago
ntopng 2.4 is available on pfSense 2.4, and it works there. If/when the package is updated on other branches it will work there, too.
Thus it's being closed. There is nothing for us to do related to this issue.
Updated by Stuart Wyatt about 7 years ago
Thanks, that's the information I was missing.
Updated by Kill Bill about 7 years ago
It is working on 2.3.3 snapshots as well.