Date: Fri, 02 Aug 2019 16:02:16 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 234754] FreeBSD 12.0 ena Network Driver on AWS EC2 Packet Loss Message-ID: <bug-234754-27103-MMV5PFE8On@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234754-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-234754-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234754 Derek VerLee <derekverlee@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |derekverlee@gmail.com --- Comment #13 from Derek VerLee <derekverlee@gmail.com> --- I'll share my experience, as I think might be a different manifestation of = this bug. I'm running a freebsd 12.0 release instance configured as a VPN route= r in ec2, with the ENI registered in the subnet's route table, and "source/dest check" disabled. Gateway is enabled in rc.conf, as well as pf, with some N= AT and filtering rules. Pinging the vpn server's local address from another instance in the subnet (Linux) works, pinging the vpn client from the vpn server works, but pinging the client from the Linux host experienced >99% packet loss, with one reply arriving in many thousands. TCP dump showed the echo request getting all the way to the client, and the reply apparently emitted on ena0, but never arriving at the linux interface. This was the same with a t3a.small and t3.small instance in us-east-1. Switching the instance type to t2.small (xn driver) solved the issue. FreeBSD 12.0-RELEASE-amd64 (ami-03b0f822e17669866), us-east-2 If I get a chance to try an instance with STABLE I will post back. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234754-27103-MMV5PFE8On>