Re: Inconsistent stats for networking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Are you doing some NAT (Masquerading) ?

Check out source code sometimes packets are counted twice because of
passing an interface like ip-chains or other.

hope this helps.

alx


On Fri, 7 Dec 2001, Kenneth Stephen wrote:

> Hi,
>
> 	Here is the results of 'ifconfig > file; netstat -s >> file' on my
> system :
>
> eth0      Link encap:Ethernet  HWaddr 00:20:78:05:EA:0B
>           inet addr:X.Y.54.140  Bcast:X.Y.54.191  Mask:255.255.255.192
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:9813111 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11709191 errors:1 dropped:0 overruns:1 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:15 Base address:0xa000
>
> eth1      Link encap:Ethernet  HWaddr 00:03:6D:1C:E3:3F
>           inet addr:X.Y.19.1  Bcast:X.Y.19.31  Mask:255.255.255.224
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:696141 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:661248 errors:1 dropped:0 overruns:1 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:5 Base address:0x9000
>
> eth1:0    Link encap:Ethernet  HWaddr 00:03:6D:1C:E3:3F
>           inet addr:X.Y.19.2  Bcast:X.Y.19.31  Mask:255.255.255.224
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           Interrupt:5 Base address:0x9000
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:72 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>
> tr0       Link encap:16/4 Mbps Token Ring  HWaddr 00:20:35:86:65:5A
>           inet addr:X.Y.83.1  Bcast:X.Y.83.31  Mask:255.255.255.224
>           UP BROADCAST RUNNING MULTICAST  MTU:2000  Metric:1
>           RX packets:11122600 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:9222364 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:9 Base address:0x9100
>
> Ip:
>     21583882 total packets received   <----- Shouldnt this be 11122600 +
> 696141 + 981311 = 21631852 ?
>     21540362 forwarded
>     0 incoming packets discarded
>     12767 incoming packets delivered  <----- What is this number?
>     16868 requests sent out
>     200 fragments failed              <----- Is this a problem?
> Icmp:
>     554 ICMP messages received
>     0 input ICMP message failed.
>     ICMP input histogram:
>         destination unreachable: 1
>         echo requests: 526
>         echo replies: 27
>     889 ICMP messages sent
>     0 ICMP messages failed
>     ICMP output histogram:
>         destination unreachable: 338
>         time exceeded: 25
>         echo replies: 526
> Tcp:
>     7 active connections openings
>     0 passive connection openings
>     0 failed connection attempts
>     0 connection resets received
>     1 connections established
>     11130 segments received          <--|______  What are these numbers?
>     15656 segments send out          <--|
>     34 segments retransmited
>     0 bad segments received.
>     29 resets sent                   <----- Is this a problem?
> Udp:
>     352 packets received
>     1 packets to unknown port received.    <----????
>     0 packet receive errors
>     354 packets sent
> TcpExt:
>     SockMallocOOM: 0
>
>
> 	Why does the total packets received number not match up to whats
> coming from 'ifconfig'? I'm running stock kernel 2.2.20 on a Debian distro
> . netstat --version reports :
>
> net-tools 1.54
> netstat 1.38 (1999-04-20)
>
> ifconfig --version reports :
>
> net-tools 1.54
> ifconfig 1.39 (1999-03-18)
>
> 	If it helps, here is the routing table :
>
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> X.Y.19.0        0.0.0.0         255.255.255.224 U     0      0        0
> eth1
> X.Y.83.0        0.0.0.0         255.255.255.224 U     0      0        0
> tr0
> X.Y.54.128      0.0.0.0         255.255.255.192 U     0      0        0
> eth0
> 192.168.0.0     0.0.0.0         255.255.0.0     U     0      0        0
> eth1
> 0.0.0.0         X.Y.54.129      0.0.0.0         UG    0      0        0
> eth0
>
> 	Any ideas / answers would be appreciated.
>
> Thanks,
> Kenneth
>
> -
> : send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-- 
Alexandre Dulaunoy			adulau@conostix.com
					http://www.conostix.com/

-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux