sharkd: support for MaxMindDB.
authorJakub Zawadzki <darkjames-ws@darkjames.pl>
Fri, 4 May 2018 18:38:19 +0000 (20:38 +0200)
committerJakub Zawadzki <darkjames-ws@darkjames.pl>
Sun, 6 May 2018 09:22:25 +0000 (09:22 +0000)
commit5cdff2610799c8f02f671d1aa7d4ec481d9139be
tree871ec4a55fb9ca0411f479cf80f6177c3a31931d
parenta834d3794d51253df92db196b61ab59b608e0b87
sharkd: support for MaxMindDB.

Call maxmind_db_lookup_process() [via host_name_lookup_process()] before processing request.
It's still buggy, webshark needs a refresh to show endpoint or conversation ipmap,
but it's better than nothing.

It seems to need refresh, cause maxmind_db_lookup_ipv[46] works only for cached entries.

Also cause mmdbresolve is pipe-based, every sharkd need to have it own mmdbresolve process.

Change-Id: I3d588d1fa9e9ba645cc3d0bff3d276b202159d21
Reviewed-on: https://code.wireshark.org/review/27335
Petri-Dish: Jakub Zawadzki <darkjames-ws@darkjames.pl>
Tested-by: Petri Dish Buildbot
Reviewed-by: Jakub Zawadzki <darkjames-ws@darkjames.pl>
sharkd.c
sharkd_session.c