Claudio Jeker schrieb: I updated both system to the latest snapshot. The problem still exists.
> Could be you're hitting a similar bug as Jon Morby even though your system > does not fatal at the same place. Hm, how can I help to isolate the bug? Tell me, what I can do to support you! May 1 19:00:26 pinky bgpd[25852]: neighbor 194.9.86.8 (iBGP AS35548): state change Idle -> Connect, reason: Start May 1 19:00:26 pinky bgpd[25852]: neighbor 194.9.86.8 (iBGP AS35548): state change Connect -> OpenSent, reason: Connection opened May 1 19:00:26 pinky bgpd[25852]: neighbor 194.9.86.8 (iBGP AS35548): state change OpenSent -> OpenConfirm, reason: OPEN message received May 1 19:00:26 pinky bgpd[25852]: neighbor 194.9.86.8 (iBGP AS35548): state change OpenConfirm -> Established, reason: KEEPALIVE message received May 1 19:00:29 pinky bgpd[10682]: nexthop 194.9.86.8 now valid: via 194.9.86.1 May 1 19:00:30 pinky bgpd[25852]: neighbor 194.9.86.8 (iBGP AS35548): received notification: error in UPDATE message, attribute length wrong May 1 19:00:30 pinky bgpd[25852]: neighbor 194.9.86.8 (iBGP AS35548): state change Established -> Idle, reason: NOTIFICATION received May 1 19:01:00 pinky bgpd[25852]: Connection attempt from neighbor 194.9.86.8 (iBGP AS35548) while session is in state Idle Regards, Falk
