Re: Overflow of RX/TX Bytes on AMD64
On Tue, 10 Feb 2015, Lisi Reisz wrote: Seriously, I can't read ip. I suppose that eventually I shall have to see if if you think ip is bad, try your hand at iw (the one that replaces iwconfig)... -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150217131221.gc8...@khazad-dum.debian.net
Re: Overflow of RX/TX Bytes on AMD64
On Mon, Feb 09, 2015 at 01:02:23PM -0700, Bob Proulx wrote: ip a ip r The counters are not printed with those but since I think those should be accessed using /proc (or /sys) I am not going to contribute to pulling those from a command. But I will. ip --statistics link ip -s l will print the numbers desired. -dsr- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150210142510.gq9...@randomstring.org
Re: Overflow of RX/TX Bytes on AMD64
On Monday 09 February 2015 20:02:23 Bob Proulx wrote: Hey if an old school dog like me can learn to deal with 'ip' instead of 'ifconfig' then you can too. The problem, anyhow for me, is that ifconfig is legible and ip is not. So I shall use ifconfig for as long as almost possible and then have to give up sorting out my nework problems. :-( Seriously, I can't read ip. I suppose that eventually I shall have to see if I can sort it out by copying and pasting into a word processor and seeing what I can make of it by way of sorting out. But as it stands, all I see is a jumbled mess. So an old dog may be able to learn to deal with ip. But for some of us it really is complicated. Even if I manage to render it legible, I've then still got to learn to deal with it. :-( Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201502101457.51347.lisi.re...@gmail.com
Re: Overflow of RX/TX Bytes on AMD64
On Tuesday 10 February 2015 14:57:51 Lisi Reisz wrote: Seriously, I can't read ip. I just had another try, and it has improved. Maybe by the time ifconfig is finally dead or useless, ip will be useful! Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201502101513.02296.lisi.re...@gmail.com
Re: Overflow of RX/TX Bytes on AMD64
John L. Ries wrote: Henrique de Moraes Holschuh wrote: In Linux, you should never use ifconfig for anything... I wouldn't go that far. I think ifconfig is just fine for quickie diagnostics; but I would never use it as a network interface configuration tool if I could help it. The problem is that the Linux kernel has changed internally how it does networking. Some of these changes have been incompatible with the old ifconfig program. That can cause people using only ifconfig to be blind to various kernel network state. Hey if an old school dog like me can learn to deal with 'ip' instead of 'ifconfig' then you can too. Most useful information is provided with these commands: ip addr show ip route show Some people like keyboard golf as reasons to change. Shortest abbreviations: ip a ip r The counters are not printed with those but since I think those should be accessed using /proc (or /sys) I am not going to contribute to pulling those from a command. Bob signature.asc Description: Digital signature
Re: Overflow of RX/TX Bytes on AMD64
On Sat, Feb 07, 2015 at 11:43:48PM -0500, Stephen R Guglielmo wrote: Hi list, I'm running Debian Jessie AMD64. I'm using RRDTool to create graphs of my network activity. Do the byte counters in the `ifconfig` output overflow? I imagine they have to at some point. What's the value at which they overflow? Is it 2^64 bytes? Also, is there a better way to access this information instead of parsing the `ifconfig` output? Maybe somewhere in /proc? Have a look at MRTG, Collectd, Munin, etc. Just check that you're not reinventing a wheel that's already in use quite widely :) Thanks! signature.asc Description: Digital signature
Re: Overflow of RX/TX Bytes on AMD64
On Mon, 9 Feb 2015 13:02:23 -0700 Bob Proulx b...@proulx.com wrote: John L. Ries wrote: Henrique de Moraes Holschuh wrote: In Linux, you should never use ifconfig for anything... I wouldn't go that far. I think ifconfig is just fine for quickie diagnostics; but I would never use it as a network interface configuration tool if I could help it. The problem is that the Linux kernel has changed internally how it does networking. Some of these changes have been incompatible with the old ifconfig program. That can cause people using only ifconfig to be blind to various kernel network state. Hey if an old school dog like me can learn to deal with 'ip' instead of 'ifconfig' then you can too. Most useful information is provided with these commands: ip addr show ip route show The counters are not printed with those but since I think those should be accessed using /proc (or /sys) I am not going to contribute to pulling those from a command. Thanks for the tips! I was modeling my script after another script that used ifconfig. I realize this isn't such a good idea, so I'll look into changing it to use /proc or /sys. pgpsfuEEMazIm.pgp Description: OpenPGP digital signature
Re: Overflow of RX/TX Bytes on AMD64
On Sun, 8 Feb 2015, Henrique de Moraes Holschuh wrote: On Sat, 07 Feb 2015, Stephen R Guglielmo wrote: In Linux, you should never use ifconfig for anything... I wouldn't go that far. I think ifconfig is just fine for quickie diagnostics; but I would never use it as a network interface configuration tool if I could help it. --| John L. Ries | Salford Systems | Phone: (619)543-8880 x107 | or (435)867-8885 | --| -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.OSX.2.00.1502090749420.281@john-l-riess-macbook.local
Re: Overflow of RX/TX Bytes on AMD64
On Sat, 07 Feb 2015, Stephen R Guglielmo wrote: I'm running Debian Jessie AMD64. I'm using RRDTool to create graphs of my network activity. Do the byte counters in the `ifconfig` output overflow? I imagine they have to at some point. What's the value at which they overflow? Is it 2^64 bytes? Yes, they do. SNMP-like counters 101: You *must* *always* handle counter wrap-around, and sudden counter resets. In practice, you also need a saturation filter coupled to a spurious peak supressor for when your sudden reset or counter warp-around detection logic fails, or system time jumps. And depending on how you get to the counters, you also need some persistence and reordering detection logic (e.g. when doing it over SNMP), but I don't think you will have to bother with this. Also, is there a better way to access this information instead of parsing the `ifconfig` output? Maybe somewhere in /proc? In Linux, you should never use ifconfig for anything... in this case, I guess you should take a look on the sources for ethtool command to find out how to proper interface to the kernel to get the full interface counters. But you will likely find something interesting in sysfs as well (not /proc). -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150208131320.ga2...@khazad-dum.debian.net
Overflow of RX/TX Bytes on AMD64
Hi list, I'm running Debian Jessie AMD64. I'm using RRDTool to create graphs of my network activity. Do the byte counters in the `ifconfig` output overflow? I imagine they have to at some point. What's the value at which they overflow? Is it 2^64 bytes? Also, is there a better way to access this information instead of parsing the `ifconfig` output? Maybe somewhere in /proc? Thanks! pgpH023nBarFM.pgp Description: OpenPGP digital signature
Re: Overflow of RX/TX Bytes on AMD64
Stephen R Guglielmo wrote: I'm running Debian Jessie AMD64. I'm using RRDTool to create graphs of my network activity. Fun! Do the byte counters in the `ifconfig` output overflow? Yes. Eventually. I imagine they have to at some point. What's the value at which they overflow? Is it 2^64 bytes? I imagine it depends upon whether you have a 32-bit or 64-bit system. Also, is there a better way to access this information instead of parsing the `ifconfig` output? Maybe somewhere in /proc? Most programs that monitor bandwidth parse /proc/net/dev directly for those counters. $ cat /proc/net/dev Inter-| Receive| Transmit face |bytespackets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo:4091 49000 0 0 0 4091 49000 0 0 0 eth2: 4052835736 5139828000 0 0 0 1869580385 4166842000 0 0 0 eth1: 3123249892 22681508000 0 0 0 33892075524 32382195000 0 0 0 wlan0: 0 0000 0 0 0 576 6000 0 0 0 eth0: 33656882297 37671184 57608000 0 0 0 3163248578 21804028000 1952712 0 0 tun0: 3614860243 4491723000 0 0 0 783124936 3435305000 0 0 0 mon.wlan0: 10501916673 54844796000 0 0 0 0 0000 0 0 0 For documentation on this see the proc(5) man page. man proc And also: https://www.kernel.org/doc/Documentation/filesystems/proc.txt Bob signature.asc Description: Digital signature
