Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Stephen Satchell <list@satchell.net>, netfilter@vger.kernel.org
Subject: Re: nft -- documentation on fib_addrtype missing, more data
Date: Fri, 11 Oct 2019 11:47:21 +0200	[thread overview]
Message-ID: <20191011094721.GL25052@breakpoint.cc> (raw)
In-Reply-To: <20191011082926.4wfyhysc6joofuel@salvia>

Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> # nft describe fib saddr type
> fib expression, datatype fib_addrtype (fib address type) (basetype integer), 32 bits
> 
> pre-defined symbolic constants (in decimal):
[..]

It might make sense to teach nft describe to also work with the type,
so you could get the symbolic constants via

nft describe fib_addrtype

What do you think?

  reply	other threads:[~2019-10-11  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 21:45 nft -- documentation on fib_addrtype missing, more data Stephen Satchell
2019-10-11  8:29 ` Pablo Neira Ayuso
2019-10-11  9:47   ` Florian Westphal [this message]
2019-10-11 10:04     ` Pablo Neira Ayuso
2019-10-11 15:09     ` Stephen Satchell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191011094721.GL25052@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=list@satchell.net \
    --cc=netfilter@vger.kernel.org \
    --cc=pablo@netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox