Re: [j-nsp] Juniper BGP invalid attributes

2009-03-18 Thread Richard A Steenbergen
On Wed, Mar 18, 2009 at 01:49:52PM -0400, Bryan Socha wrote: > Does anyone know what Junos revisions for the M series will fix this? > We ended up just filtering out the offending announcement but would > prefer to update and avoid future ones. Richard's list looks like all E > series releases. W

Re: [j-nsp] Juniper BGP invalid attributes

2009-03-18 Thread Bryan Socha
Does anyone know what Junos revisions for the M series will fix this? We ended up just filtering out the offending announcement but would prefer to update and avoid future ones. Richard's list looks like all E series releases. Bryan Socha ___ juniper-

Re: [j-nsp] Juniper BGP invalid attributes

2009-03-18 Thread Barry Greene
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > 1) Routers shouldn't be leaking confederation information > into AS4_PATH. > This is the issue that Juniper covers under PSN-2009-01-200, > and all code built after 2009-01-26 appears to be fixed in > this regard. This is the same issue that

Re: [j-nsp] Juniper BGP invalid attributes

2009-03-18 Thread Richard A Steenbergen
On Tue, Mar 17, 2009 at 08:46:06PM -0700, Andy Vance wrote: > Richard, > > Appears these are the releases that it has been fixed in. > > 8-1-4p0-4, 8-2-4p0-7, 9-0-2p0-1, 9-1-2p0-1, 9-2-1p0-1, 9-3-0p0-1, 10-0-0 Now that things have calmed down, I've got a few more updates on this incident and som

Re: [j-nsp] Juniper BGP invalid attributes

2009-03-18 Thread Andy Vance
: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Richard A Steenbergen Sent: Tuesday, March 17, 2009 6:23 PM To: Richard A Steenbergen Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Juniper BGP invalid attributes On Tue, Mar 17, 2009 at 07:54:37PM -0500

Re: [j-nsp] Juniper BGP invalid attributes

2009-03-17 Thread Richard A Steenbergen
On Tue, Mar 17, 2009 at 08:23:13PM -0500, Richard A Steenbergen wrote: > Ok got some packet captures of the invalid update, it looks like > 193.5.68.0/23 was being announced and propagated globally with the > leaked confederations in AS4_PATH issue described in PSN-2009-01-200. Actually it looks l

Re: [j-nsp] Juniper BGP invalid attributes

2009-03-17 Thread Richard A Steenbergen
On Tue, Mar 17, 2009 at 07:54:37PM -0500, Richard A Steenbergen wrote: > Who else just noticed Juniper bgp sessions all over the place flapping > with: > > code 3 (Update Message Error) subcode 1 (invalid attribute list) > code 3 (Update Message Error) subcode 11 (AS path attribute problem) > Rec

[j-nsp] Juniper BGP invalid attributes

2009-03-17 Thread Richard A Steenbergen
Who else just noticed Juniper bgp sessions all over the place flapping with: code 3 (Update Message Error) subcode 1 (invalid attribute list) code 3 (Update Message Error) subcode 11 (AS path attribute problem) Received BAD update for family inet-unicast(1), prefix 193.5.68.0/23 etc? -- Richar