All of lore.kernel.org
 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 00:24:58 +0000	[thread overview]
Message-ID: <565F8BDA.9040405@gmail.com> (raw)
In-Reply-To: <3419281448878074@web15j.yandex.ru>

Гаврилов Игорь wrote:
>> I am not sure if this should work or not.
> In all examples this worked, But I can't test it on old kenels - I
> use 3.10.
>
>> If there is no/low incoming traffic to this box then you could
>> shape on egress.
> Unfortunately  this is not an option. The single case, where IFB
> could be a problem, and you can't shape on egress interface is when
> you have traffic to/from router. There is IPSec tunnels from WAN
> interface, and I need to share bandwidth dynamically between regular
> internet traffic and IPSec.
>
>> Generally I would avoid redirecting protocol all then restricting
>> htb default - you may end up dropping arp.
> I have dedicated class for ARP.
>

Ok, I can't easily test old kernels either.

I did a quick test on my desktop with a recent git kernel and it doesn't
work for me either.

The same test (using ifb) does work on egress.

Adding a printk shows a call to nf_ct_get(skb, &ctinfo)

returns NULL which makes flow fallback to dst.

  parent reply	other threads:[~2015-12-03  0:24 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 [this message]
2015-12-03  8:45 ` Гаврилов Игорь
2015-12-03  9:19 ` Florian Westphal
2015-12-03 10:50 ` Гаврилов Игорь
2015-12-03 10:51 ` Andy Furniss
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=565F8BDA.9040405@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.