VPN service fails after update applied in Debian Squeeze Post: 302711615

Sponsored Content

Operating Systems Linux Debian VPN service fails after update applied in Debian Squeeze Post 302711615 by r4ym4r on Monday 8th of October 2012 08:53:03 AM

10-08-2012

Registered User

VPN service fails after update applied in Debian Squeeze

Hello everybody,

I used to log in to my office via PPTP VPN, but on last October 5th I updated my installed Debian Squeeze and it caused my VPN service (client-side) to fail. After this upgrade I'm unable to log in to the VPN server. Here follows the log:

Code:

#tail -f /var/log/messages
Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded.
pppd 2.4.5 started by root, uid 0
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
LCP: timeout sending Config-Requests
Connection terminated.
Modem hangup.
Exit.

According to the log I saved I see the following packages were upgraded:

Code:

libnm-glib-vpn1
network-manager

as well as some others (including the Linux kernel).

I reset my VPN configuration via Gnome's Network Manager without satisfactory results.

The authentication method I use is CHAPv2.

Could you please give me a hand to solve my VPN connection issue?

---------- Post updated 10-08-12 at 06:53 AM ---------- Previous update was 10-07-12 at 07:09 AM ----------

Here you are some new fresh information that might be useful to debug this issue:

root@thunderbox:/home/thor# tail -f /var/log/messages
[
...
]
Oct 8 08:21:42 thunderbox pppd[3357]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded.
Oct 8 08:21:42 thunderbox kernel: [ 244.066976] PPP generic driver version 2.4.2
Oct 8 08:21:42 thunderbox pppd[3357]: pppd 2.4.5 started by root, uid 0
Oct 8 08:21:42 thunderbox pppd[3357]: Using interface ppp0
Oct 8 08:21:42 thunderbox pppd[3357]: Connect: ppp0 <--> /dev/pts/2
Oct 8 08:21:45 thunderbox pppd[3357]: Connection terminated.
Oct 8 08:21:45 thunderbox pppd[3357]: Exit.

root@thunderbox:/home/thor# tail -f /var/log/debug
[
...
]
Oct 8 08:21:42 thunderbox modem-manager: (net/ppp0): could not get port's parent device

I think it is specially important this part: modem-manager: (net/ppp0): could not get port's parent device. This looks strange for me. However, I'd noticed this message appears when I open Virtual Box, look at this:

Oct 8 08:48:38 thunderbox modem-manager: (net/vboxnet0): could not get port's parent device

I don't want to deviate what I am looking to be solved, but I think the output above might be useful, too.

How to regain access to my VPN? Please suggest.

Last edited by Scott; 10-07-2012 at 10:18 AM.. Reason: Please use code tags.

r4ym4r

View Public Profile for r4ym4r

Find all posts by r4ym4r

2 More Discussions You Might Find Interesting

1. IP Networking

Corporate VPN service with separate nets for different users/groups

Hi We are going to host some services for customers with separate private networks for each customer. Each customer will need one or more users. I have to put up a VPN solution, and I would like to use something that will work on "any" platform, easily, without too much...

2. Solaris

flash update fails

Hi I am trying to update firmware of SF V440 but I am getting below error, Sun Fire V440, No Keyboard Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.10.10, 4096 MB memory installed, Serial #56988021. Ethernet address 05:30:b0:56:a1:3d, Host ID: 8356a25d. ...

LEARN ABOUT CENTOS

pppd-radius

PPPD-RADIUS(8)						      System Manager's Manual						    PPPD-RADIUS(8)

NAME

       radius.so - RADIUS authentication plugin for pppd(8)

SYNOPSIS

       pppd [ options ] plugin radius.so

DESCRIPTION

       The  RADIUS  plugin for pppd permits pppd to perform PAP, CHAP, MS-CHAP and MS-CHAPv2 authentication against a RADIUS server instead of the
       usual /etc/ppp/pap-secrets and /etc/ppp/chap-secrets files.

       The RADIUS plugin is built on a library called radiusclient which has its own configuration files (usually in  /etc/radiusclient),  consult
       those files for more information on configuring the RADIUS plugin

OPTIONS

       The RADIUS plugin introduces one additional pppd option:

       radius-config-file filename
	      The  file  filename  is  taken  as  the  radiusclient  configuration  file.   If	this  option  is  not  used,  then the plugin uses
	      /etc/radiusclient/radiusclient.conf as the configuration file.

       avpair attribute=value
	      Adds an Attribute-Value pair to be passed on to the RADIUS server on each request.

       map-to-ifname
	      Sets Radius NAS-Port attribute to number equal to interface name (Default)

       map-to-ttyname
	      Sets Radius NAS-Port attribute value via libradiusclient library

USAGE

       To use the plugin, simply supply the plugin radius.so option to pppd, and edit /etc/radiusclient/radiusclient.conf appropriately.   If  you
       use  the  RADIUS  plugin,  the  normal  pppd authentication schemes (login, checking the /etc/ppp/*-secrets files) are skipped.	The RADIUS
       server should assign an IP address to the peer using the RADIUS Framed-IP-Address attribute.

SEE ALSO

       pppd(8) pppd-radattr(8)

AUTHOR

       David F. Skoll <dfs@roaringpenguin.com>

																    PPPD-RADIUS(8)