https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209682
--- Comment #10 from Hans Petter Selasky ---
Does applying the fix at:
https://reviews.freebsd.org/D4605
resolve those IPv6 based panics?
It might be you're just lucky that the IPv4 arptimer is not panicing.
--HPS
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225438
--- Comment #2 from Dave Baukus ---
Admittedly, the test case listed is specious, but the following a bit less so:
while :
do
setfib 1 arp -d $ADDR &
setfib 1 ping -c 4 $ADDR &
setfib 1 arp -d $ADDR &
/etc/r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209682
--- Comment #9 from Dave Baukus ---
(In reply to Hans Petter Selasky from comment #8)
I've tried your test and more in an infinite loop; all I get is various crashes
in the IPv6 code (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225438
On Wed, Jan 24, 2018 at 3:16 AM, Andrey V. Elsukov
wrote:
> On 24.01.2018 02:26, Andrey V. Elsukov wrote:
> > I think it is correct behavior if you try to forward to loopback
> > address. In case when you listen on the LLA and fwd to this LLA there is
> > seems the bug.
> >
> > # ipfw add fwd fe8
A few years back a working group announced their work on MPTCP for
FreeBSD, http://caia.swin.edu.au/newtcp/mptcp/. Around that time also a
QR mentioned the project,
https://www.freebsd.org/news/status/report-2013-01-2013-03.html#Multipath-TCP-(MPTCP)-for-FreeBSD
Since then all of this seems to
Hi,
Hope this email finds you well.
Would you be interested in a list of key decision makers from Defence,
Safety and Security Industry? For your marketing activities and business
development.
Target Audience: Law Enforcement Professionals, Military Officers,
Government Officials, Emerg
