From: Mike Machado <mike@innercite.com>
To: netfilter@lists.netfilter.org
Subject: Re: pptp-conntrack-nat
Date: 11 Jun 2003 18:14:07 -0700 [thread overview]
Message-ID: <1055380447.20003.28.camel@rocket.innercite.com> (raw)
In-Reply-To: <1055376249.20254.16.camel@rocket.innercite.com>
There appears to be something that affects more than just the MASQUERADE
target. For shitz and gigglez I tried changing the rule to
iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o eth0 -j REJECT
and got the same Invalid Argument. I then tried -j DROP and that worked.
ipt_REJECT is also loaded, so is it possible that the pptp-conntrack-nat
patches changes some internal nat structures or code that is not
allowing the other ipt_ modules to function?
Just to be thorough, did a fresh cvs update I applied all the pending
patches, and got the same thing.
On Wed, 2003-06-11 at 17:04, Mike Machado wrote:
> I used CVS/POM and patched my vanilla 2.4.20 kernel to include support
> for ip_conntrack_pptp and ip_nat_pptp, but after I do this, the
> MASQUERADE target no longer works. lsmod shows both modules load
> successfully as well as the ipt_MASQUERADE, but when I run my nat rule:
>
> iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o eth0 -j MASQUERADE
>
> it just says Invalid Argument. I have two identical kernels, one with
> the pptp patch applied, one without, and the one without allows the
> MASQUERADE target just fine. Is there a known bug with the latest CVS
> pptp-conntrack-nat patch interfearing with masquerading? Thanks.
--
Mike Machado
mike@innercite.com
InnerCite Inc.
Engineering Director / CTO
next prev parent reply other threads:[~2003-06-12 1:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 0:04 pptp-conntrack-nat Mike Machado
2003-06-12 1:14 ` Mike Machado [this message]
2003-06-12 1:52 ` pptp-conntrack-nat Philip Craig
-- strict thread matches above, loose matches on Subject: below --
2003-11-27 15:34 pptp-conntrack-nat Oleg Savostyanov
2003-12-01 11:43 ` pptp-conntrack-nat Oleg Savostyanov
2003-12-01 12:16 ` pptp-conntrack-nat Goetz Bock
2003-12-01 12:22 ` pptp-conntrack-nat Rob Sterenborg
2004-05-04 19:14 pptp-conntrack-nat Ampugnani, Fernando
2004-05-05 3:24 ` pptp-conntrack-nat Philip Craig
2004-05-05 5:10 ` pptp-conntrack-nat Andrew E. Mileski
2004-05-05 13:41 pptp-conntrack-nat Ampugnani, Fernando
2004-09-14 16:10 pptp-conntrack-nat lucas baresi
2004-09-14 16:18 ` pptp-conntrack-nat rruegner
2004-09-14 17:31 ` pptp-conntrack-nat Jason Opperisano
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=1055380447.20003.28.camel@rocket.innercite.com \
--to=mike@innercite.com \
--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