I am using a networks_file such as this, being the next hop 123.123.123.123, I do have other bgp providers for other routes.
123.123.123.123,17766,223.255.235.0/24 123.123.123.123,56000,223.255.236.0/24 123.123.123.123,56000,223.255.237.0/24 123.123.123.123,56000,223.255.238.0/24 123.123.123.123,56000,223.255.239.0/24 123.123.123.123,55649,223.255.240.0/22 123.123.123.123,55649,223.255.240.0/24 123.123.123.123,55649,223.255.241.0/24 123.123.123.123,55649,223.255.242.0/24 123.123.123.123,55649,223.255.243.0/24 123.123.123.123,45954,223.255.244.0/24 123.123.123.123,45954,223.255.245.0/24 123.123.123.123,45954,223.255.246.0/24 123.123.123.123,45954,223.255.247.0/24 123.123.123.123,55415,223.255.254.0/24 The issue I am having is that altough the AS numbers are properly populated, the BGPNextHop field is always 0.0.0.0 I am using this aggregate list: aggregate: src_host,dst_host,dst_as,src_as,src_port,dst_port,proto,tos,peer_src_ip,peer_dst_ip >From the config keys (http://wiki.pmacct.net/OfficialConfigKeys) i read: > when 'true' ('file' being an alias of 'true') it instructs nfacctd and > sfacctd to generate 'src_as' and 'dst_as' (only! ie. no peer-AS) by looking up > source and destination IP addresses against a networks_file So apparently it won't populate BGPNextHop when using networks file, is that right? Is the only resort to get that information would be to have a bgp session stablished? _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
