Re: [pmacct-discussion] iBGP and networks_file

[Steve Dodd]

Just wanted to confirm, setting

networks_file_no_lpm: true


achieved the desired result.

Thanks,
Steve

On 2/24/16, 11:25 AM, "pmacct-discussion on behalf of Markus Weber"
<pmacct-discussion-boun...@pmacct.net on behalf of f...@uucp.de> wrote:

>Hi Steve,
>
>you are using nfacctd_as_new fallback? That is said to work like "When
>'fallback' is specified, lookup is done against the winning longest
>match lookup method (sFlow/NetFlow <= BGP), which can be different for
>source and destination IP prefix.".
>
>If I understand you correctly, you want to have the networks file take
>precedence over BGP, ignoring normal longest match lookups. I remember
>Paolo stating a while ago, that this is/was not possible ... and
>fallback would have been renamed to "longest" make this clear.
>
>... Oh, OTOH, check out networks_file_no_lpm - which "Makes a matching
>IP prefix defined in a networks_file win always" (1.5.2) ... guess this
>is what you are looking for (and what I've been looking for as well ;-).
>
>Markus
>
>
>
>On 24.02.2016 16:57, Steve Dodd wrote:
>> Hi all,
>>
>> I¹m trying to address the case of iBGP learned routes showing AS0 for
>> src_as/dst_as. I have defined a list of our internal network space
>> with a mapping to our AS. However, it appears that an explicit match
>> is required IE:
>>
>> [networks.lst]
>> 65001, 10.0.0.0/8
>>
>> This would result in an appropriate src_as/dst_as mapping of 65001 for
>> 10.0.0.0/8, but not for 10.1.0.0/24.
>>
>> Is this the expected behavior?
>>
>> Thanks,
>> Steve
>>
>>
>> ___
>> 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

[pmacct-discussion] src_as/dst_as populating as 0

[Steve Dodd]

I¹m having an issue where a large number of flows aren¹t populating with
src_as/dst_as information. Here¹s my conf file:

daemonize: true
!debug: true
logfile: /var/log/nfacctd.log
aggregate[in]: src_host, src_as
aggregate[out]: dst_host, dst_as
plugins: memory[in], memory[out]
nfacctd_port: 2055
bgp_daemon: true
bgp_daemon_ip: 199.167.38.86
bgp_daemon_port: 179
bgp_daemon_max_peers: 20
nfacctd_as_new: bgp

I have verified that the IP addresses supplying the netflow export are the
same as the BGP peering session, which was indicated might be an issue in a
previous thread. Does anyone have any pointers or suggestions?

Thanks,
Steve


___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists