Hi Paolo, yes, thanks: it just works with this flow_to_rd_map, for src_as and peer_src_as, that are now properly filled.
However I still don't have anything neither in as_path nor in src_as_path (and also not in comms, but it's not that useful for me). Is there anything to do? regards, Olivier Le 11 oct. 2013 à 21:02, Paolo Lucente <pa...@pmacct.net> a écrit : > Hi Olivier, > > The scenario is supported. You using 1.5.0rc1? If so, you need to add > a flow_to_rd_map map. More info in: "examples/flow_to_rd.map.example" > in the pmacct distribution tarball. In principle you should need just > a line like: > > id=<route distinguisher> ip=0.0.0.0/0 > > Let me know how it goes. > > Cheers, > Paolo > > On Fri, Oct 11, 2013 at 08:02:02PM +0200, Olivier Benghozi wrote: >> Hi, >> >> I'm trying to implement a working config of nfacctd with bgp thread to push >> some netflow stuff into a PostgreSQL DB. >> >> I have some Netflow v5 streams (that is, transporting few information) and >> an i-MP-BGP reflected session, which sends all the routing table in the >> VPNv4 address family (nothing in the IPv4 unicast AFI/SAFI), since the >> traffic is in a VRF. >> My problem is that I need to have those VPNv4 routes (whose the Route >> Distinguisher is known) to be successfully matched with the netflow records >> by nfacctd, to fill all the fancy AS information (as_path, src_as, and so >> on). >> >> In my conf I use things like bgp_agent_map (to match all netflow speakers >> to my unique BGP session router_id, with bgp_ip=the.rou.ter.id ip= >> 0.0.0.0/0), bgp_peer_src_as_type: bgp, and bgp_src_as_path_type: bgp. >> >> But src_as, as_path... sadly stay at 0. >> >> Is this working mode possible? Is there something obviously wrong in my >> parameters? >> >> Thanks by advance . _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
