Hi Luca.
Thanks for quick answer! I was convinced it bgp_probe_client.pl should
establish a connection. So, now the packet (seen in tcpdump) betwen
quagga and the bgp_probe_client.pl is going. But the quagga report that:
[...]
2013/05/05 23:37:11 BGP: stream_read_try: read failed on fd 13:
Connection reset by peer
2013/05/05 23:37:11 BGP: YY.YY.YY.2 [Error] bgp_read_packet error:
Connection reset by peer
[...]
In the quagga there is no connection to YY.YY.YY.2:
[...]
r1# sh ip bgp sum
...
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
YY.YY.YY.2 4 65520 12 23 0 0 0 never Active
[...]
The quagga configuration is:
[...]
router bgp AABBCC
neighbor YY.YY.YY.2 remote-as 65520
neighbor YY.YY.YY.2 prefix-list WORLD_OUT_LOCALHOST out
neighbor YY.YY.YY.2 route-map RM-LOCALHOST-out out
ip prefix-list WORLD_OUT_LOCALHOST seq 5 permit any
route-map RM-LOCALHOST-out permit 10
[...]
The bgp_probe_client.pl configuration is:
[...]
# BGP
my $local_ip = 'YY.YY.YY.2';
my $local_as = 65520;
my $remote_ip = 'YY.YY.YY.1';
my $remote_as = AABBCC;
# nProbe
my $nprobe_ip = '127.0.0.1';
my $nprobe_port = 4096;
[...]
What is wrong?
--
Mark
W dniu 05.05.2013 22:48, Luca Deri pisze:
Marek
The perl script is a server to which your router must connect via BGP and not
the other way round
Luca
Sent from my iPhone (sorry for typos)
On 05/mag/2013, at 21:41, "[email protected]" <[email protected]> wrote:
Hi.
I'm trying to configure nprobe BGP plugin to connect with quagga. I think
something is wrong with configuration of my system or bgp_probe_client.pl. I
configure correctly parameters below:
[...]
# BGP
my $local_ip = '<my local IP>';
my $local_as = 65500;
my $remote_ip = '<IP of the quagga system>';
my $remote_as = <my public AS>;
# nProbe
my $nprobe_ip = '127.0.0.1';
my $nprobe_port = 4096;
[...]
If I run the bgp_probe_client.pl script I see no warning, on the screen there
is nothing displayed, and the scripts seems to be running:
[...]
root@test:~# etstat -eapln
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode
PID/Program name
...
tcp 0 0 0.0.0.0:179 0.0.0.0:* LISTEN 0244594 20360/perl
...
root@test:~#
[...]
But no one packet is send by bgp_probe_client.pl, the:
"tcpdump -n -i eth0 port 179"
on the machine with bgp_probe_client.pl display nothing, just like the script
was not trying to connect to bgp peer? From time to time, the quagga is trying
to connect to the bgp_probe_client.pl but the peer session is not established.
As I read in the manuals, after running the bgp_probe_client.pl should
establish a connection with the quagga, but there is no packet send. Why?
How to diagnoze the problem? Mayby someone have the same issue?
Regards
--
Mark
_______________________________________________
Ntop-misc mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
_______________________________________________
Ntop-misc mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
_______________________________________________
Ntop-misc mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
