Re: [OpenCALEA] Recent updates

[Mario Antonio]

See attached conf file (basically make /home/calea the default folder for
everything)

I issue the following secuence of commands (so far, I am avoiding the
controller interface)

controllerd -f /home/calea/opencalea.conf &
df_collector -f /home/calea/opencalea.conf &
lea_collector -f /home/calea/opencalea.conf -b 127.0.0.1 -t li4 -f lf4  &
tap -f /home/calea/opencalea.conf  -x 001 -y 001 -z 001 -c pcap host 1.1.1.1
&
and (Killing the previous tap process)
tap -f /home/calea/opencalea.conf  -x 002 -y 002 -z 002 -c  ias-cmc host
1.1.1.1 &

Two folders were created in /home/calea  001 and 002 with  the following
files: CmC ,CmII  , and Log

I noticed that the CmC file remained empty for both tapping process
I have the following questions:
1) Am I missing something since the CmC files do not show up any content?
(both lea_collector files show content, though)
2) Is there an easy way/tool to verify the resulting files format?
3) Since I used -c pcap with tap, I was expecting that I could read the CmC
file with tcpdump, is this correct?

Regards,

Mario Antonio






----- Original Message ----- 
From: "Norman Brandinger" <norm@goes.com>
To: <opencalea@merit.edu>
Sent: Thursday, May 03, 2007 5:04 PM
Subject: [OpenCALEA] Recent updates


> There have been some interesting updates to the OpenCALEA software base.
>
> It should be noted that the software is under heavy development and is
> not ready for a "load and go" installation.
>
> 1. The packet capture routine (tap) can now call T1.IAS and/or T1.678
> LAES routines to BER encode the captured packet.
> 2. Tap can then send the BER encoded packet (along with a control
> header) to the OpenCALEA delivery function (df_collection).
> 2a. Tap currently sends two "ROUTE ADD" control messages to
> df_collector.  These messages instruct df_collector to open connections
> to the LEA collector (lea_collector in our case).
> 3. The df_collector looks at the control header and routes the BER
> encoded data to the appropriate LEA.
>
> Actually, LEA for our testing purposes is the old lea_collector that has
> been modified to "sink" data to files.
>
> The ASN.1 routines included in the OpenCALEA distribution contain
> "converter-sample" programs.  These programs have been used to validate
> that the BER encoded data that tap is sending matches the data that the
> lea_collector recorded to its files.
>
> During the development of these recent changes, I've been more focused
> on getting a T1.IAS/T1.678 encoded packet sent to the lea_collector than
> writing pretty code. I'm in the process of cleaning up and hardening
> what "mechanically" works.
>
> Regards,
> Norm
>
>
>

Attachment: opencalea.conf
Description: Binary data