From: Florian Westphal <fw@strlen.de>
To: maowenan <maowenan@huawei.com>
Cc: Phil Sutter <phil@nwl.cc>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: libmnl compile failure.
Date: Wed, 21 Dec 2016 12:28:48 +0100 [thread overview]
Message-ID: <20161221112848.GA5346@breakpoint.cc> (raw)
In-Reply-To: <F95AC9340317A84688A5F0DF0246F3F20151E85F@szxeml504-mbs.china.huawei.com>
maowenan <maowenan@huawei.com> wrote:
>
>
> > -----Original Message-----
> > From: Phil Sutter [mailto:phil@nwl.cc]
> > Sent: Monday, December 19, 2016 4:49 PM
> > To: maowenan
> > Cc: netfilter-devel@vger.kernel.org
> > Subject: Re: libmnl compile failure.
> >
> > Hi,
> >
> > On Fri, Dec 16, 2016 at 08:54:59AM +0800, maowenan wrote:
> > > There is something wrong when I make libmnl, could you please help check?
> >
> > There is no error message in the output you pasted. Looks like you're calling
> > 'make' in an already built source tree, so nothing needs to be done. Do you see
> > the binaries in src/.libs?
> >
> > Cheers, Phil
>
> Local
> process
> ^ | .-----------.
> .-----------. | | | Routing |
> | |-----> input / \---> output --->| Decision |----
> --> prerouting --->| Routing | .-----------. \
> | Decision | --> postrouting
> | | /
> | |---------------> forward ---------------------------
> .-----------.
>
> Is nftables output chain before routing decision? I think output is after routing decision, Is it wrong with above graphic?
Yes, the graph is wrong.
Output is after routing (which is why we need 'mangle' table in iptables
for rerouting and nftables' "route" chain property).
prev parent reply other threads:[~2016-12-21 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 0:54 libmnl compile failure maowenan
2016-12-19 8:49 ` Phil Sutter
2016-12-19 8:55 ` maowenan
2016-12-21 4:26 ` maowenan
2016-12-21 11:28 ` Florian Westphal [this message]
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=20161221112848.GA5346@breakpoint.cc \
--to=fw@strlen.de \
--cc=maowenan@huawei.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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;
as well as URLs for NNTP newsgroup(s).