<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: cipe-l,AT,inka,DOT,de
Subject: Wrong no. of bytes with cipe and accounting tables (fwd)
From: Holger Marzen <holger,AT,marzen,DOT,de>
Date: Mon, 22 Dec 2003 21:45:47 +0100 (CET)

Additional insight :-)

When I ping 4 Times through cipcb2 then I see 4 packets in both INPUT
chains and a reasonable number of bytes. The ACC_cipcb2_OUTPUT then
looks ok as well. But ACC_ppp0_OUTPUT has 0 packets and 0 bytes.

Does the cipe-module has a bug that causes its outgoing packets not
being processed or flagged with the correct outgoing interface?

-- 
PGP/GPG Key-ID:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xB5A1AFE1

---------- Forwarded message ----------
Date: Mon, 22 Dec 2003 20:08:13 +0100 (CET)
From: Holger Marzen <holger,AT,marzen,DOT,de>
To: cipe-l,AT,inka,DOT,de
Subject: Wrong no. of bytes with cipe and accounting tables

To count my traffic I setup some accounting rules that are called by the
input- and output rules CHECKIN and CHECKOUT. The accounting rules look
like:

Chain ACC_cipcb2_INPUT (1 references)
 pkts bytes target     prot opt in     out     source               
destination
  106 58467 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0

Chain ACC_cipcb2_OUTPUT (1 references)
 pkts bytes target     prot opt in     out     source               
destination
   83  6236 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0

Chain ACC_ppp0_INPUT (1 references)
 pkts bytes target     prot opt in     out     source               
destination
  113 64380 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0
      ^^^^^ looks ok (>58467)

Chain ACC_ppp0_OUTPUT (1 references)
 pkts bytes target     prot opt in     out     source               
destination
    7   988 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0
        ^^^ cannot be ok because it's less than 6236!

Since the cipcb2 traffic goes out through ppp0 I don't understand why
both traffic and packet count of ppp0 is less than the values of cipcb2.
But only in the output chains. The values of the input chains look good.

That's how the accounting rules are inserted as first rules in the
chains:

Chain CHECKOUT (1 references)
 pkts bytes target     prot opt in     out     source               
destination
 9071 1116K ACC_ppp0_OUTPUT  all  --  *      ppp0    0.0.0.0/0            
0.0.0.0/0
 5409 1511K ACC_cipcb2_OUTPUT  all  --  *      cipcb2  0.0.0.0/0            
0.0.0.0/0
 [...]

Chain CHECKIN (1 references)
 pkts bytes target     prot opt in     out     source               
destination
18539 8203K ACC_ppp0_INPUT  all  --  ppp0   *       0.0.0.0/0            
0.0.0.0/0
 6118 3433K ACC_cipcb2_INPUT  all  --  cipcb2 *       0.0.0.0/0            
0.0.0.0/0
 [...]

How can ppp0's counters be less than cipcb2's counter? Does CIPE
compress packets and puts several of them together in a single packet?

--
Message sent by the cipe-l,AT,inka,DOT,de mailing list.
Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>


<< | Thread Index | >> ]    [ << | Date Index | >> ]