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
Old 10-08-2012
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.
 

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... (0 Replies)
Discussion started by: signal
0 Replies

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. ... (3 Replies)
Discussion started by: upengan78
3 Replies
DH_INSTALLSYSTEMD(1)						     Debhelper						      DH_INSTALLSYSTEMD(1)

NAME
dh_installsystemd - install systemd unit files SYNOPSIS
dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...] DESCRIPTION
dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting systemd unit files. In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from sysvinit to systemd and back. For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and dh_installsystemd --name=quotarpc quotarpc.service. FILES
debian/package.service, debian/package@.service If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build directory. debian/package.tmpfile If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is currently only used by systemd.) debian/package.target, debian/package@.target If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build directory. debian/package.socket, debian/package@.socket If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build directory. debian/package.mount If this exists, it is installed into lib/systemd/system/package.mount in the package build directory. debian/package.path, debian/package@.path If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build directory. debian/package.timer, debian/package@.timer If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build directory. OPTIONS
--no-enable Disable the service(s) on purge, but do not enable them on install. Note that this option does not affect whether the services are started. Please remember to also use --no-start if the service should not be started. --name=name Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used, dh_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service. Moreover, maintainer scripts are only generated for units that match the given name. --restart-after-upgrade Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10. In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. --no-restart-after-upgrade Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the prerm script and started again in the postinst script. -r, --no-stop-on-upgrade, --no-restart-on-upgrade Do not stop service on upgrade. --no-start Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a corresponding init script). Note that this option does not affect whether the services are enabled. Please remember to also use --no-enable if the services should not be enabled. NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments). Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org 11.1.6ubuntu2 2018-05-10 DH_INSTALLSYSTEMD(1)
All times are GMT -4. The time now is 05:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy