From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: VPN PPTP
Date: Wed, 16 Jun 2004 21:39:09 +0100 [thread overview]
Message-ID: <200406162139.09672.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <200406162119.07631.Antony@Soft-Solutions.co.uk>
On Wednesday 16 June 2004 9:19 pm, Antony Stone wrote:
> On Wednesday 16 June 2004 8:57 pm, Luis GUSTAVO wrote:
> > yes.. i use NAT.
> >
> > but i download patch-o-matic, and apply pptp-nat.
> >
> > which rules i use now ?
>
> The ones I suggested earlier (with the addition, of course, of the
> appropriate NAT rules, which presumably need to go in your PREROUTING chain
> (if you're doing destination NAT?).
Just in case your next posting was going to be something like "I have those
rules, but it doesn't work", here is a suggestion for how to find out what's
not working.
Add two LOGging rules to the end of your FORWARD chain, one specifying at
least one of (a) the source address of the remote client, and/or (b) the
destination address of the server on your network, and the other specifying
at least one of (a) the source address of your local server, and/or (b) the
destination address of the remote client.
Then the LOG output will show you any packets going between the two machines
which are not being properly processed by the ACCEPT rules I suggested
earlier, and you can see what sort of packets they are, and add appropriate
rules to let them through.
Regards,
Antony.
--
The lottery is a tax for people who can't do maths.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-06-16 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 19:12 VPN PPTP Luis GUSTAVO
2004-06-16 19:41 ` Antony Stone
2004-06-16 19:57 ` Luis GUSTAVO
2004-06-16 20:19 ` Antony Stone
2004-06-16 20:39 ` Antony Stone [this message]
2004-06-16 20:43 ` Luis GUSTAVO
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=200406162139.09672.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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