public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: RE: Cisco vpnclient prevents proper shutdown starting with 2.6.2
Date: Sat, 07 Feb 2004 21:20:13 +0000	[thread overview]
Message-ID: <4025568D.5070800@blueyonder.co.uk> (raw)

Meinhard E. Mayer wrote:
 > Until version 2.6.1 the Cisco VPN module (version 4.0.3(B)) cisco_ipsec,
 > although "tainted" worked fine with all 2.4.22 and 2.6 kernel versions.
 > However, for 2.6.2, although the module compiles and loads, starting the
 > vpnclient hangs, and the client cannot be stoped (i.e.
 > /etc/init.d/vpnclient_init stop also hangs, and therefore both shutdown
 > and reboot of the computer do not complete, and I was forced to "pull
 > the plug." Fortunately the journaled file system prevented serious
 > damage.
 >
 > I used the same .config (which I append) for compiling 2.6, 2.6.1, and
 > 2.6.2, so I assume that something in your networking drivers must have
 > changed to cause this bug.
 >
 > I would appreciate any suggestions for fixing this problem, since I need
 > VPN to access the University library.
I tried using this client with up to 2.6.1-mm5 and ended up with  Dead 
processes for cvpnd and vpnclient, nothing else was affected, went back 
to 2.4.x kernel.
Regards
Sid

-- 
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.


             reply	other threads:[~2004-02-07 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07 21:20 Sid Boyce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-27  0:30 Cisco vpnclient prevents proper shutdown starting with 2.6.2 Sid Boyce
2004-02-24 20:41 Gertjan van Wingerde
2004-02-25  3:46 ` Eugene Teo
     [not found] <fa.fds2rgj.110cgg9@ifi.uio.no>
2004-02-24 15:50 ` jhp
2004-02-23  1:33 Patrick Toal
2004-02-07  5:17 Meinhard E. Mayer
2004-02-07  9:10 ` Eduard Bloch
2004-02-08 16:05 ` Rik van Riel

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=4025568D.5070800@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --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