From: "Voltaire Pascual" <voltaire@voltaire.servebeer.com>
To: Cory Visi <merlin@phear.lwz.org>, netfilter@lists.netfilter.org
Subject: Re: Static compile issues - same problem.
Date: Sat, 31 May 2003 20:50:51 +0800 [thread overview]
Message-ID: <001901c32773$44f90a80$6400a8c0@homes> (raw)
In-Reply-To: Pine.LNX.4.30.0305270725050.7597-100000@phear.lwz.org
Anyone have solution to this problem yet? I have patched 2.4.20 with
ipt_pptp_conntrack successfully (static/module) but i cant use NAT in the
firewall after.
# iptables -t nat -A POSTROUTING -o $EXTERNAL -s $INTERNAL_NETWORK -j SNAT
--to-source $EXTERNAL_IP
Invalid argument
Appreciate your help.
----- Original Message -----
From: "Cory Visi" <merlin@phear.lwz.org>
To: <netfilter@lists.netfilter.org>
Sent: Tuesday, May 27, 2003 7:42 PM
Subject: Static compile issues
> I am using a 2.4.20 kernel with pom-20030107 and iptables v1.2.7a. From
> pom-20030107, I have installed all the pending patches and all the base
> patches. In addition, I have installed the following extra patches:
>
> ipt-amanda-conntrack-nat
> ipt-eggdrop-conntrack-nat
> ipt-proc
> ipt-mms-conntrack-net
> ipt-pptp-conntrack-net
> ipt-quake3-conntrack-net
> ipt-rsh-conntrack-net
> ipt-tftp-conntrack-net
>
> The patch names are not official or anything. I just split them up and
> called them that. Hopefully, the name is clear enough to you to recognize
> an "extra" patch. Please let me know if this is confusing.
>
> The problem is, when I compile the kernel statically and enable all the
> iptables options, I cannot do NAT. Any iptables line that specifies a
> chain in the nat table causes an Invalid Argument:
>
> # iptables -t nat -A POSTROUTING -o $EXTERNAL -s $INTERNAL_NETWORK -j SNAT
> --to-source $EXTERNAL_IP
> Invalid argument
>
> Another interesting thing to point out, is that I also compiled this
> kernel with modules and experienced the same problem. I was, however, able
> to fix it by disabling the IPv4 netfilter option for "NAT of local
> connections". For the module kernel, disabling this option fixes the
> problem. For the staticly compiled kernel, disabling this option has no
> effect-- the error persists.
>
> Anyone have any ideas?
> Please CC me directly if you respond to the list, since I am not
> subscribed (yet).
>
> Thank you,
> Cory Visi
>
>
prev parent reply other threads:[~2003-05-31 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 11:42 Static compile issues Cory Visi
2003-05-31 12:50 ` Voltaire Pascual [this message]
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='001901c32773$44f90a80$6400a8c0@homes' \
--to=voltaire@voltaire.servebeer.com \
--cc=merlin@phear.lwz.org \
--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