On Wed, Aug 12, 2015 at 03:54:42PM -0700, Sean Bruno wrote:
> On 08/12/15 15:43, Glen Barber wrote:
> > On Wed, Aug 12, 2015 at 03:41:21PM -0700, Sean Bruno wrote:
> >> On 08/12/15 15:15, Glen Barber wrote:
> >>> On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote:
> I was reading through
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/12/15 15:43, Glen Barber wrote:
> On Wed, Aug 12, 2015 at 03:41:21PM -0700, Sean Bruno wrote:
>> On 08/12/15 15:15, Glen Barber wrote:
>>> On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote:
I was reading through the Release notes, an
On Wed, Aug 12, 2015 at 03:41:21PM -0700, Sean Bruno wrote:
> On 08/12/15 15:15, Glen Barber wrote:
> > On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote:
> >> I was reading through the Release notes, and decided to enable
> >> net.inet.tcp.pmtud_blackhole_detection in my test environment. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/12/15 15:15, Glen Barber wrote:
> On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote:
>> I was reading through the Release notes, and decided to enable
>> net.inet.tcp.pmtud_blackhole_detection in my test environment. It
>> appears that t
On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote:
> I was reading through the Release notes, and decided to enable
> net.inet.tcp.pmtud_blackhole_detection in my test environment. It appears
> that the monitoring tunable net.inet.tcp.pmtud_blackhole_min_activated is
> incorrectly listed. Usi
I was reading through the Release notes, and decided to enable
net.inet.tcp.pmtud_blackhole_detection in my test environment. It
appears that the monitoring tunable
net.inet.tcp.pmtud_blackhole_min_activated is incorrectly listed. Using
sysctl -a | grep net.inet.tcp.pmtud, doesn't show it as a
