Re: tcpdump: enable some more bgp info

2017-05-30 Thread Claudio Jeker
On Tue, May 30, 2017 at 11:06:10AM +0200, Michal Mazurek wrote: > On 10:43:30, 30.05.17, Job Snijders wrote: > > In the registry created by RFC 6608, the value "0" is the BGP Finite > > State Machine Error subcode meaning "Unspecified Error". I think that > > when a name is assigned to a value, the

Re: tcpdump: enable some more bgp info

2017-05-30 Thread Michal Mazurek
On 10:43:30, 30.05.17, Job Snijders wrote: > In the registry created by RFC 6608, the value "0" is the BGP Finite > State Machine Error subcode meaning "Unspecified Error". I think that > when a name is assigned to a value, the name should be printed (like > your patch does for subcode values 1, 2,

Re: tcpdump: enable some more bgp info

2017-05-30 Thread Job Snijders
On Tue, May 30, 2017 at 10:21:17AM +0200, Michal Mazurek wrote: > On 12:15:06, 29.05.17, Job Snijders wrote: > > perhaps add a comment like /* RFC 6608 */ above the below: > > Right, it will make it more consistent. > > > > +static const char *bgpnotify_minor_fsm[] = { > > > + NULL, "In OpenSent

Re: tcpdump: enable some more bgp info

2017-05-30 Thread Claudio Jeker
On Tue, May 30, 2017 at 10:21:17AM +0200, Michal Mazurek wrote: > On 12:15:06, 29.05.17, Job Snijders wrote: > > perhaps add a comment like /* RFC 6608 */ above the below: > > Right, it will make it more consistent. > > > > +static const char *bgpnotify_minor_fsm[] = { > > > + NULL, "In OpenSent

Re: tcpdump: enable some more bgp info

2017-05-30 Thread Peter Hessler
On 2017 May 30 (Tue) at 10:21:17 +0200 (+0200), Michal Mazurek wrote: :On 12:15:06, 29.05.17, Job Snijders wrote: :> perhaps add a comment like /* RFC 6608 */ above the below: : :Right, it will make it more consistent. : :> > +static const char *bgpnotify_minor_fsm[] = { :> > + NULL, "In OpenSent

Re: tcpdump: enable some more bgp info

2017-05-30 Thread Theo de Raadt
> > > +static const char *bgpnotify_minor_fsm[] = { > > > + NULL, "In OpenSent State", "In OpenConfirm State", > > > + "In Established State", > > > +}; > > > > and maybe s/NULL/"Unspecified Error"/ > > If it's NULL, then tcpdump will print out the number: > > if (p == NULL) { >

Re: tcpdump: enable some more bgp info

2017-05-30 Thread Michal Mazurek
On 12:15:06, 29.05.17, Job Snijders wrote: > perhaps add a comment like /* RFC 6608 */ above the below: Right, it will make it more consistent. > > +static const char *bgpnotify_minor_fsm[] = { > > + NULL, "In OpenSent State", "In OpenConfirm State", > > + "In Established State", > > +}; > >

Re: tcpdump: enable some more bgp info

2017-05-29 Thread Job Snijders
On Mon, May 29, 2017 at 12:02:33PM +0200, Michal Mazurek wrote: > The error information for bgp was commited in 2009 > (bgpnotify_minor_cease, bgpnotify_minor_cap) but never enabled, so do > that here. Also add FSM error codes. perhaps add a comment like /* RFC 6608 */ above the below: > +static

tcpdump: enable some more bgp info

2017-05-29 Thread Michal Mazurek
The error information for bgp was commited in 2009 (bgpnotify_minor_cease, bgpnotify_minor_cap) but never enabled, so do that here. Also add FSM error codes. Index: print-bgp.c === RCS file: /cvs/src/usr.sbin/tcpdump/print-bgp.c,v ret