From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Problems with SNAT in POSTROUTING
Date: Tue, 6 Jan 2004 16:04:21 +0000 [thread overview]
Message-ID: <200401061604.21261.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040106154833.16498.qmail@web61101.mail.yahoo.com>
On Tuesday 06 January 2004 3:48 pm, Copag wrote:
> Sorry. I was in my house, now I'm at work.
>
> > When you say "new version of iptables" do you mean
> > you installed new
> > userspace tools, or have you simply moved to a new
> > version of Patch-O-Matic
> > iptables kernel patches, or further, have you
> > upgraded your kernel and patched
> > in a new version of patch-o-matic?
>
> We installed the new version of iptables only in the
> iptables version (1.2.28 to 1.2.29), with no changes
> in the kernel or Patch-O-Matic.
>
> > *IF* you have upgraded patch-o-matic and kernel,
> > you lkely need to rebuild your
> > userspace tools.... I recently moved from 2.4.23 to
> > 2.6.0 and more recent patch-o-matic
> > and found that to get SNAT working I had to rebuild
> > userspace tools.
>
> What is the "userspace tools"? What can I rebuild this
> to test?
iptables (ie: the command you use as a user) is the userspace tool, and
netfilter is the kernel part which does the filter according the rules
configured by iptables.
Since you say you have installed the new version of iptables, this is the
userspace tools - have you also upgraded the kernel (containing netfilter) to
match it?
Antony.
--
The truth is rarely pure, and never simple.
- Oscar Wilde
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-01-06 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200401060131.47476.Alistair Tonner <>
2004-01-06 15:48 ` Problems with SNAT in POSTROUTING Copag
2004-01-06 16:04 ` Antony Stone [this message]
2004-01-06 16:34 ` Unknown, Alistair Tonner
2004-01-06 5:41 Copag
2004-01-06 6:31 ` Unknown, Alistair Tonner
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=200401061604.21261.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.netfilter.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