From: Brian G <unixman83@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: How to get access to NAT info from userland
Date: Thu, 14 Apr 2011 02:12:49 -0500 [thread overview]
Message-ID: <4DA69E71.4040807@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1104140901331.28694@obet.zrqbmnf.qr>
On 4/14/2011 2:03 AM, Jan Engelhardt wrote:
> On Sunday 2011-04-03 02:07, Brian G wrote:
>> On 4/2/2011 6:55 PM, Sam Roberts wrote:
>>> On Sat, Apr 2, 2011 at 1:23 AM, Brian G<unixman83@gmail.com> wrote:
>>> Does the conntrack -L output have the info you'd like?
>> Probably. Too bad my distro (CentOS) doesn't seem to provide this binary.
> Ye, enterprise distributions have a bad track record for shipping the
> complete NF suite. Avoid :/
TPROXY will work, it should become commonplace by the time IPv6 gets
going strong. Someone on stackoverflow answered my question, although he
called tproxy a 'hack'. It will work fine so long as it doesn't hinder
performance.
Brian G.
next prev parent reply other threads:[~2011-04-14 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 8:23 How to get access to NAT info from userland Brian G
[not found] ` <AANLkTi=U8KZ_=ckSJ9yrqsTdG=L3tgtzLcDQ58mS=eRM@mail.gmail.com>
2011-04-03 0:07 ` Brian G
2011-04-14 7:03 ` Jan Engelhardt
2011-04-14 7:12 ` Brian G [this message]
2011-04-14 7:18 ` Jan Engelhardt
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=4DA69E71.4040807@gmail.com \
--to=unixman83@gmail.com \
--cc=jengelh@medozas.de \
--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.