From: Patrick McHardy <kaber@trash.net>
To: jon hale <jon.h.hale@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Does policy routing based on owner-gid really work?
Date: Mon, 01 Sep 2008 15:14:43 +0200 [thread overview]
Message-ID: <48BBEAC3.8040801@trash.net> (raw)
In-Reply-To: <abe9c56e0808221638m35d2af7bu3535099e55e6c786@mail.gmail.com>
jon hale wrote:
> I have a problem when I combine owner-gid, fwmark, and iproute2.
> I am starting to wonder if I can really get there from here.
>
> Synopsis:
> I have been trying to set up policy routing based upon the group id
> of the process sending the packets.
>
> It works for most packets, but there is some scenario that happens at
> the end of every ftp upload, where the packet goes out the wrong
> interface and gums up the works.
The stack may send packets that don't belong to the original socket.
You need to use CONNMARK to make sure all packets of a connection
are marked similar.
next prev parent reply other threads:[~2008-09-01 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 23:38 Does policy routing based on owner-gid really work? jon hale
2008-09-01 13:14 ` Patrick McHardy [this message]
2008-09-02 18:44 ` jon hale
2008-09-03 14:22 ` Eric Leblond
2008-09-03 22:52 ` jon hale
2008-09-04 6:59 ` Eric Leblond
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=48BBEAC3.8040801@trash.net \
--to=kaber@trash.net \
--cc=jon.h.hale@gmail.com \
--cc=netfilter-devel@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.