From: Patrick McHardy <kaber@trash.net>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: 2.6.20: ipt_owner match and INPUT chain
Date: Sat, 03 Mar 2007 17:24:36 +0100 [thread overview]
Message-ID: <45E9A144.1050600@trash.net> (raw)
In-Reply-To: <200703021359.35886.thomas.jarosch@intra2net.com>
Thomas Jarosch wrote:
> Hello Patrick,
>
> On Friday, 2. March 2007, Patrick McHardy wrote:
>
>>The mainline kernel never supported this, you're thinking of the
>>owner socketlookup patch, which had multiple issues and was never
>>merged.
>
>
> Thanks for your reply. You're right, on 2.4 I've applied the socketlookup
> patch. I use it to accept incoming connections for a socks v5 proxy.
>
> Socks allows a client to bind a port on the external IP of the server
> and then wait for an incoming connection. Would it make sense to write a
> conntrack module which parses the communication between socks client and
> server and then adds the incoming connection to conntrack?
Not sure if its worth the effort. It also doesn't seem to fit the helper
model really well since the expectation is only relevant for the proxy
itself, not for the firewalls in between. Or does the proxy open a new
connection to the client when an external connection arrives?
> The easier solution would be to patch the socks server to execute a script
> if the client requests to bind a port on the server. The connection could be
> added via the userspace conntrack tool, right?
That should work. We could also add support for helperless expectations
for this, which will properly deal with NAT automatically.
next prev parent reply other threads:[~2007-03-03 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 8:46 2.6.20: ipt_owner match and INPUT chain Thomas Jarosch
2007-03-02 11:57 ` Patrick McHardy
2007-03-02 12:59 ` Thomas Jarosch
2007-03-03 16:24 ` Patrick McHardy [this message]
2007-03-05 17:06 ` Thomas Jarosch
2007-03-05 18:11 ` Patrick McHardy
2007-03-08 15:36 ` Thomas Jarosch
2007-03-08 18:01 ` Patrick McHardy
2007-03-09 10:38 ` Thomas Jarosch
2007-03-15 17:04 ` Thomas Jarosch
2007-03-16 4:06 ` Patrick McHardy
2007-03-16 12:52 ` Thomas Jarosch
2007-03-16 13:00 ` 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=45E9A144.1050600@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=thomas.jarosch@intra2net.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).