Ethereal-dev: RE: [Ethereal-dev] COL_PROTOCOL problem

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Martin Thomas <martin_a_thomas@xxxxxxxxx>
Date: Mon, 19 Feb 2001 13:10:56 -0800 (PST)
Like this?

  pinfo->current_proto = "RFC1006";
  if ( check_col( pinfo->fd, COL_PROTOCOL ) ) {
    col_set_str( pinfo->fd, COL_PROTOCOL, "RFC1006" );

I'll take out the check_col and try it again..

Thanks / Martin


--- Jeff Foster <jfoste@xxxxxxxxxxxx> wrote:
> 
> 
> From: Martin Thomas
> [mailto:martin_a_thomas@xxxxxxxxx]
> Sent: Monday, February 19, 2001 2:51 PM
> 
> > I am trying to figure out a problem I have with
> the
> > COL_PROTOCOL field.. I expected that the last
> > dissector
> > to fill in this field using col_set_str would
> override
> > all previous dissectors but that is not what I am
> > seeing.
> 
> > The background is this: I have rewritten the tpkt
> > dissector from Andreas Sikkema (and called it
> RFC1006)
> > so that it stands alone from q931. So far, so
> good.
> > Then I added COTP as a sub-dissector. This works..
> > (packets are dissected) but the COL_PROTO shows
> > RFC1006.. unless I put that as a filter term, in
> which
> > case, the protocol field changes to COTP.
> 
> 
> Perhaps you have a proto_tree value test before the 
> col_set_str call. During the file load the tree
> value
> will be null unless a filter is set; so the
> col_set_str
> function isn't being called.
> 
> 
> Jeff Foster
> jfoste@xxxxxxxxxxxx
> 
> 
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
>
http://www.ethereal.com/mailman/listinfo/ethereal-dev


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/