From: Menno Smits <menno@netbox.biz>
To: Jeff Hall <hall@vdata.com>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: PPTP connection tracking and Poptop on same box
Date: Thu, 04 Sep 2003 16:59:46 +1000 [thread overview]
Message-ID: <3F56E2E2.5040007@netbox.biz> (raw)
In-Reply-To: <Pine.GSO.4.56.0309031853090.10914@shemp.vdata.com>
Hi Jeff,
Thanks for your quick reply.
Jeff Hall wrote:
> I experienced some of these problems also trying to get 2.4.20 working
> with PoPToP and making outgoing connections from PCs behind the PoPToP
> server. Take a look at my messages dated March 2,3,20,21 and
> April 8 of this year in the netfilter-devel archives. With the patches
> in those messages I have multiple sessions connecting to a PoPToP server
> running on my firewall server and can make at least one outgoing
> connection from a PC behind that server (I didn't test making multiple
> outgoing connections but I believe that will also worked based on some
> tests I ran months ago). I also successfully tested running a PPTP client
> on the PoPToP server.
I've read those posts before but I went over them again just to make
sure I hadn't missed anything.
I checked the patches in your posts against a POM patched 2.4.20 kernel
I used to use here which exhibits the same problems as my 2.4.21 kernel.
I can't even find where your patches to ip_conntrack_pptp.c could be
applied! (even when trying to apply the patch manually). Key lines which
surround your changes simply don't exist in my tree. I was using POM out
of CVS from a few months ago in that kernel. What POM version are you
using? Which POM patches are you using?
I'm thinking I might try a vanilla kernel with the bare minimum of
patches to support PPTP conntrack. Knowing what POM version and patches
you're using would be useful for me so I can try and duplicate your setup.
> I have not (at least knowingly) modified the connection MTU, MRU, or
> TCPMSS and while I occassionally get the 'out of order' messages from
> pptpd the connection seems to recover. I'm using PoPToP v 1.1.3-2 with a
> patch to generate unique call ids.
Actually the MTU/MRU/TCPMSS stuff was to deal with "GRE: Discarding
duplicate packet" problems not 'out of order packet" problems like I
originally stated (it was a while ago). I removed these workarounds
today just to make sure that these had nothing to do with the problems
I'm having. Connection attempts seemed to behave in just the same way
(unreliably), and I started getting lots of "GRE: Discarding duplicate
packet" messages when a connection did establish and data was transferred.
Today I also made sure that the pptpd version I'm using (1.1.4) has the
callid patch and it definitely does. I modified it to log the callids
its using and it uses different ids for each connection, so no issue
there. Besides, that only becomes important once you have multiple
clients involved and so far in my testing there's only one.
Menno
next prev parent reply other threads:[~2003-09-04 6:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 5:36 PPTP connection tracking and Poptop on same box Menno Smits
2003-09-03 23:21 ` Jeff Hall
2003-09-04 6:59 ` Menno Smits [this message]
2003-09-04 8:04 ` Jeff Hall
2003-09-04 12:16 ` Wim Ceulemans
2003-09-04 23:57 ` Jeff Hall
2003-09-05 0:21 ` Menno Smits
2003-09-05 11:55 ` Harald Welte
2003-09-08 0:58 ` Menno Smits
2003-09-18 7:28 ` Wim Ceulemans
2003-09-18 23:57 ` Menno Smits
2003-09-09 8:39 ` Philip Craig
2003-09-21 14:05 ` Harald Welte
2003-09-22 8:06 ` Philip Craig
2003-09-22 8:52 ` Harald Welte
2003-09-21 22:48 ` Harald Welte
-- strict thread matches above, loose matches on Subject: below --
2003-09-02 23:25 Menno Smits
2004-01-18 23:00 Carl Farrington
2004-01-18 23:38 ` Antony Stone
[not found] <739652C2AFA4834AAB5986A215F68CEC4977@svr1.home.compsup.net>
2004-01-19 0:03 ` Antony Stone
2004-01-27 2:00 ` Harald Welte
2004-01-19 16:23 Carl Farrington
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=3F56E2E2.5040007@netbox.biz \
--to=menno@netbox.biz \
--cc=hall@vdata.com \
--cc=netfilter-devel@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 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.