Project

General

Profile

Actions

Bug #6987

closed

ntopng needs Google API key for GeoIP map

Added by Stuart Wyatt over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
ntop
Target version:
-
Start date:
12/05/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
All

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

ntopng.diff (2.62 KB) ntopng.diff Add Google Maps API key to ntopng Kill Bill, 12/09/2016 03:50 PM
98c38351acf58f2ea9987cd42e267e2e80168f99.patch.txt (5.19 KB) 98c38351acf58f2ea9987cd42e267e2e80168f99.patch.txt net/ntopng Google Maps API key patch Kill Bill, 12/09/2016 05:18 PM
Actions #1

Updated by Kill Bill over 7 years ago

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.)

Actions #2

Updated by Kill Bill over 7 years ago

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.

Actions #3

Updated by Kill Bill over 7 years ago

Result after patching:

Actions #4

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.

Actions #5

Updated by Renato Botelho about 7 years ago

  • Status changed from New to Closed
Actions #6

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?

Actions #7

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.

Actions #8

Updated by Stuart Wyatt about 7 years ago

Thanks, that's the information I was missing.

Actions #9

Updated by Kill Bill about 7 years ago

It is working on 2.3.3 snapshots as well.

Actions

Also available in: Atom PDF