On 24 Sep, John W. O'Brien wrote:
> On 9/23/18 17:50, Don Lewis wrote:
>> On 23 Sep, John W. O'Brien wrote:
>>> I'd like to check my understanding and then ask a procedural question.
>>>
>>> FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1].
>>> That changeset, resulting in 11
On 23.09.2018 16:43, John W. O'Brien wrote:
> I'd like to check my understanding and then ask a procedural question.
>
> FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1].
> That changeset, resulting in 11.1R-p13 and 11.2R-p2, included a patch to
> the way IPv6 fragment reass
On 9/23/18 17:50, Don Lewis wrote:
> On 23 Sep, John W. O'Brien wrote:
>> I'd like to check my understanding and then ask a procedural question.
>>
>> FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1].
>> That changeset, resulting in 11.1R-p13 and 11.2R-p2, included a patch to
On 23 Sep, John W. O'Brien wrote:
> I'd like to check my understanding and then ask a procedural question.
>
> FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1].
> That changeset, resulting in 11.1R-p13 and 11.2R-p2, included a patch to
> the way IPv6 fragment reassembly is h
I'd like to check my understanding and then ask a procedural question.
FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1].
That changeset, resulting in 11.1R-p13 and 11.2R-p2, included a patch to
the way IPv6 fragment reassembly is handled [2] that was part of the
merge to rel