From owner-freebsd-bugs@freebsd.org Fri Jul 7 07:29:09 2017 Return-Path: Delivered-To: freebsd-bugs@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 D13B8D9C59C for ; Fri, 7 Jul 2017 07:29:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 B6E756F440 for ; Fri, 7 Jul 2017 07:29:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v677T9YB034783 for ; Fri, 7 Jul 2017 07:29:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220296] MIB interface on amd64 Date: Fri, 07 Jul 2017 07:29:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: s-hrgsh@chic.ocn.ne.jp X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2017 07:29:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220296 --- Comment #4 from s-hrgsh@chic.ocn.ne.jp --- I was wrong. It seems that it was not a problem of NIC. The value of ifSpeed point to Ipkts. #bsnmpwalk | grep ifSeep ; netstat -i -b=20 ifSpeed[1] =3D 9294705 ifSpeed[2] =3D 20206398 ifSpeed[3] =3D 29295 ifSpeed[4] =3D 0 ifSpeed[5] =3D 2268916 ifSpeed[6] =3D 171116 ifSpeed[7] =3D 113610 ifSpeed[8] =3D 0 ifSpeed[9] =3D 14 Name Mtu Network Address Ipkts Ierrs Idrop Ibytes= =20=20=20 Opkts Oerrs Obytes Coll lan0 1500 00:19:99:e4:ac:30 9294705 0 0 1364171021 19523554 0 25105648582 0 lan0 - 192.168.200.0 192.168.200.1 71670 - - 11866792= =20=20 267958 - 113581224 - wan0 1500 00:19:99:e1:0d:ca 20206399 0 0 25712734670 10417400 0 1580979113 0 lo0 16384 lo0 30290 0 0 3687783= =20=20=20 30290 0 3687783 0 lo0 - localhost localhost 49 - - 3505= =20=20=20=20 49 - 3505 - lo0 - fe80::%lo0/64 fe80::1%lo0 0 - - 0= =20=20=20=20 28 - 1568 - lo0 - your-net localhost 30241 - - 3684278= =20=20=20 30241 - 3684278 - pflog 33160 pflog0 0 0 0 0= =20=20=20=20 0 0 0 0 tun0 1500 tun0 171116 0 0 144450348= =20=20 168468 0 15513269 0 tun0 - 172.16.0.0/16 172.16.255.2 8 - - 672= =20=20=20=20 8 - 672 - tun0 - fe80::%tun0/6 fe80::219:99ff:fe 14 - - 784= =20=20=20=20 1 - 76 - tun1 1500 tun1 113611 0 0 11745774= =20=20 304219 0 388647534 0 tun1 - 172.16.0.0/16 172.16.255.2 0 - - 0= =20=20=20 59232 - 71841322 - tun1 - fe80::%tun1/6 fe80::219:99ff:fe 0 - - 0= =20=20=20=20 2 - 172 - tun2 1500 tun2 0 0 0 0= =20=20=20=20 0 0 0 0 tun2 - 172.16.0.0/16 172.16.255.2 0 - - 0= =20=20=20=20 0 - 0 - tun2 - fe80::%tun2/6 fe80::219:99ff:fe 0 - - 0= =20=20=20=20 1 - 96 - ng0 1454 ng0 2268917 0 0 2847307844= =20 1031338 0 154997380 0 ng0 - 180.25.65.148 p338148-ipngn2004 132454 - - 80941280= =20=20 173324 - 81027323 - ng1 1454 ng1 14 0 0 784= =20=20=20=20 16 0 1016 0 ng1 - fe80::%ng1/64 fe80::219:99ff:fe 14 - - 784= =20=20=20=20 2 - 232 - --=20 You are receiving this mail because: You are the assignee for the bug.=