From owner-freebsd-cloud@freebsd.org Wed Jan 11 21:15:28 2017 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1D5BCAA70D for ; Wed, 11 Jan 2017 21:15:28 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7FAC611F7 for ; Wed, 11 Jan 2017 21:15:28 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 848341343B for ; Wed, 11 Jan 2017 21:15:26 +0000 (UTC) Subject: Re: xn0 interface "Obytes" not populating To: freebsd-cloud@freebsd.org References: <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org> From: Allan Jude Message-ID: <9f002dc8-b679-d912-fc15-46aa50f7a722@freebsd.org> Date: Wed, 11 Jan 2017 16:15:22 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iAvM7mVv96L7GEOVHsfDArC6sENDo66cs" X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 21:15:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --iAvM7mVv96L7GEOVHsfDArC6sENDo66cs Content-Type: multipart/mixed; boundary="WCX3cS7kC3PFH82S2slKksGDA0oGNKXwo"; protected-headers="v1" From: Allan Jude To: freebsd-cloud@freebsd.org Message-ID: <9f002dc8-b679-d912-fc15-46aa50f7a722@freebsd.org> Subject: Re: xn0 interface "Obytes" not populating References: <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org> In-Reply-To: --WCX3cS7kC3PFH82S2slKksGDA0oGNKXwo Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017-01-11 15:01, Pete Wright wrote: >=20 >=20 > On 1/11/17 11:55 AM, Allan Jude wrote: >> On 2017-01-11 14:33, Jason wrote: >>> Hi, >>> I installed vnstat, which is a bandwidth monitoring app. I noticed= >>> that >>> for some reason its TX bytes were 0, but the RX bytes were being >>> tracked as >>> expected. I don't know how vnstat is collecting its metrics every 5 >>> minutes, but I'm guessing it's similar to how 'netstat -I xn0 -bn' wo= uld >>> collect its details. After running 'netstat -I xn0 -bn', I notice th= at >>> "Obytes" for "" is 0, which may be the problem. However, the= >>> "Obytes" for the actual IP address seems to be working: >>> >>> # netstat -I xn0 -bn >>> Name Mtu Network Address Ipkts Ierrs Idrop >>> Ibytes Opkts Oerrs Obytes Coll >>> xn0 1500 22659117 0 0 >>> 2579194762 >>> 21221967 0 0 0 >>> xn0 - 10.0.10.0/24 10.0.10.40 22567359 - - >>> 2258113267 >>> 21130240 - 3518207522 - >>> >>> On a different machine that command works fine. It is running BSD 11= as >>> well, but it's not using the xn driver -- it uses the fxp driver. It= 's >>> output is: >>> >>> # netstat -I xn0 -bn >>> Name Mtu Network Address Ipkts Ierrs Idrop >>> Ibytes Opkts Oerrs Obytes Coll >>> em0 1500 1507204306 0 0 >>> 1567750969110 100389817 0 80619546746 0 >>> em0 - 192.168.10.0/ 192.168.10.10 1506281038 - - >>> 1548639235291 100283723 - 79211140098 - >>> >>> I'm running FreeBSD 11 on both instances, except the one that's havin= g >>> difficulty is running on AWS, so is on Xen. >>> >>> Any insight into how to fix this so "Obytes" populates for "Link#2"? >>> >>> Thanks! >>> _______________________________________________ >>> freebsd-cloud@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-cloud >>> To unsubscribe, send any mail to "freebsd-cloud-unsubscribe@freebsd.o= rg" >>> >> >> There is a fix for this here: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213439 >=20 > Oh great - do you think this will also address this PR: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213814 >=20 > If I have time this week I'll try to verify this as well and will close= > 213814 if it works. >=20 > Cheers, > -pete >=20 No, it does not fix the ixv(4) problem. It was a bug specifically in xn(4), which is the paravirtual nic. ixv is an SR-IOV passthru device. So it is a different problem. However, head just got an all new framework for the intel NIC drivers, I am wondering if THAT fixes this issue, likely by coincidence. --=20 Allan Jude --WCX3cS7kC3PFH82S2slKksGDA0oGNKXwo-- --iAvM7mVv96L7GEOVHsfDArC6sENDo66cs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJYdqBtAAoJEBmVNT4SmAt+/0cP/2jRIH292i1EF03EfDAzY+aL Uf/oSEGQnxBHbE3GGHYdfd/m1PYjoc/z68Y6kR4dcKOaqT+ai8SEPkSFAr1mzFQ2 NiuBNUk5iiiSuatNV1xaK3fE5bNw+QhzSX4WzzwHuUOBcltbyBSnJzzuGoJr256r byXDHBPvLNvXKSm91Mp5r7K5bLnS4xdwPnqP361F30mBmsJ5Azj0JaqDNlVM4H2C NVDZXiDilv3N+zFbPS72uEu/SrquRjy5y09DX9wjy5/J/OSBvQkLMDORTSzLPUdT /nREXW8KHbHQ+QyMchzIUlxuVkgn+KjeVXAJ8rUSCygpjJnmQLDcomh0IP5u+HxX 13f9I/sj7WdzMMYZvweFPgvj5W0Locd1HdhvtGm9vThHiRrhw5dq3bCcKpyIsIs7 WAFQjemyO9lF5Yk+bntGpAUhctfANiKqo1pImtilWBZBTkrCUx+X5DzE4DDvFQkw bfnukd2TajwHUSxQUOGit3DZMofHNxNVgzE1Jgk8fftabdjg8tTGKjgB083oN7A2 Ya0WQQCNatR5c2d3I4/yKFzVAbFGvwj7skJ3DL0TyQD86rrlOiYbR51HgrFtJtWH aslZibF+xNBdiF557QYa4detbYzj+VLzbZijzG+YhQPpTKTY0iA7Y85Egr0A8GNr zc4aKYjbqHiiZN/UWZlj =adk/ -----END PGP SIGNATURE----- --iAvM7mVv96L7GEOVHsfDArC6sENDo66cs--