Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: Problem with cls_flow nfct-* keys
Date: Thu, 03 Dec 2015 10:51:30 +0000	[thread overview]
Message-ID: <56601EB2.2070407@gmail.com> (raw)
In-Reply-To: <3419281448878074@web15j.yandex.ru>

Гаврилов Игорь wrote:
> So this problem not related to my setup. Seems that it occurs for a
> long time. Is there any possibility to fix this, and what is the
> reason of such behavior.

As Florian says on ingress tc gets the packet before conntrack.

I was slightly hopeful that I was wrong (in thinking this never worked)
when I saw "nf_ct_get" in the code, but it just looks at the skb which
on ingress won't have the fields filled in.

/* Return conntrack_info and tuple hash for given skb. */
static inline struct nf_conn *
nf_ct_get(const struct sk_buff *skb, enum ip_conntrack_info *ctinfo)
{
         *ctinfo = skb->nfctinfo;
         return (struct nf_conn *)skb->nfct;
}

Historically at least people used imq to get at traffic after netfilter.
It seems it's still alive -

www.linuximq.net

but you need to patch kernel/iptables.

When ifb first appeared it was mentioned that an action could be made to
get netfilter state and Florian mentions act_connmark.c so I guess some
progress was made.

Not really much use for your example I suppose.

  parent reply	other threads:[~2015-12-03 10:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 10:07 Problem with cls_flow nfct-* keys Гаврилов Игорь
2015-11-30 11:33 ` Гаврилов Игорь
2015-11-30 12:02 ` Andy Furniss
2015-11-30 15:49 ` Гаврилов Игорь
2015-12-03  0:24 ` Andy Furniss
2015-12-03  8:45 ` Гаврилов Игорь
2015-12-03  9:19 ` Florian Westphal
2015-12-03 10:50 ` Гаврилов Игорь
2015-12-03 10:51 ` Andy Furniss [this message]
2015-12-04 16:00 ` Гаврилов Игорь
2015-12-06 11:06 ` Andy Furniss
2015-12-07 11:15 ` Гаврилов Игорь
2015-12-08 21:38 ` Andy Furniss

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=56601EB2.2070407@gmail.com \
    --to=adf.lists@gmail.com \
    --cc=lartc@vger.kernel.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