I noticed earlier today that our PRsearch application isn't showing 10.4 fixes (sometimes? always?) in the detailed view, which is weird. We are looking into that. I'll post a note back here when I hear more on that.
701928 was a fix to a regression, the regression only "escaped" in 10.4R8. So even though it is "fixed" in 11.4R2, the same regression was introduced after 11.4R1, so there was never any customer vulnerability in 11.4. Same story with 12.1R1. Thanks, Jim -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Clarke Morledge Sent: Friday, June 01, 2012 1:54 PM To: [email protected] Subject: Re: [j-nsp] Junos 10.4R8 on MX (PR 701928) I am going back to an old thread regarding PR 701928 being introduced in 10.4R8 back in January or before. The PR description summary is "DPC, ADPC, MS-DPC, MX-FPC and MX-DPC may restart with backtrace in ia_wpkt_next() routine," yet there is a workaround. Now that 10.4R10 is out, I am a little puzzled to see in the PR search notes, http://kb.juniper.net/KB22825, that this is resolved in 11.4R2 and 12.1R1. But nothing is mentioned about a fix in a 10.4x release. I would have thought that this would have been fixed in a 10.4x release by now, thus making the workaround unnecessary. Does anyone know if you still have to implement the workaround in 10.4R10? Clarke Morledge College of William and Mary Information Technology - Network Engineering Jones Hall (Room 18) Williamsburg VA 23187 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
