Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jan 2017 16:15:22 -0500
From:      Allan Jude <allanjude@freebsd.org>
To:        freebsd-cloud@freebsd.org
Subject:   Re: xn0 interface "Obytes" not populating
Message-ID:  <9f002dc8-b679-d912-fc15-46aa50f7a722@freebsd.org>
In-Reply-To: <b29e9559-5258-840a-ee6d-4096f69fa144@nomadlogic.org>
References:  <CAEJmKMddjNSC2Kgw1B_=Lg__m6DYvWt-7_ffsK9r-9uteBNi=Q@mail.gmail.com> <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org> <b29e9559-5258-840a-ee6d-4096f69fa144@nomadlogic.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--iAvM7mVv96L7GEOVHsfDArC6sENDo66cs
Content-Type: multipart/mixed; boundary="WCX3cS7kC3PFH82S2slKksGDA0oGNKXwo";
 protected-headers="v1"
From: Allan Jude <allanjude@freebsd.org>
To: freebsd-cloud@freebsd.org
Message-ID: <9f002dc8-b679-d912-fc15-46aa50f7a722@freebsd.org>
Subject: Re: xn0 interface "Obytes" not populating
References: <CAEJmKMddjNSC2Kgw1B_=Lg__m6DYvWt-7_ffsK9r-9uteBNi=Q@mail.gmail.com>
 <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org>
 <b29e9559-5258-840a-ee6d-4096f69fa144@nomadlogic.org>
In-Reply-To: <b29e9559-5258-840a-ee6d-4096f69fa144@nomadlogic.org>

--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 "<Link#2>" 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 <Link#2>      <REDACTED>        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 <Link#1>      <REDACTED>        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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9f002dc8-b679-d912-fc15-46aa50f7a722>