Excellent, will give it a try on a box that I never have this problem on. Will let you know of the symptoms are the same when I trigger it.
Best, Reshad On 28 March 2018 12:32:44 AM IST, Kristof Provost <kris...@sigsegv.be> wrote: >On 27 Mar 2018, at 20:59, Reshad Patuck wrote: >> The current value of 'net.link.epair.netisr_maxqlen' is 2100, I will >> make it 210. >> Will this require a reboot? or can I just change the sysctl and >reload >> the epair module? >> >You shouldn’t need to reboot or reload the epair module. When I set it >to 2 on my box it pretty much immediately lost connectivity over the >epair interfaces. > >I’d expect you to get hit by the bug relatively quickly now, so be >aware of that. > >Regards, >Kristof _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
