From: Unknown <unknown@unknown.invalid>
From: Alistair Tonner <>
To: Copag <c0p4g@yahoo.com.br>, netfilter@lists.netfilter.org
Subject: Re: Problems with SNAT in POSTROUTING
Date: Tue, 6 Jan 2004 11:34:37 -0500 [thread overview]
Message-ID: <42126.729936763$1073407011@news.gmane.org> (raw)
In-Reply-To: <20040106154833.16498.qmail@web61101.mail.yahoo.com>
On January 6, 2004 10:48 am, 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.
>
Here is your problem. If you change versions of netfilter you need
to put those changes into your kernel -- i.e. -- rebuild the kernel.
That makes it a good time to upgrade patch-o-matic if you use anything
out of it.
> > *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?
>
> Thanks a lot.
>
>
> Joao Paulo
>
>
>
> ______________________________________________________________________
>
> Conheça a nova central de informações anti-spam do Yahoo! Mail:
> http://www.yahoo.com.br/antispam
next prev parent reply other threads:[~2004-01-06 16:34 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
2004-01-06 16:34 ` Unknown, Alistair Tonner [this message]
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='42126.729936763$1073407011@news.gmane.org' \
--to=unknown@unknown.invalid \
--cc=c0p4g@yahoo.com.br \
--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