On 2015-10-19 at 12:43:33 +0200, vkochan <vadi...@gmail.com> wrote:
> On Mon, Oct 19, 2015 at 12:36:42PM +0200, Tobias Klauser wrote:
> > On 2015-10-15 at 16:14:09 +0200, Geoff Ladwig <glad...@verdantnetworks.com> 
> > wrote:
> > > Vadim,
> > > 
> > > Thanks for responding.
> > > 
> > > I have never found much use for the ASCII output... but would be happy
> > > either way.
> > > 
> > > Possibly a --headers options so you can individually select --header, 
> > > --hex
> > > --ascii..?
> > > 
> > >  
> > > 
> > > I did not necessarily think this would be a new feature.. it seemed to 
> > > work
> > > this way be default in an older version (0.5.7)
> > > 
> > > Running on a different machine with the older version below, you can see 
> > > the
> > > header, asiii and hex all presented. This has no command line options. I'm
> > > guessing the display function shows things it has decoded and then shows 
> > > the
> > > rest (the packet data in this case) in hex.
> > 
> > Exactly, that's the default behavior. But it looks like with the nlmsg
> > dissector (which wasn't included in 0.5.7 yet) this doesn't work.
> 
> Sorry, seems I broke it ...

No problem! I fixed it in commit
f5f002fd8966b78ece5b4e1757e639379619670a. I would be glad if you could
check whether you see any problems with it.

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"netsniff-ng" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to netsniff-ng+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to