Date: Tue, 1 Nov 2016 09:34:24 -0700 From: Pete Wright <pete@nomadlogic.org> To: "Bradley T. Hughes" <bradleythughes@fastmail.fm> Cc: freebsd-cloud@freebsd.org Subject: Re: xn0 systat no egress data? Message-ID: <a9900bca-c64f-6a59-f7bf-ef95e776d059@nomadlogic.org> In-Reply-To: <33AA44AE-3958-4010-9CB3-DCF4D39D3054@fastmail.fm> References: <8be5174c-fcd5-0e5b-921f-5cfc31e99c4f@nomadlogic.org> <33AA44AE-3958-4010-9CB3-DCF4D39D3054@fastmail.fm>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/1/16 6:02 AM, Bradley T. Hughes wrote: > >> On 31 Oct 2016, at 21:44, Pete Wright <pete@nomadlogic.org> wrote: >> >> hey all - this is regarding the following bug i've opened: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213814 >> >> tl;dr version is that on 11.0-RELEASE on EC2 when i invoke "systat -ifstat" the egress data flows for the xn0 device do not update. verified it works as expected on 10.3-RELEASE. tried reading through code but am pretty confused as to how xn0 is created and what code is used to update the sysctl MIBs. > > FWIW, I see the same with the ixv0 device on a c4.large AWS EC2 instance. I also commented on the PR in bugzilla with additional info. > Thanks Bradley - I've also observed this behaviour on the ixv0 interfaces as well. I believe the patch is on the right track - i.e. I suspect the issue lies in the backend Xen device code. Hoping it's a trivial fix for someone more familiar with the plumbing of that code than me. Cheers! -pete -- Pete Wright pete@nomadlogic.org nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a9900bca-c64f-6a59-f7bf-ef95e776d059>