From: "Jan Kaastrup" <jka@protego.dk>
To: mark@vevers.net
Cc: netfilter@lists.netfilter.org
Subject: RE: Iptables and SNAT
Date: Tue, 17 Feb 2004 15:39:37 +0100 [thread overview]
Message-ID: <000001c3f563$de6ba5b0$2d64a8c0@pcjka> (raw)
In-Reply-To: <200402171428.52966.mark@vevers.net>
Hi
Thanks for the answer.
I found out that recompiling the iptables with
KERNEL_DIR=<my-kernel-source> did the trick!
-----Original Message-----
From: Mark Vevers [mailto:mark@vevers.net]
Sent: 17. februar 2004 15:29
To: Jan Kaastrup
Subject: Re: Iptables and SNAT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 17 Feb 2004 11:03 am, you wrote:
> Hi
> I have iptable module loaded
Ok - are you using RedHat's IP tables? Or have you compiled
your own and your own patch-o-matic additions? - I've seen
problems before where people have mixed & matched. On RH
if using patch-o-matic patches and upgrading iptables to match
I uninstall the iptables rpm, compile from a vanilla kernel and
then add the patch-o-matic patches and then recompile the
userspace apps from scratch.
BTW You need to be careful using vanilla kernels with
multi-threaded apps on Fedora as it appears there are
problems with fedora and a kernel which doesn't have
NPTL support. RH.9 seems not to mind even though the
vanilla kernel doesn't support NPTL.
Cheers
Mark
- --
Mark Vevers. mark@ifl.net / mark@vevers.net
Principal Internet Engineer, Internet for Learning,
Research Machines Plc. (AS5503)
- --
GPG Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB08F3CA3
Fingerprint: 85BA 30C4 9EC8 1792 4C8C C31E 58B5 3D1C B08F 3CA3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFAMiUjWLU9HLCPPKMRAi0wAJ9/8W/vNs6+jP70KGtvMc8mQkOongCcCp5Y
DQnQ4zyWomkhPaW0gj26rJk=
=C7Qg
-----END PGP SIGNATURE-----
next parent reply other threads:[~2004-02-17 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200402171428.52966.mark@vevers.net>
2004-02-17 14:39 ` Jan Kaastrup [this message]
[not found] <95ac437a-3f19-490a-80d0-3ce0a20850ed@y10g2000prg.googlegroups.com>
[not found] ` <46ee7b1c0910212155pd99519cw9831d4bb7d7f3064@mail.gmail.com>
[not found] ` <b8dec168-132d-4fba-9d09-fbb5554c339d@m7g2000prd.googlegroups.com>
2009-10-27 5:08 ` IPtables and SNAT codingfreak
2009-10-27 9:03 ` Richard Horton
2004-02-17 6:55 Iptables and bridge Stephen Satchell
2004-02-17 10:18 ` Iptables and SNAT Jan Kaastrup
2004-02-17 10:57 ` Mark Vevers
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='000001c3f563$de6ba5b0$2d64a8c0@pcjka' \
--to=jka@protego.dk \
--cc=mark@vevers.net \
--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