On Fri, Jan 30, 2009 at 03:14:00PM +0100, Arnoud Vermeer wrote: > Hi Tico, > > The problem is limited to quagga it seems. I have setup a juniper and > cisco session and they both come up fine. Only the quagga routers seem > to hang on the empty update. >
... > The quagga log shows the following: > > 2009/01/30 15:05:53 BGP: 2001:db8:1::a500:6777:1 [Event] Connect start > to 2001:db8:1::a500:6777:1 fd 13 > 2009/01/30 15:05:53 BGP: %ADJCHANGE: neighbor 2001:db8:1::a500:6777:1 Up > 2009/01/30 15:05:53 BGP: 2001:db8:1::a500:6777:1 rcvd UPDATE w/ attr: , > origin i, mp_nexthop 2001:db8:1::a506:5503:1, community 6777:6777, path > 65503 > 2009/01/30 15:05:53 BGP: 2001:db8:1::a500:6777:1 rcvd 2001:db8:10::/64 > 2009/01/30 15:05:53 BGP: 2001:db8:1::a500:6777:1 rcvd 2001:db8:11::/64 > 2009/01/30 15:05:53 BGP: 2001:db8:1::a500:6777:1 rcvd 2001:db8:12::/64 > 2009/01/30 15:05:53 BGP: 2001:db8:1::a500:6777:1 rcvd UPDATE w/ attr: , > origin i, mp_nexthop 2001:db8:1::a506:5503:1, community 6777:6777, path > 65504 65503 65502 > 2009/01/30 15:05:53 BGP: 2001:db8:1::a500:6777:1 rcvd UPDATE about > 2001:db8:97::/64 -- DENIED due to: as-path contains our own AS; Hmm. That's a funky reason to close the connection. IIRC the RFC does not enforce the sender to ensure that the path is considered loop-free on the client. > 2009/01/30 15:05:54 BGP: %NOTIFICATION: sent to neighbor > 2001:db8:1::a500:6777:1 6/4 (Cease/Administratively Reset) 0 bytes > 2009/01/30 15:05:54 BGP: %ADJCHANGE: neighbor 2001:db8:1::a500:6777:1 > Down User reset > 2009/01/30 15:05:54 BGP: 2001:db8:1::a500:6777:1 [Event] Connect start > to 2001:db8:1::a500:6777:1 fd 13 > 2009/01/30 15:05:54 BGP: 2001:db8:1::a500:6777:1 [Event] BGP connection > closed fd 13 > No idea why quagga is so upset by getting a as-path that contains the own IP... -- :wq Claudio
