[quagga-users 14951] Re: announce problem between quagga and cisco router
Yavuz Maşlak <[email protected]> Mon, 19 Feb 2018 22:37:54 +0300
| Newsgroups | gmane.network.quagga.user |
|---|---|
| Message-ID | <CAH47Nx_-F5Fq+ppbUbozXdP+6yyRfQ=C0nnMyiDg-mUgsM8GrQ@mail.gmail.com> |
--===============2784794129691873565== Content-Type: multipart/alternative; boundary="f403045f8bd6978a50056595d4b4" --f403045f8bd6978a50056595d4b4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 <[email protected]> wrote: > On Mon, Feb 19, 2018 at 1:45 AM, Yavuz Ma=C5=9Flak <[email protected]= > > 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-n7Wb/xkVUn1Wk0Htik3J/[email protected] [email protected] > Dirtside Systems ......... Web: <http://www.dirtside.com/> > --f403045f8bd6978a50056595d4b4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div><div><div>once i listen port 179 with tcpdump, I= only observe as following that only the cisco serves port 179 .=C2=A0 Wher= eas the quagga listens port 179 <br>root@router2:~ # netstat -na | grep LIS= TEN<br>tcp4=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 0 *.2605=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 LI= STEN<br>tcp4=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 0 *.179=C2=A0=C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 LISTEN<br>tcp6=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 0 *.179=C2=A0=C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 LISTEN<br>tcp4=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 0 *.2601=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 LISTEN<br><br></div>Also trying to reach to port 179 using = telnet , the quagga closes the session <br></div><br># telnet 127.0.0.1 179= <br>Connection closed by foreign host.<br><br></div>is it a problem ? <br><= br></div>But i can reach=C2=A0 port 2605 and 2601.<br><div><br><div><div><d= iv><div>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<br= >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<br>22:27:53.231631 IP 172.16.17.2= .179 > 172.16.17.1.29994: Flags [P.], seq 154:235, ack 1, win 15111, len= gth 81: BGP<br>22:27:53.401543 IP 172.16.17.2.179 > 172.16.17.1.29994: F= lags [P.], seq 235:316, ack 1, win 15111, length 81: BGP<br>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<br>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: BG= P<br>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<br>22:27:53.439842 IP 172= .16.17.2.179 > 172.16.17.1.29994: Flags [.], seq 3521:4981, ack 1, win 1= 5111, length 1460: BGP<br></div></div></div></div></div></div><div class=3D= "gmail_extra"><br><div class=3D"gmail_quote">On Mon, Feb 19, 2018 at 5:50 P= M, William Herrin <span dir=3D"ltr"><<a href=3D"mailto:[email protected]" t= arget=3D"_blank">[email protected]</a>></span> wrote:<br><blockquote class= =3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd= ing-left:1ex"><span class=3D"">On Mon, Feb 19, 2018 at 1:45 AM, Yavuz Ma=C5= =9Flak <<a href=3D"mailto:[email protected]">[email protected]</= a>> wrote:<br> > # show ip bgp neighbors 172.16.17.2 advertised-routes<br> <br> </span>> It comes nothing<br> <br> Now you've confirmed that quagga isn't advertising the route (as<br= > opposed to the Cisco router filtering it).<br> <br> There are several common causes for this:<br> <br> 1. The exact route you define in the router bgp network statement is<br> not present in the routing table.<br> 2. The ip prefix-list you applied does not allow the route to be advertised= .<br> 3. The as-path access list you applied does not allow the route to be<br> advertised.<br> 4. An error in your route map prevented the lists from being applied<br> so the default deny-all list was applied.<br> <div class=3D"HOEnZb"><div class=3D"h5"><br> Regards,<br> Bill Herrin<br> <br> --<br> William Herrin ................ <a href=3D"mailto:herrin-n7Wb/xkVUn1Wk0Htik3J/[email protected]">herr= in-n7Wb/xkVUn1Wk0Htik3J/[email protected]</a>=C2=A0 <a href=3D"mailto:[email protected]">[email protected]<= /a><br> Dirtside Systems ......... Web: <<a href=3D"http://www.dirtside.com/" re= l=3D"noreferrer" target=3D"_blank">http://www.dirtside.com/</a>><br> </div></div></blockquote></div><br></div> --f403045f8bd6978a50056595d4b4-- --===============2784794129691873565== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Quagga-users mailing list Quagga-users-UOy77sIEA+cAd7ICUelF/[email protected] https://lists.quagga.net/mailman/listinfo/quagga-users --===============2784794129691873565==--