Le 21 nov. 2012 à 18:54, Paolo Lucente <[email protected]> a écrit : > Hi Frederic, Jerome,
Hi Paolo, > I see two cases essentially: 1) Router to location and BGP community to > location is easy to solve as the source for that will always be internal > data/docs: a map, with syntax similar to pre_tag_map would do the job, > ie. "id=<location ID> [ip|bgp_nexthop|src_comms|comms]=<data>"; agree or > would anybody propose a different approach? I agree, our communities defines a lot of geographical information from where the route was learned, however the aggregation through interfaces id and router is enough for us. The mapping "country" -> community through an external API to BGP suggested by Jerome is kind of a hack of a BGP daemon instead of hacking directly pmacct :-) > 2) route to location: this > is interesting since data for routes out of the own network is to be > taken from somewhere - API, DB, etc.: is anybody aware of any public/ > freely accessible data in this sense and/or has a recommendation which > data set to use? We use maxmind API : http://www.maxmind.com/download/geoip/api/c/ Our idea is to load this in a plugin and then do exactly the same as the BGP plugin : for each IP, we do an internal lookup in the maxmind database loaded in ram. > Frederic: would your interest lie more on the first or the second case? Definitely the second case which seems to me the proper way to do this :-) Best regards, -- Frédéric Gabut-Deloraine | Network Architect Mob. : +33 (0) 6.40.67.37.33 | skype : fgabutdeloraine Dailymotion | 140 boulevard Malesherbes, 75017 Paris, France _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
