On Sun, May 29, 2005 at 08:02:22PM -0600, jared r r spiegel wrote:
> 
>   note, i setup the 192.168.7.17 <-> 192.168.7.18 testcase due
>   to initially seeing the issue against a remote host, and then
>   trying to duplicate with a simple case.
> 
>   also, the following counters are staying at 0 in all cases:

  sigh, hopefully i have all the bases covered now:

  for instance, here is 192.168.7.18's netstat -sp ipcomp
  before and after i do a crapload of pings with that -p 00 from .17:

-----
[/home/jrrs] $ netstat -sp ipcomp
ipcomp:
        40220 input IPCOMP packets
        28212 output IPCOMP packets
        0 packets from unsupported protocol families
        0 packets shorter than header shows
        0 packets dropped due to policy
        34 packets for which no TDB was found
        0 input packets that failed to be processed
        9890 packets for which no XFORM was set in TDB received
        0 packets were dropped due to full output queue
        0 packets where counter wrapping was detected
        0 packets attempted to use an invalid TDB
        0 packets got larger than max IP packet size
        0 packets that failed (de)compression processing
        5563 packets less than minimum compression length
        29424355 input bytes
        28678436 output bytes
[/home/jrrs] $ netstat -sp ipcomp
ipcomp:
        40696 input IPCOMP packets
        28212 output IPCOMP packets
        0 packets from unsupported protocol families
        0 packets shorter than header shows
        0 packets dropped due to policy
        34 packets for which no TDB was found
        0 input packets that failed to be processed
        10366 packets for which no XFORM was set in TDB received
        0 packets were dropped due to full output queue
        0 packets where counter wrapping was detected
        0 packets attempted to use an invalid TDB
        0 packets got larger than max IP packet size
        0 packets that failed (de)compression processing
        5563 packets less than minimum compression length
        29437012 input bytes
        28678436 output bytes

--- 192.168.7.18 ping statistics ---
476 packets transmitted, 0 packets received, 100.0% packet loss

------

  and here is the same if i leave out the '-p00' stuff and it 
  works:

------
[/home/jrrs] $ netstat -sp ipcomp
ipcomp:
        40699 input IPCOMP packets
        28212 output IPCOMP packets
        0 packets from unsupported protocol families
        0 packets shorter than header shows
        0 packets dropped due to policy
        34 packets for which no TDB was found
        0 input packets that failed to be processed
        10366 packets for which no XFORM was set in TDB received
        0 packets were dropped due to full output queue
        0 packets where counter wrapping was detected
        0 packets attempted to use an invalid TDB
        0 packets got larger than max IP packet size
        0 packets that failed (de)compression processing
        5572 packets less than minimum compression length
        29437500 input bytes
        28678436 output bytes
[/home/jrrs] $ netstat -sp ipcomp
ipcomp:
        46470 input IPCOMP packets
        33980 output IPCOMP packets
        0 packets from unsupported protocol families
        0 packets shorter than header shows
        0 packets dropped due to policy
        34 packets for which no TDB was found
        0 input packets that failed to be processed
        10366 packets for which no XFORM was set in TDB received
        0 packets were dropped due to full output queue
        0 packets where counter wrapping was detected
        0 packets attempted to use an invalid TDB
        0 packets got larger than max IP packet size
        0 packets that failed (de)compression processing
        5575 packets less than minimum compression length
        35252272 input bytes
        34492580 output bytes

--- 192.168.7.18 ping statistics ---
5767 packets transmitted, 5766 packets received, 0.0% packet loss

------

  hopefully that can clarify any ambiguity questions.
  the 'packets for which no TDB was found' was from 
  a while back when i setup the CPIs wrong.

-- 

[ openbsd 3.7 GENERIC ( may 17 ) // i386 ]

Reply via email to