On Thu, Mar 08, 2001 at 01:24:37PM +0100, Sasa Milic wrote:
> Take a look at local.linterfaces.lifTable table. There you will
> find:
> locIfipInPkts OBJECT IDENTIFIER ::= { lifEntry 42 }
> locIfipOutPkts OBJECT IDENTIFIER ::= { lifEntry 43 }
> locIfipInOctets OBJECT IDENTIFIER ::= { lifEntry 44 }
> locIfipOutOctets OBJECT IDENTIFIER ::= { lifEntry 45 }
But they do not seem to be correct, too!
When I send a ping like this:
ping -c 1 -s 1 212.117.XXX.YYY
then I would assume that the locIfipInPkts increases by 1 and the
locIfipInOctets increases by 20(IP)+8(ICMP)+1(DATA) = 29 bytes. But it does
in fact increase by 1 packet but 33 bytes! Exactly the same 4 mistyrious bytes
I always have "too much" in the normal "show interface" byte counter and which
I assumed to be the HDLC overhead (although I don't know how to come to 4 bytes
for it...)
I verified the 29 bytes with ethereal and tcpdump on both sides. The remote
host *gets* only 29 bytes and not 33!
Any ideas? Does it be correct at your side?
bye,
-christian-
--
Christian Hammers WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0
[EMAIL PROTECTED] Internet & Security for Professionals Fax 0241/911879
WESTEND ist CISCO Systems Partner - Premium Certified
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
