From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: incoming interface + ifb0
Date: Tue, 29 Jul 2008 20:31:28 +0200 [thread overview]
Message-ID: <20080729183128.GA2556@ami.dom.local> (raw)
In-Reply-To: <200807291626.36572.denys@visp.net.lb>
On Tue, Jul 29, 2008 at 04:26:36PM +0300, Denys Fedoryshchenko wrote:
> On Tuesday 29 July 2008, Jarek Poplawski wrote:
>
> > I didn't use this nor checked enough, so I can be wrong, but
> > since ingress with ifb0 is in prerouting, you probably can't use
> > rt_iif. You shouldn't filter at ifb on "dev" neither - it's "ifb"
> > at the moment. You need to match skb->iif with something (flow?).
> Yes
> I want to create on outgoing device or ifb(preffered) - tree of flows.
> Cause each interface = customer - i need to classify customers by flows.
>
> Since customer can have multiple/spoofed ip's - i cannot filter by ip for now.
> So iif only my choice seems.
>
> Maybe if i do redirect on outgoing to ifb on outgoing device it will work?
I doubt you can do something like this - or I miss something. IMHO,
you could try with this flow filter on ifb as a replacement for ipt
+ fw. Otherwise, if you can schedule on outgoing devs, you can use
e.g. cls_route. On the other hand ppp usually enables controlling
of clients, so maybe you should better try to use this more.
Jarek P.
prev parent reply other threads:[~2008-07-29 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 10:22 incoming interface + ifb0 Denys Fedoryshchenko
2008-07-29 12:48 ` Jarek Poplawski
2008-07-29 13:26 ` Denys Fedoryshchenko
2008-07-29 18:31 ` Jarek Poplawski [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=20080729183128.GA2556@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=denys@visp.net.lb \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).