https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274007
Mark Linimon changed:
What|Removed |Added
Keywords||vendor
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274007
--- Comment #4 from Shawn Anastasio ---
On further inspection, it appears the failure I observed is caused by an
unrelated bug in the virtio network driver rather than IPSec
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268699).
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274007
--- Comment #3 from Shawn Anastasio ---
I am able to reproduce this on -CURRENT on powerpc64le. With a debug kernel
build, I'm hitting the following assertion when flooding an ipsec link between
two VMs using ipsec3 with the net.inet.ipsec.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274007
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@gmail.com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274007
--- Comment #2 from Timothy Pearson ---
(In reply to Zhenlei Huang from comment #1)
What would you like to know in particular?
The hardware is fairly straightforward on both test boxes, we are using Opteron
CPUs with igb Ethernet cards an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274007
--- Comment #1 from Zhenlei Huang ---
May you please share your setup briefly?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274007
Mark Linimon changed:
What|Removed |Added
Keywords||regression
Assignee|b...@
