You could also do what I do. Use quagga to setup a peering session to your sensors and in addition to the full BGP feed you can inject your own internal prefixes and ASNs.
Regards, --Jason On 4/8/11 6:02 PM, Paolo Lucente wrote: > Hi Tristram, > > OK, thanks for confirming your current setting for nfacctd_as_new. On the > private IP addresses, well, you did mention private IP addresses in your > original email - hence i was wondering too how did you meant. > > So far i can propose you two solutions: > > * trivial solution, external to pmacct: spot the ASNs reported as 0 and > possibly constrain further on the IP prefix (ie. 180.222.64.0/21) via > an SQL query and replace the zro with your actual ASN. I mean something > a-la: "UPDATE <table> SET src_as=<your ASN> WHERE src_as=0 ..." > > * internal to pmacct: please read about bgp_stdcomm_pattern_to_asn in > CONFIG-KEYS. Essentially it revolves around tagging routes with some > standard community XXXXX:YYYYY and see that reflected in the database, > ie. Peer-AS=XXXXX, Origin-AS=YYYYY. > > Cheers, > Paolo > > On Sat, Apr 09, 2011 at 12:20:01PM +1200, Tristram Cheer wrote: >> Hi Paolo, >> >> I have this in my config >> >> nfacctd_as_new: bgp >> >> When you ask about private IPs in the BGP I'm not sure what you mean, In the >> BGP feed it comes from a public IP, the table is a full route table and in >> the as file I only have 180.222.64.0/21 in there >> >> >> Hope this helps >> >> >> Tristram >> >> On 9 April 2011 05:11, Paolo Lucente <[email protected]> wrote: >> >>> Hi Tristram, >>> >>> Can you say what the 'nfacctd_as_new' directive is set to or whether >>> it's left to its default value? Can you also say whether the private >>> IP addresses are present at all in your BGP? >>> >>> Your approach will not work. And it's expected that own ranges are being >>> reported with no ASN information. Can suggest solution(s) but want to get >>> a better overview first. >>> >>> Cheers, >>> Paolo >>> >>> On Thu, Apr 07, 2011 at 05:54:13PM +1200, Tristram Cheer wrote: >>>> Hi All, >>>> >>>> I'm having a bit of trouble with src_as and dst_as, I have a BGP session >>> up >>>> and running and it's working for all except our own ranges and some >>> private >>>> IP's, I would like to be able to have a txt file with a set of static >>>> AS/NETWORKS as well as the BGP session for lookups. I thought I could do >>>> this via bgp_peer_src_as_map >>>> >>>> I have a text file with: >>>> >>>> 45230,180.222.64.0/21 >>>> >>>> and in my nfacctd.conf file I have >>>> >>>> bgp_peer_src_as_map: /etc/nfacctd_as_map.txt >>>> >>>> >>>> But src_ip or dst_ip with network 180.222.64.0/21 in it shows 0 ASN, Any >>>> clues? >>>> >>>> >>>> Cheers >>>> >>>> Tristram >>> >>>> _______________________________________________ >>>> 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 > -- Jason Chambers UCLA [email protected] 310-206-5603 _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
