From: Jay Nitikman <jay@permeable.com>
To: linux-ppp@vger.kernel.org
Subject: Re: ioctl(ppp_dev_fd, PPPIOCSCOMPRESS, (caddr_t) &data) fails
Date: Sun, 13 Nov 2005 23:51:08 +0000 [thread overview]
Message-ID: <4377D16C.8000500@permeable.com> (raw)
In-Reply-To: <43762E6B.5020108@permeable.com>
Okay, I have more information. My boot log does not show the following
line:
PPP MPPE Compression module registered
Which seems to be required in order for MPPE to be valid. I have no
idea what would prevent the compiled-in MPPE module from registering.
Any ideas would be helpful.
Jay
Jay Nitikman wrote:
> My working vpn connection stopped working "suddenly". I did some testing
> and discovered that the call:
>
> ioctl(ppp_dev_fd, PPPIOCSCOMPRESS, (caddr_t) &data)
>
> in ccp_test() in sys-linux.c in pppd always returns EINVAL.
>
> My kernel, 2.6.10-gentoo-r6, has MPPE compiled in, not as a module.
> The ppp_dev_fd has a value of "22" which seems reasonable. So it
> appears that PPPIOCSCOMPRESS is invalid. Huh?
>
> I am using Gentoo ppp-2.4.3-r9.
>
> This has been working fine for months. I have tried rebooting, both
> cold and warm. I've tried rebuilding ppp-2.4.3-r9. I've tried
> ppp-2.4.2-r15. My vpn provider says that nothing has changed on their
> side.
>
> Any ideas why that ioctl should fail and how to fix it?
>
--
-----------------
Jay Nitikman
jay@permeable.com
-----------------
next prev parent reply other threads:[~2005-11-13 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 18:03 ioctl(ppp_dev_fd, PPPIOCSCOMPRESS, (caddr_t) &data) fails Jay Nitikman
2005-11-13 23:51 ` Jay Nitikman [this message]
2005-11-14 0:10 ` James Cameron
2005-11-14 13:20 ` Jay Nitikman
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=4377D16C.8000500@permeable.com \
--to=jay@permeable.com \
--cc=linux-ppp@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 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.