[Coral-dev] Coral with DAG

[Stephen Donnelly]

I would be willing to take a look at the patch as well.

Regards,
Stephen.

> -----Original Message-----
> From: coral-dev-bounces at caida.org [mailto:coral-dev-bounces at caida.org] On
> Behalf Of Ken Keys
> Sent: Wednesday, 9 November 2011 7:10 a.m.
> To: Srinivas Krishnan
> Cc: Stephen Donnelly; coral-dev at caida.org
> Subject: Re: [Coral-dev] Coral with DAG
> 
> We are maintaining CoralReef, but I'm afraid we haven't kept up with changes in
> DAG, as we don't have any of the newer DAG cards.  If you send your patch to
> coral-info at caida.org, I'll see about integrating it into a release.
> 
> --
> Ken Keys
> kkeys at caida.org
> 
> On Mon, Nov 07, 2011 at 10:55:09PM -0500, Srinivas Krishnan wrote:
> > I ended up coding the functionality using the DAG API. Digging deeper
> > coral uses ioctl's to access information on the card and the new DAGs
> > dont use the same ioctls anymore.
> >
> > I patched coral to use the DAG API that should be more stable over
> > time. Is Coral actively being maintained, and is there a way for the
> > patch to make it into the repo ?
> >
> > -srinivas
> >
> >
> >
> > On Mon, Nov 7, 2011 at 10:26 PM, Stephen Donnelly <
> > Stephen.Donnelly at endace.com> wrote:
> >
> > >  I am not sure if the Coralreef developers are still maintaining the
> > > native DAG interface, possibly a bug has crept in.****
> > >
> > > ** **
> > >
> > > As a work-around you might try using the libpcap interface in Coral
> > > instead. Download and compile libpcap from tcpdump.org; it should
> > > automatically detect and include DAG support if it is installed.
> > > Then build Coral with libpcap support, making sure it is finding and
> > > linking against your new libpcap version. You may need to modify
> > > LD_LIBRARY_PATH or remove the distribution libpcap version.****
> > >
> > > ** **
> > >
> > > You can then capture from the libpcap ?dag0? interface in Coral (and
> > > other
> > > tools) instead of using the DAG native support. You will lose some
> > > time stamp resolution and the interface information with this method
> > > but it may be more robust.****
> > >
> > > ** **
> > >
> > > Regards,****
> > >
> > > Stephen.****
> > >
> > > ** **
> > >
> > > *From:* coral-dev-bounces at caida.org
> > > [mailto:coral-dev-bounces at caida.org] *On Behalf Of *Srinivas
> > > Krishnan
> > > *Sent:* Sunday, 6 November 2011 4:37 p.m.
> > > *To:* coral-dev at caida.org
> > > *Subject:* [Coral-dev] Coral with DAG****
> > >
> > > ** **
> > >
> > > We are trying to use Coral with our 10G DAG and compiled coral with
> > > DAG support. However, every time we try to use a utility it
> > > segfaults. Here is a sample:****
> > >
> > > ** **
> > >
> > >  crl_rate -Cproto=ETHER /dev/dag0****
> > >
> > > ** **
> > >
> > > Also a short trace of where it fails:****
> > >
> > > ** **
> > >
> > > Program received signal SIGSEGV, Segmentation fault.****
> > >
> > > coral_dag_init (src=0x6420d0) at coral_type_dag.c:158****
> > >
> > > 158             coral_cell_field_offset(iface0, PAYLOAD) = 18;****
> > >
> > > (gdb) bt****
> > >
> > > #0  coral_dag_init (src=0x6420d0) at coral_type_dag.c:158****
> > >
> > > #1  0x0000000000407638 in coral_open (src=0x6420d0) at
> > > coral_init.c:760***
> > > *
> > >
> > > #2  0x0000000000403d99 in src_info (src=0x0) at crl_info.c:227****
> > >
> > > #3  0x0000000000404908 in main (argc=3, argv=0x7fffffffe738) at
> > > crl_info.c:352****
> > >
> > > ** **
> > >
> > > Any suggestions on how to get around it ?****
> > >
> > >
> > > -srinivas****
> > >
> 
> > _______________________________________________
> > Coral-dev mailing list
> > Coral-dev at caida.org
> > https://rommie.caida.org/mailman/listinfo/coral-dev
> 
> _______________________________________________
> Coral-dev mailing list
> Coral-dev at caida.org
> https://rommie.caida.org/mailman/listinfo/coral-dev