From: Patrick McHardy <kaber@trash.net>
To: lepton <ytht.net@gmail.com>
Cc: Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH] 2.6.22.6 netfilter: sk_setup_caps in ip_make_route_harder
Date: Fri, 21 Sep 2007 14:39:58 +0200 [thread overview]
Message-ID: <46F3BB9E.4000105@trash.net> (raw)
In-Reply-To: <20070919155554.GA11710@router.lepton.home>
lepton wrote:
> Yes, you are right.
> What do you think about this:
> For all packets can be sent out, we just disable
> all things in sk_route_caps in ip_route_me_harder
Whats the point of doing that? Is rerouting breaking anything for you?
next prev parent reply other threads:[~2007-09-21 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070919093648.GA7491@router.lepton.home>
2007-09-19 15:00 ` [RFC PATCH] 2.6.22.6 netfilter: sk_setup_caps in ip_make_route_harder Patrick McHardy
2007-09-19 15:17 ` Patrick McHardy
2007-09-19 15:55 ` lepton
2007-09-21 12:39 ` Patrick McHardy [this message]
2007-09-21 14:07 ` lepton
2007-09-21 14:57 ` Patrick McHardy
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=46F3BB9E.4000105@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ytht.net@gmail.com \
/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).