Re: bgpd crashes on long AS-path

2009-02-18 Thread Stuart Henderson
On 2009-02-18, Jules Desforges wrote: > On Monday (16th), I was notified that bgp had crashed on 4 out of the > 8 machines. The bgpd crashed because it was being advertised > a route with a long AS path (> 255). errata and patches have been issued for 4.3/4.4. 010: RELIABILITY FIX: February 18,

Re: bgpd crashes on long AS-path

2009-02-18 Thread Daniel Ouellet
Emilio Perea wrote: On Wed, Feb 18, 2009 at 03:38:11PM -0500, Daniel Ouellet wrote: May be, you should run current and there is yet an other fresh commit on the subject just done a few minutes ago: "clau...@cvs.openbsd.org 2009/02/18 13:30:36" http://marc.info/?l=openbsd-cvs&m=123498913126874

Re: bgpd crashes on long AS-path

2009-02-18 Thread Emilio Perea
On Wed, Feb 18, 2009 at 03:38:11PM -0500, Daniel Ouellet wrote: > May be, you should run current and there is yet an other fresh commit > on the subject just done a few minutes ago: "clau...@cvs.openbsd.org > 2009/02/18 13:30:36" > > http://marc.info/?l=openbsd-cvs&m=123498913126874&w=2 Daniel,

Re: bgpd crashes on long AS-path

2009-02-18 Thread Daniel Ouellet
Jules Desforges wrote: I admin multipe openbgp servers for a handful of companies. On Monday (16th), I was notified that bgp had crashed on 4 out of the 8 machines. The bgpd crashed because it was being advertised a route with a long AS path (> 255). The incident was global, and more informatio

Re: bgpd crashes on long AS-path

2009-02-18 Thread Chris Kuethe
http://marc.info/?l=openbsd-cvs&m=123490079821382&w=2 looks like this might already be fixed. On Wed, Feb 18, 2009 at 12:06 PM, Jules Desforges wrote: > I admin multipe openbgp servers for a handful of companies. > > On Monday (16th), I was notified that bgp had crashed on 4 out of the > 8 machi

bgpd crashes on long AS-path

2009-02-18 Thread Jules Desforges
I admin multipe openbgp servers for a handful of companies. On Monday (16th), I was notified that bgp had crashed on 4 out of the 8 machines. The bgpd crashed because it was being advertised a route with a long AS path (> 255). The incident was global, and more information can be found on the n