From: Philip Craig <philipc@snapgear.com>
To: Chris Miller <cmiller@compuville.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: PPTP reviisted
Date: Tue, 30 Sep 2003 09:58:50 +1000 [thread overview]
Message-ID: <3F78C73A.8060003@snapgear.com> (raw)
In-Reply-To: <E1A43gZ-0007lH-Mn@bear.dns-nac-zone.com>
Chris Miller wrote:
> 7) Booted new kernel. Everything seems fine. SSH in so I can apply a
> rule that for some reason didn't get applied at boot. Here's what happenend:
>
>
>
> # iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -j MASQUERADE
>
> iptables: Invalid argument
From the help for the latest pptp-conntrack-nat.patch:
- you have to recompile your iptables userspace program since some
structure sizes change
--
Philip Craig - philipc@snapgear.com - http://www.SnapGear.com
SnapGear - Custom Embedded Solutions and Security Appliances
next prev parent reply other threads:[~2003-09-29 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 5:56 PPTP reviisted Chris Miller
2003-09-28 7:27 ` Daniel Chemko
2003-09-29 19:26 ` Chris Miller
2003-09-29 23:58 ` Philip Craig [this message]
2003-09-29 3:34 ` REDIRECT incoming Port to IP Jon Pol
2003-09-29 4:14 ` Jon Pol
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=3F78C73A.8060003@snapgear.com \
--to=philipc@snapgear.com \
--cc=cmiller@compuville.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