From: Mark Vevers <mark@vevers.net>
To: Jan Kaastrup <jka@protego.dk>,
'netfilter' <netfilter@lists.netfilter.org>
Subject: Re: Iptables and SNAT
Date: Tue, 17 Feb 2004 10:57:04 +0000 [thread overview]
Message-ID: <200402171057.08738.mark@vevers.net> (raw)
In-Reply-To: <004d01c3f53f$73685cf0$2d64a8c0@pcjka>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 17 Feb 2004 10:18 am, Jan Kaastrup wrote:
> Hi list
> After a reboot of my RedHat mashine, the NAT part of Iptables stop
> working.
Is the iptable_nat module loaded?
/sbin/lsmod will list the modules and if any modules are not loaded for
the ruleset then you'll either need to modprobe them beforehand or
alter modules.conf to load them when iptables loads (add below ...)
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)
iD8DBQFAMfOEWLU9HLCPPKMRAu0XAJ9yVLQ0X3x0XNQ84irLTOVdZPrWUACdGr2Y
udGvM/2ukyptia+Vh/+UX6s=
=t6Ag
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-17 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 21:12 Iptables and bridge Adi
2004-02-17 6:55 ` Stephen Satchell
2004-02-17 10:18 ` Iptables and SNAT Jan Kaastrup
2004-02-17 10:57 ` Mark Vevers [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 " codingfreak
2009-10-27 9:03 ` Richard Horton
[not found] <200402171428.52966.mark@vevers.net>
2004-02-17 14:39 ` Iptables " Jan Kaastrup
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=200402171057.08738.mark@vevers.net \
--to=mark@vevers.net \
--cc=jka@protego.dk \
--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