Hi Paolo.
I found the mistake in my configuration myself. The reason of that the
"0" appears was, that the agent_to_peer.map was wrong mapping.
The correct mapping is:
id=XXXX ip=127.0.0.1
Thanks for your previous instructions. Now I can collect the traffic
using netflow.
--
Mark
W dniu 02.05.2013 22:27, [email protected] pisze:
Hi Paolo.
I compile the lastest pmacct. I configure quagga, and the peer session
is active:
[...]
show ip bgp sum
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
127.0.0.1 4 YY 35 234430 0 0 0 00:13:55 0
...
and of course correct information about my peers.
[...]
But... using pmacct -s there is "0" as SRC_AS and DST_AS printed:
SRC_AS DST_AS SRC_IP DST_IP SRC_PORT DST_PORT ...
0 0 AAA BBB 35726 41135 ...
^^ ^^
I think, that it should be number of AS??? Would you be so kind and tell
me where is the mistake of my configuration?
Configuration of quagga:
router bgp YY
bgp router-id XXXXX
neighbor 127.0.0.1 remote-as YY
neighbor 127.0.0.1 port 17917
neighbor 127.0.0.1 update-source XXXXX
...
Configuration of pmacctd:
daemonize: true
pidfile: /var/run/pmacctd.pid
syslog: daemon
interface: eth0
aggregate: src_host, dst_host, src_port, dst_port, src_as, dst_as,
proto, tos
plugins: memory
pmacctd_as: bgp
bgp_daemon: true
bgp_daemon_ip: 127.0.0.1
bgp_agent_map: /usr/local/pmacct/current/etc/agent_to_peer.map
bgp_daemon_port: 17917
In debug of pmacctd there is only BGP_KEEPALIVE received and
BGP_KEEPALIVE sent entry.
Regards
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
