Hi Frederic, Jerome, It's correct there is no support for geo aggregation within pmacct and i find it an interesting topic. Generalizing, whatever approach is taken some sort of mapping is required, ie. route to location, router (ie. sFlow exporter, NetFlow exporter, BGP next-hop) to location or BGP community to location, and would be nice to keep this open and flexible.
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? 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? Frederic: would your interest lie more on the first or the second case? Also, do we agree on such breakdown or you/anybody can see any further cases? Cheers, Paolo On Wed, Nov 21, 2012 at 10:24:12AM +0100, J?r?me Fleury wrote: > Hi Fr?d?ric, > > that is an interesting question. There is no easy way that I know to do > what you want as far as I know. Obviously, this advocates the need for a > "plugin architecture" inside pmacct, which I strongly support. > > Also, let me imagine something: > > - have a special BGP daemon that would be plugged into your geoip database > and that could encode geographical information into BGP communities > - then the pmacct BGP daemon could read these communities and aggregate > with that information > > This is probably not feasible yet. > > Jerome. > > > On Tue, Nov 20, 2012 at 8:30 PM, Fr?d?ric GABUT-DELORAINE < > [email protected]> wrote: > > > Hello everybody, > > > > First of all, pmacct is a great tool, thanks for the amazing work :-) > > > > We use it to collect netflow and sflow from our routers and we have a lot > > of mysql instances to aggregate into different ways our flows. We aggregate > > per AS, per flow, per subnet, per interface, per router? And we would like > > to be able to aggregate per geographical information (country, continent, > > etc.). I have not seen anywhere a way to do that in pmacct so : > > > > 1. Is there an easy way I missed ? :-) > > 2. Would you advise to use per subnet aggregation and to have a lookup in > > our geoip base ? (we loose pmacct flexibility and we have really a lot of > > sql entries to update :-) ) > > 3. Would you advise to develop the same mecanism pmacct has with the bgp > > daemon ? Except of instead of getting the BGP information from the route > > our "plugin" would return all the geographical information ? > > > > What is the best way to implement the geographical aggregation according > > to you ? > > > > Thanks in advance, > > > > Best regards, > > > > -- > > Fr?d?ric Gabut-Deloraine | Network Architect > > Dailymotion | 140 boulevard Malesherbes, 75017 Paris, France > > > > > > > > _______________________________________________ > > pmacct-discussion mailing list > > http://www.pmacct.net/#mailinglists > > > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
