From: James Cameron <james.cameron@hp.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Daniel Drake <dsd@gentoo.org>,
akpm@osdl.org, frank@google.com, linux-kernel@vger.kernel.org,
james.cameron@hp.com
Subject: Re: ppp_mppe+pptp for 2.6.14?
Date: Tue, 30 Aug 2005 09:51:31 +1000 [thread overview]
Message-ID: <20050829235131.GB20452@hp.com> (raw)
In-Reply-To: <20050829221034.GA4161@lists.us.dell.com>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
On Mon, Aug 29, 2005 at 05:10:34PM -0500, Matt Domsch wrote:
> I've asked James Cameron, pptp project lead, to try a test to force
> the server side to issue a CCP DOWN, to make sure the client-side
> kernel ppp_generic module does the right thing and drops packets.
I'm still working on this; tried Matt's patch against 2.6.13 last night,
but it seems 2.6.13 has broken raw sockets for pptp and pptpd ...
ENOPROTOOPT returned from the read() on the raw socket carrying the GRE
stream from pptp to the net. Wasn't happening with 2.6.12.5.
My plan is to try Matt's patch against 2.6.12.5, and try 2.6.13 bare, to
isolate the cause of the ENOPROTOOPT changed behaviour.
The previous version of Matt's patch (before the SC_MUST_COMP feature)
is working fine for me with 2.6.12.5.
(If anyone has any ideas on raw socket breakage, let me know. 2.6.13
changed net/ipv4/raw.c but the changes look to me to be minor.)
--
James Cameron
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-29 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 17:12 ppp_mppe+pptp for 2.6.14? Daniel Drake
[not found] ` <ec92bc305082910272da17f87@mail.gmail.com>
2005-08-29 17:30 ` Anshuman Gholap
2005-08-29 22:10 ` Matt Domsch
2005-08-29 23:51 ` James Cameron [this message]
2005-08-30 4:11 ` James Cameron
-- strict thread matches above, loose matches on Subject: below --
2005-08-30 13:37 Matt_Domsch
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=20050829235131.GB20452@hp.com \
--to=james.cameron@hp.com \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=dsd@gentoo.org \
--cc=frank@google.com \
--cc=linux-kernel@vger.kernel.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