From: Patrick McHardy <kaber@trash.net>
To: Jorge Daniel Sequeira Matias <martin@andorinha.ist.utl.pt>
Cc: linux-ppp@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: pppd stuck in ioctl(TIOCSETD) in Linux 2.6.15.4+
Date: Tue, 27 Jun 2006 22:43:14 +0000 [thread overview]
Message-ID: <44A1B482.80901@trash.net> (raw)
In-Reply-To: <004b01c69a3a$6b80c660$0201a8c0@athlon64>
Jorge Daniel Sequeira Matias wrote:
>
> Hi everyone,
>
> I'm running a PPTP VPN Server for almost 4 years now. This server is
> running in a Debian Linux (unstable).
> The configuration for the last 1 year and a half was the following:
>
> Computer 2x Intel Xeon 2.6GHz and 512MB RAM
> Linux v2.6.11.6 (vanilla) with MPPE patch
> Debian distribution with the following packages
> - pppd 2.4.3-20050321
> - libradius1 0.3.2-8
> - radiusclient1 0.3.2-8
>
> With this configuration I had reach a peek of aprox. 600 hundred PPTP
> connections simultaneously. The computer gets heavy loaded doing MPPE
> compression/decompression with 40Mbits/sec of PPP traffic but didn't
> have any problem with this setup. The authentication process is using a
> pool of RADIUS servers.
>
> This machine is also a firewall, and now a new feature was needed:
> PPTP VPN connections from the inside.
>
> The problem:
>
> After the upgrade to a Linux v2.6.15.4 (vanilla) with no patches to
> use the new "ip_conntrack_pptp" module, I started to get "pppd"
> processes hanging in "S" state and consuming CPU power.
Does the problem go away without the ip_conntrack_pptp module loaded?
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Jorge Daniel Sequeira Matias <martin@andorinha.ist.utl.pt>
Cc: linux-ppp@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: pppd stuck in ioctl(TIOCSETD) in Linux 2.6.15.4+
Date: Wed, 28 Jun 2006 00:43:14 +0200 [thread overview]
Message-ID: <44A1B482.80901@trash.net> (raw)
In-Reply-To: <004b01c69a3a$6b80c660$0201a8c0@athlon64>
Jorge Daniel Sequeira Matias wrote:
>
> Hi everyone,
>
> I'm running a PPTP VPN Server for almost 4 years now. This server is
> running in a Debian Linux (unstable).
> The configuration for the last 1 year and a half was the following:
>
> Computer 2x Intel Xeon 2.6GHz and 512MB RAM
> Linux v2.6.11.6 (vanilla) with MPPE patch
> Debian distribution with the following packages
> - pppd 2.4.3-20050321
> - libradius1 0.3.2-8
> - radiusclient1 0.3.2-8
>
> With this configuration I had reach a peek of aprox. 600 hundred PPTP
> connections simultaneously. The computer gets heavy loaded doing MPPE
> compression/decompression with 40Mbits/sec of PPP traffic but didn't
> have any problem with this setup. The authentication process is using a
> pool of RADIUS servers.
>
> This machine is also a firewall, and now a new feature was needed:
> PPTP VPN connections from the inside.
>
> The problem:
>
> After the upgrade to a Linux v2.6.15.4 (vanilla) with no patches to
> use the new "ip_conntrack_pptp" module, I started to get "pppd"
> processes hanging in "S" state and consuming CPU power.
Does the problem go away without the ip_conntrack_pptp module loaded?
next prev parent reply other threads:[~2006-06-27 22:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 22:38 pppd stuck in ioctl(TIOCSETD) in Linux 2.6.15.4+ Jorge Daniel Sequeira Matias
2006-06-27 22:43 ` Patrick McHardy [this message]
2006-06-27 22:43 ` Patrick McHardy
2006-06-27 22:50 ` Jorge Daniel Sequeira Matias
2006-06-27 22:50 ` Jorge Daniel Sequeira Matias
2006-06-27 23:03 ` Phil Mayers
2006-06-27 23:30 ` Jorge Daniel Sequeira Matias
2006-06-29 20:06 ` Jorge Daniel Sequeira Matias
2006-06-29 23:26 ` Paul Mackerras
2006-07-11 12:18 ` Jorge Daniel Sequeira Matias
2006-07-11 22:53 ` James Cameron
2006-07-12 11:46 ` Jorge Daniel Sequeira Matias
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=44A1B482.80901@trash.net \
--to=kaber@trash.net \
--cc=linux-ppp@vger.kernel.org \
--cc=martin@andorinha.ist.utl.pt \
--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.