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