Thanks for your answer, but that does not really solve the problem. I have 
already run debug on the protocol, but I am unable to find which of the routes 
cause this error. 
Even so I am accepting only prefixes which originating just from my peer, for 
testing purpose and I still have this issue. 
So I have a few additional questions:
How is malformed route marked in the log? Or is the last route before announced 
error the one which causing this error? And if yes, what can I do for stopping 
BIRD to process this route?
Can I protect BIRD from dropping connection when he received malformed path? 
Under the protection I mean, if there is possible way how to tell BIRD to drop 
malformed routes and continue working with good routes? 
If not is the only possibility to tell my peer to filter that route for me?

Tomas Jirik

-----Original Message-----
From: Ondrej Filip [mailto:fe...@network.cz] 
Sent: Thursday, November 6, 2014 4:25 PM
To: Jiřík Tomáš; bird-users@network.cz
Subject: Re: Malformed AS_PATH error

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6.11.2014 15:48, Jiřík Tomáš wrote:
> Hi,
> 
> I am seeing this error message in bird's log and I am unable to find 
> reason.
> 
> 
> 
> <RMT> PEER: Error: Malformed AS_PATH:
> 40022002080000b8800000b8800000b8
> 
> 
> 
> Weird thing is that if my peer sends me just his prefixes everything 
> is alright. When he sends me full IP table and I apply filter to 
> accept just my peer prefixes, the error occurs again.
> 
> 
> 
> I have theory, that when BIRD reads route with a  malformed path even 
> if he does not  accept it, it drops BGP connection with this error.

Yes, that's right. Some of the prefixes has malformed BGP attribute AS-PATH. 
This behaviour is partially discussed in programmer's documentation.

> So I have 2 questions. Am I correct in my theory? And if so is there 
> way around it?

We the AS path really seems to be odd. You can run debug to see which prefix is 
causing this issue.

                        Ondrej


> 
> 
> 
> best regards,
> 
> 
> 
> Tomas Jirik
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUW5K2AAoJED82D4RIDoWPGpoQAJuWJFZZ+l/kUCbNvXUF1h3Y
yrERtGBGa/bnlsPRw+b49snPFq2H7OQ7jUDTgJa/g0GlnCNE0vfJBHedCZgHeXvT
sLf1XbzEqWJ1eSJpfC47h8NDEFX+ScDvPE3hl8cAOYKz1DQW8n343faEcopNzEA0
JJr/qvYzEXUWq/FL7Tp6lyUc4TLTw35N//Pt0FSAZgqgUlsRdYVpWqVvLeYjN4hy
9HcvpfcJY6RJw3nZn/xVwwggKMsrdjKdu2DV1RUGtyJDO9bJLtb6hWWm6bj6B2Hg
e2J3emYG2VVs6qp5EsEKE3x6ayXYBofAVaWHozQu8Zq2vdW/hwbKTe33SQUih6wY
Px1F6gAFvX4VtVMJhaVumc4P8IUMrhVwcNgkIYceGbJ1SckQUEmYDCJS/pfRAhxI
LQwWK8LT2ls+taFC5jQSjTx2CxC+823bS3nabwkUtEIzut7xsTxktUKKIXIm/z04
pF38bOrmGfuajypJr2BSPOHUKHN5woK/4OF78Cg6Iymd8hbpt5a0TlKT4o8eAGek
TmKGp9i1PugMrRsZqR51Rha4zKHeMk3tVGAK6o4LL7x1hsjsyfToL6/ePoIn51p6
72ir5V2fUpM0XgQY4xN40uRUxg7+PblOuKBR1002JkGtxZBmzqwuy7p8mVqO8TcQ
Jew1i8PkkU7LKRMRDdDI
=MqEp
-----END PGP SIGNATURE-----

Reply via email to