From: Matt Domsch <matt@domsch.com>
To: Philip Craig <philipc@snapgear.com>, laforge@netfilter.org
Cc: netfilter@lists.netfilter.org
Subject: Re: pptp & NAT
Date: Sat, 5 Nov 2005 08:22:07 -0600 [thread overview]
Message-ID: <20051105142207.GA29131@domsch.com> (raw)
In-Reply-To: <436ADCFB.6070201@snapgear.com>
On Fri, Nov 04, 2005 at 02:00:59PM +1000, Philip Craig wrote:
> Please try the attached patch. It has fixed a problem for someone else,
> and I think this problem may be the same, but I'm not sure.
With this patch applied, it's working for me.
> > - I am unable to estabish two pptp connections from one client, I can
> > connect to one pptp server and I can connect to a second pptp server,
> > but the second connection never accepts any traffic, when I stop the
> > first connection, the second connection begins to work. Is this a bug or
> > a known missing feature ?
>
> This is intended to work. I haven't personally tested it in
> 2.6.14 though.
Using the endian fix patch and this patch (both are attached to bug
397), this is working for me on a 2.6.14 kernel (really, git HEAD from
yesterday plus these two patches). I've got 2 clients, one WindowsXP,
one Fedora Core 4, hitting the same PPTP server at the same time.
Sincere thanks to both you and Harald for this effort!
Thanks,
Matt
next prev parent reply other threads:[~2005-11-05 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 3:53 pptp & NAT Sebastian Böhm
2005-11-04 4:00 ` Philip Craig
2005-11-05 14:22 ` Matt Domsch [this message]
2005-11-05 22:48 ` Sebastian
2005-11-06 9:26 ` Harald Welte
2005-11-16 14:05 ` Hwo to applu this " Sebastião Antônio Campos (GWA)
-- strict thread matches above, loose matches on Subject: below --
2007-03-09 16:33 PPTP NAT Andrei-Florian Staicu
[not found] <1042821169.13896.22.camel@torwood>
2003-01-18 15:41 ` Harald Welte
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=20051105142207.GA29131@domsch.com \
--to=matt@domsch.com \
--cc=laforge@netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=philipc@snapgear.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.