Mailing List Archive

On Sun, Feb 18, 2018 at 1:37 PM, Yavuz Ma?lak <maslakyavuz@gmail.com> wrote:

> On the quagga, as run command sh ip bgp sum
> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> State/PfxRcd
> 172.16.17.2 4 100 2595798 2828 0 0 678738 01:42:35
> 685381
> 192.168.229.150 4 65100 742620 3894 0 0 0 2d16h15m
> 680941
>
> On the cisco router, sh ip bgp sum
> As you see the cisco can't receive any prefix from the quagga as following
>
> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> State/PfxRcd
> 172.1.6.89 4 65200 485578 113928 12007991 0 0
> 22:30:37 685395
> 172.16.17.1 4 100 107 111539 12008005 0 0
> 01:44:26
> *0*
>
> What can the problem be ?
>

Don't know, but "show ip bgp neighbors 172.16.17.2 advertised-routes" may
lead you there.

Regards,
Bill Herrin


--
William Herrin ................ herrin@dirtside.com bill@herrin.us
Dirtside Systems ......... Web: <http://www.dirtside.com/>

# show ip bgp neighbors 172.16.17.2 advertised-routes
BGP table version is 0, local router ID is 192.168.229.150
Status codes: s suppressed, d damped, h history, * valid, > best, =
multipath,
i internal, r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path

It comes nothing

Regards

On Mon, Feb 19, 2018 at 12:51 AM, William Herrin <bill@herrin.us> wrote:

> On Sun, Feb 18, 2018 at 1:37 PM, Yavuz Ma?lak <maslakyavuz@gmail.com>
> wrote:
>
>> On the quagga, as run command sh ip bgp sum
>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>> State/PfxRcd
>> 172.16.17.2 4 100 2595798 2828 0 0 678738 01:42:35
>> 685381
>> 192.168.229.150 4 65100 742620 3894 0 0 0 2d16h15m
>> 680941
>>
>> On the cisco router, sh ip bgp sum
>> As you see the cisco can't receive any prefix from the quagga as following
>>
>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ
>> Up/Down State/PfxRcd
>> 172.1.6.89 4 65200 485578 113928 12007991 0 0
>> 22:30:37 685395
>> 172.16.17.1 4 100 107 111539 12008005 0 0
>> 01:44:26
>> *0*
>>
>> What can the problem be ?
>>
>
> Don't know, but "show ip bgp neighbors 172.16.17.2 advertised-routes" may
> lead you there.
>
> Regards,
> Bill Herrin
>
>
> --
> William Herrin ................ herrin@dirtside.com bill@herrin.us
> Dirtside Systems ......... Web: <http://www.dirtside.com/>
>

On Mon, Feb 19, 2018 at 1:45 AM, Yavuz Ma?lak <maslakyavuz@gmail.com> wrote:
> # show ip bgp neighbors 172.16.17.2 advertised-routes

> It comes nothing

Now you've confirmed that quagga isn't advertising the route (as
opposed to the Cisco router filtering it).

There are several common causes for this:

1. The exact route you define in the router bgp network statement is
not present in the routing table.
2. The ip prefix-list you applied does not allow the route to be advertised.
3. The as-path access list you applied does not allow the route to be
advertised.
4. An error in your route map prevented the lists from being applied
so the default deny-all list was applied.

Regards,
Bill Herrin

--
William Herrin ................ herrin@dirtside.com bill@herrin.us
Dirtside Systems ......... Web: <http://www.dirtside.com/>

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users

Well How can i configure on the quagga about prefix-list / router-map or
as-path to be advertised regarding routes towards the cisco router ?
There is a 192.168.0.0/22 to be advertised
Could you give me an example about that ?
Regards


On Mon, Feb 19, 2018 at 5:50 PM, William Herrin <bill@herrin.us> wrote:

> On Mon, Feb 19, 2018 at 1:45 AM, Yavuz Ma?lak <maslakyavuz@gmail.com>
> wrote:
> > # show ip bgp neighbors 172.16.17.2 advertised-routes
>
> > It comes nothing
>
> Now you've confirmed that quagga isn't advertising the route (as
> opposed to the Cisco router filtering it).
>
> There are several common causes for this:
>
> 1. The exact route you define in the router bgp network statement is
> not present in the routing table.
> 2. The ip prefix-list you applied does not allow the route to be
> advertised.
> 3. The as-path access list you applied does not allow the route to be
> advertised.
> 4. An error in your route map prevented the lists from being applied
> so the default deny-all list was applied.
>
> Regards,
> Bill Herrin
>
> --
> William Herrin ................ herrin@dirtside.com bill@herrin.us
> Dirtside Systems ......... Web: <http://www.dirtside.com/>
>

once i listen port 179 with tcpdump, I only observe as following that only
the cisco serves port 179 . Whereas the quagga listens port 179
root@router2:~ # netstat -na | grep LISTEN
tcp4 0 0 *.2605 *.* LISTEN
tcp4 0 0 *.179 *.* LISTEN
tcp6 0 0 *.179 *.* LISTEN
tcp4 0 0 *.2601 *.* LISTEN

Also trying to reach to port 179 using telnet , the quagga closes the
session

# telnet 127.0.0.1 179
Connection closed by foreign host.

is it a problem ?

But i can reach port 2605 and 2601.

22:27:51.748692 IP 172.16.17.2.179 > 172.16.17.1.29994: Flags [P.], seq
2050821377:2050821454, ack 4130014953, win 15111, length 77: BGP
22:27:52.484283 IP 172.16.17.2.179 > 172.16.17.1.29994: Flags [P.], seq
77:154, ack 1, win 15111, length 77: BGP
22:27:53.231631 IP 172.16.17.2.179 > 172.16.17.1.29994: Flags [P.], seq
154:235, ack 1, win 15111, length 81: BGP
22:27:53.401543 IP 172.16.17.2.179 > 172.16.17.1.29994: Flags [P.], seq
235:316, ack 1, win 15111, length 81: BGP
22:27:53.437185 IP 172.16.17.2.179 > 172.16.17.1.29994: Flags [.], seq
316:1776, ack 1, win 15111, length 1460: BGP
22:27:53.437220 IP 172.16.17.2.179 > 172.16.17.1.29994: Flags [P.], seq
1776:2061, ack 1, win 15111, length 285: BGP
22:27:53.439815 IP 172.16.17.2.179 > 172.16.17.1.29994: Flags [.], seq
2061:3521, ack 1, win 15111, length 1460: BGP
22:27:53.439842 IP 172.16.17.2.179 > 172.16.17.1.29994: Flags [.], seq
3521:4981, ack 1, win 15111, length 1460: BGP

On Mon, Feb 19, 2018 at 5:50 PM, William Herrin <bill@herrin.us> wrote:

> On Mon, Feb 19, 2018 at 1:45 AM, Yavuz Ma?lak <maslakyavuz@gmail.com>
> wrote:
> > # show ip bgp neighbors 172.16.17.2 advertised-routes
>
> > It comes nothing
>
> Now you've confirmed that quagga isn't advertising the route (as
> opposed to the Cisco router filtering it).
>
> There are several common causes for this:
>
> 1. The exact route you define in the router bgp network statement is
> not present in the routing table.
> 2. The ip prefix-list you applied does not allow the route to be
> advertised.
> 3. The as-path access list you applied does not allow the route to be
> advertised.
> 4. An error in your route map prevented the lists from being applied
> so the default deny-all list was applied.
>
> Regards,
> Bill Herrin
>
> --
> William Herrin ................ herrin@dirtside.com bill@herrin.us
> Dirtside Systems ......... Web: <http://www.dirtside.com/>
>