From owner-freebsd-cloud@freebsd.org Wed Jan 11 19:33:59 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 DAE26CAB0DE for ; Wed, 11 Jan 2017 19:33:59 +0000 (UTC) (envelope-from snakedoctr@gmail.com) Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3C091318 for ; Wed, 11 Jan 2017 19:33:59 +0000 (UTC) (envelope-from snakedoctr@gmail.com) Received: by mail-oi0-x234.google.com with SMTP id 3so598818455oih.1 for ; Wed, 11 Jan 2017 11:33:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=i/hehWrZc8cfuAcV22ZJkT61JGsiOnFaRw58YZBOe98=; b=pbUIjAlLmd6eZAu1XCcJLFe0Kt2pLmCseKWziu2Bu7Qm+bYM+E8Z6idzMjeFLzhN/N u7V7UUjSYEQcR0NMqT3453ZSokIvqJ/9egACuxTfOYTv9B6Bfda1Gyt9seBD25kIOrsP LSGHRmSRyRQM8wELK2YgIj1ruUOpoOwcjHzCLrzWBl9oIIkkmnoK7VcfgZWRuteg8vRl ADANk7XjVHc4rGvAMtcymZRUyV604CAgm013J4MlcErFDgwE72U0AbOuwFdnMGGMnbRR pyq4/H2h5bPmX+mjEOHXWPmte7R/8JLJm3cn4ijNBP0ykWvMxp5jEIVzAZESpuZrnq4f WIMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=i/hehWrZc8cfuAcV22ZJkT61JGsiOnFaRw58YZBOe98=; b=RsLSCbFsmVhZSlxpmrix6JWavwgS4GxIElVAQDfGDtU2n/OtlqxTp62wBNiCkJPcXu 4RtKFy+5FLwvAbXIVe2gpZvuAfYdKTEfg+D5QZoeCY8UstFKgd9w/TkHkb+VFoCu2Gnn oiNX1h7j40HRjzIPQBLvVYXF/r98nRcaO6aNNhhUv0Z26lWk7cjrrolCXK1ypTFvj5IG Oot5ZW+3zZSLeZbVGBCbSX6h4+P5ZhgjtSCaJtxhR5uZgVHAVDXAhquLlr+qeHnn+xs8 WoC5QeNo4DiPtkaNsny2qrnkGODYoWYnY4eLnHAR8k37EK+yvjuLI9jD7WwC6+JfwvO2 pvOQ== X-Gm-Message-State: AIkVDXI0z4P8sIsWQnOcYb3C2kjxQavAtykPLuLfcJ9y91Yb0wKWnBsmU6975FuNZ1fdwb4Sff1cOb2UjLYcIQ== X-Received: by 10.202.186.7 with SMTP id k7mr4580883oif.206.1484163238747; Wed, 11 Jan 2017 11:33:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.71.156 with HTTP; Wed, 11 Jan 2017 11:33:58 -0800 (PST) From: Jason Date: Wed, 11 Jan 2017 14:33:58 -0500 Message-ID: Subject: xn0 interface "Obytes" not populating To: freebsd-cloud@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 19:34:00 -0000 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' would collect its details. After running 'netstat -I xn0 -bn', I notice that "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 having difficulty is running on AWS, so is on Xen. Any insight into how to fix this so "Obytes" populates for "Link#2"? Thanks! From owner-freebsd-cloud@freebsd.org Wed Jan 11 19:35:14 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 F339FCAB117 for ; Wed, 11 Jan 2017 19:35:14 +0000 (UTC) (envelope-from snakedoctr@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9BBE1347 for ; Wed, 11 Jan 2017 19:35:14 +0000 (UTC) (envelope-from snakedoctr@gmail.com) Received: by mail-oi0-x22d.google.com with SMTP id w204so101623744oiw.0 for ; Wed, 11 Jan 2017 11:35:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=lN7itUh8bIXrCyEgMvRPrYfR0wBE/IR0LUB8fC+QIRY=; b=bsFu8FwR+4tEhyc8NjS8s2JtEmKrBru1aZ7EuMr/imYh7OZ6mOvjDeMY5MWMeepj4p FMSjBSudhm1UzhohIlk4LqnU1xoY3o46V2V4ntWmYfj/5VGhYCz7cDTVGMRkuyh6W3xT LknNeHd/uZOIr2lAPW3ov+YjLmctVQKq9tf93RvxTGNrPNDWxy8YrM1jSiNUhDPatChg UuYX8I9Az+Tt7TOCDCGTDJb5ZG2vmP49iNFokaOAxKFCynawe3kyePnM3U9dI4UarvoB sOYzBXYRf/JS9EY+8wemcWasocdbZxnTWk7Lxe5mykAOCFpVzemQnmSKlSYbjWJGKs94 eMwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=lN7itUh8bIXrCyEgMvRPrYfR0wBE/IR0LUB8fC+QIRY=; b=jTHuD59pvNDEXfD4iES5sBAIe/WDvVEf4Rr3yF10s7CjEW7BkjlLAbrncpRlcv2aYf LTVn11HgWcxinzGJkIaWgzahHyTBIG0K/dSgOZHiOvs2tQ1pj5lfRKZiYDszqG9Zn5w9 Z5X7vqRtUd1GaDC6lnkx1Fucy4z+AEXc7RKEUcWQ9jCwv+GyjTKBYC19O8F4HDB2oBSY spLQGVAX0VH3SsPb+NYwfgl0rLh55Fcu0L11FVLpZJctrcDMT7ggSzf3IHuB98qvtt8U tHIhHGTk714wR39bJ/tHxHaJ6Ok5yYVvdV6iSgH+FhD1Gdp3DyATboMJ5OpObwUy52gB AbaA== X-Gm-Message-State: AIkVDXJXpn0ieeqbqaBWlUHWQI/ps6KW16jKuuWkMo/m5qz3VfSffXy6RIDp7M4Ce0Kan+ACsndc7K6vw1iCDw== X-Received: by 10.157.46.67 with SMTP id c3mr4745723otd.163.1484163314084; Wed, 11 Jan 2017 11:35:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.71.156 with HTTP; Wed, 11 Jan 2017 11:35:13 -0800 (PST) In-Reply-To: References: From: Jason Date: Wed, 11 Jan 2017 14:35:13 -0500 Message-ID: Subject: Re: xn0 interface "Obytes" not populating To: freebsd-cloud@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 19:35:15 -0000 Sorry, I meant to say that the working machine uses the em interface (not fxp like I mentioned). On Wed, Jan 11, 2017 at 2:33 PM, 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' would > collect its details. After running 'netstat -I xn0 -bn', I notice that > "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 <(225)%20811-3267> 21130240 - 3518207522 <(351)%20820-7522> > - > > 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 having > difficulty is running on AWS, so is on Xen. > > Any insight into how to fix this so "Obytes" populates for "Link#2"? > > Thanks! > From owner-freebsd-cloud@freebsd.org Wed Jan 11 19:55:25 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 E40F7CABD2A for ; Wed, 11 Jan 2017 19:55:25 +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 AA9AC1D94 for ; Wed, 11 Jan 2017 19:55:25 +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 9CEE513240 for ; Wed, 11 Jan 2017 19:55:18 +0000 (UTC) Subject: Re: xn0 interface "Obytes" not populating To: freebsd-cloud@freebsd.org References: From: Allan Jude Message-ID: <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org> Date: Wed, 11 Jan 2017 14:55:14 -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="HXQfs4T8GJc4umT5j0pq29bvaa4u7WC8G" 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 19:55:26 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HXQfs4T8GJc4umT5j0pq29bvaa4u7WC8G Content-Type: multipart/mixed; boundary="rlCIghEXNuaQB4c1hhlmANKnx0jp6NGVJ"; protected-headers="v1" From: Allan Jude To: freebsd-cloud@freebsd.org Message-ID: <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org> Subject: Re: xn0 interface "Obytes" not populating References: In-Reply-To: --rlCIghEXNuaQB4c1hhlmANKnx0jp6NGVJ Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017-01-11 14:33, Jason wrote: > Hi, > I installed vnstat, which is a bandwidth monitoring app. I noticed t= hat > for some reason its TX bytes were 0, but the RX bytes were being tracke= d 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' woul= d > collect its details. After running 'netstat -I xn0 -bn', I notice that= > "Obytes" for "" is 0, which may be the problem. However, the > "Obytes" for the actual IP address seems to be working: >=20 > # netstat -I xn0 -bn > Name Mtu Network Address Ipkts Ierrs Idrop > Ibytes Opkts Oerrs Obytes Coll > xn0 1500 22659117 0 0 257919= 4762 > 21221967 0 0 0 > xn0 - 10.0.10.0/24 10.0.10.40 22567359 - - 225811= 3267 > 21130240 - 3518207522 - >=20 > On a different machine that command works fine. It is running BSD 11 a= s > well, but it's not using the xn driver -- it uses the fxp driver. It's= > output is: >=20 > # 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 - >=20 > I'm running FreeBSD 11 on both instances, except the one that's having > difficulty is running on AWS, so is on Xen. >=20 > Any insight into how to fix this so "Obytes" populates for "Link#2"? >=20 > 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.org= " >=20 There is a fix for this here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213439 --=20 Allan Jude --rlCIghEXNuaQB4c1hhlmANKnx0jp6NGVJ-- --HXQfs4T8GJc4umT5j0pq29bvaa4u7WC8G 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) iQIcBAEBAgAGBQJYdo2lAAoJEBmVNT4SmAt+XGgP/1pfV5SZ96EsekvKS0p0FFJk YJP2OnphA+cvxairzqehV5NpjOKQ619EplF5KXmHQGUnZgqp7CIz2mWbPQjMHsCr 8tuWZ+Wmsx/zvy3GsO0+5wGf5LGH0Z8hE7yxNQudR3TMVKOARhTPD6u7FtmPAp+o m10p2SLjQKOjeF0Qmhutvxi2HmZCjMbqYchbMx4ZoncIA0EykoC+UMQJEeiUHSDi gY0/hBd/AuGe+IbXuWTj+830q/H/0ysyeKXgQgdkSb/3OUii00eD5SmxENiMjf5Y 0SpTinh+Jh1rABMNovGjhRO9TCK8XcASz2lCEaKFc4PMlqb3TZaswO2J4AI7YGjV CYEMZjMQxpICy7surisOU8qP3ItqDhwUWRS0zckNqixVsq9qtsxvrQg4W/nE4l6Y Z9K11BrvmZfwC1LBLRXA1KX+wFghbP+rvZLAzJ5ktmtjk3XrtQvTHtIyOkmQV/LD WGUjxtyrHTmxztKzHBeJ0LPYy6YDLh6hpBh1gReilX6GtmPjgIsei1HAt8SM+Tzr tkB2YyNJr/fr2P3DRlT3C95o9Yl2xDX55Wg8OuLGo8ZvWF44OPtVMNE4LJwmFLMk WsDoMygRDbp2Fvl46vXRc4iCJIMPkFSgNqp/WVu3Vi0kjVO0Jz+DMEcE/S/DWa1D q6vi+v7fClYFWBZB65kH =ox9e -----END PGP SIGNATURE----- --HXQfs4T8GJc4umT5j0pq29bvaa4u7WC8G-- From owner-freebsd-cloud@freebsd.org Wed Jan 11 20:01:30 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 412D5CAB215 for ; Wed, 11 Jan 2017 20:01:30 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (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 11C701A8E for ; Wed, 11 Jan 2017 20:01:29 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from la-dgt-31327.usa.tribune.com (nat-192-187-90-113.nat.tribpub.com [192.187.90.113]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 1b0e2f7c TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Wed, 11 Jan 2017 12:01:28 -0800 (PST) Subject: Re: xn0 interface "Obytes" not populating To: freebsd-cloud@freebsd.org References: <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org> From: Pete Wright Message-ID: Date: Wed, 11 Jan 2017 12:01:28 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 20:01:30 -0000 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' would >> collect its details. After running 'netstat -I xn0 -bn', I notice that >> "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 having >> 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.org" >> > > There is a fix for this here: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213439 Oh great - do you think this will also address this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213814 If I have time this week I'll try to verify this as well and will close 213814 if it works. Cheers, -pete -- Pete Wright pete@nomadlogic.org nomadlogicLA 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-- From owner-freebsd-cloud@freebsd.org Wed Jan 11 21:29:51 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 67CA5CAAD55 for ; Wed, 11 Jan 2017 21:29:51 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (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 414AD1B9B for ; Wed, 11 Jan 2017 21:29:50 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from la-dgt-31327.usa.tribune.com (nat-192-187-90-113.nat.tribpub.com [192.187.90.113]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 5d62dbc2 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Wed, 11 Jan 2017 13:29:50 -0800 (PST) Subject: Re: xn0 interface "Obytes" not populating To: freebsd-cloud@freebsd.org References: <2425be22-3b78-0a96-a828-6e6c7e7eb087@freebsd.org> <9f002dc8-b679-d912-fc15-46aa50f7a722@freebsd.org> From: Pete Wright Message-ID: <7ec68ebb-725b-0a8c-2ee3-5a85e71dcbcf@nomadlogic.org> Date: Wed, 11 Jan 2017 13:29:49 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <9f002dc8-b679-d912-fc15-46aa50f7a722@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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:29:51 -0000 On 1/11/17 1:15 PM, Allan Jude wrote: > On 2017-01-11 15:01, Pete Wright wrote: >> >> >> 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' would >>>> collect its details. After running 'netstat -I xn0 -bn', I notice that >>>> "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 having >>>> 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.org" >>>> >>> >>> There is a fix for this here: >>> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213439 >> >> Oh great - do you think this will also address this PR: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213814 >> >> If I have time this week I'll try to verify this as well and will close >> 213814 if it works. >> >> Cheers, >> -pete >> > > 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. > ah right of course, thanks for the clarification on this Allan! -pete -- Pete Wright pete@nomadlogic.org nomadlogicLA