libgcrypt11 version 1.5.0-3ubuntu2.2 breaks vpnc for cisco 3000 gateway

Bug #1217183 reported by mitch_feaster on 2013-08-27
54
This bug affects 11 people
Affects Status Importance Assigned to Milestone
libgcrypt11 (Ubuntu)
Undecided
Unassigned

Bug Description

It appears that version 1.5.0-3ubuntu2.2 of libgcrypt11 breaks vpnc for some cisco 3000 vpn gateways. Ever since I updated I haven't been able to connect, but today I rolled back to libgcrypt11=1.5.0-3ubuntu2.1 and things are working again. Note that I tried with 1.5.0-3ubuntu2.2 immediately before rolling back so it's highly unlikely that anything changes on the cisco gateway side to fix it.

With libgcrypt11=1.5.0-3ubuntu2.2 I was seeing the following messages in /var/log/syslog:

    Aug 21 22:44:56 sonbuntu NetworkManager[1193]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)
    Aug 21 22:44:56 sonbuntu NetworkManager[1193]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found.
    Aug 21 22:44:56 sonbuntu NetworkManager[1193]: <warn> /sys/devices/virtual/net/tun0: couldn't determine device driver; ignoring...
    Aug 21 22:47:06 sonbuntu avahi-daemon[1116]: Withdrawing workstation service for tun0.
    Aug 21 22:47:06 sonbuntu NetworkManager[1193]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0)
    Aug 21 22:48:08 sonbuntu NetworkManager[1193]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)
    Aug 21 22:48:08 sonbuntu NetworkManager[1193]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found.
    Aug 21 22:48:08 sonbuntu NetworkManager[1193]: <warn> /sys/devices/virtual/net/tun0: couldn't determine device driver; ignoring...

I also strace'd vpnc and things seemed to hang around here:

    time(NULL) = 1377150323
    times({tms_utime=8, tms_stime=1, tms_cutime=0, tms_cstime=0}) = 1717972828
    gettimeofday({1377150323, 725505}, NULL) = 0
    getrusage(RUSAGE_SELF, {ru_utime={0, 88000}, ru_stime={0, 16000}, ...}) = 0
    time(NULL) = 1377150323
    times({tms_utime=8, tms_stime=1, tms_cutime=0, tms_cstime=0}) = 1717972828
    time(NULL) = 1377150323
    poll([{fd=3, events=POLLIN}], 1, 96000) = 0 (Timeout)
    poll([{fd=3, events=POLLIN}], 1, 192000^C <unfinished ...>

After rolling back to libgcrypt11=1.5.0-3ubuntu2.1 I don't see these messages and I can successfully connect to my vpn.

See also: http://askubuntu.com/questions/335694/vpnc-has-stopped-working-with-cisco-vpn-gateway-ubuntu-13-04

description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libgcrypt11 (Ubuntu):
status: New → Confirmed
John Pang (john-pijin) wrote :

I'm not sure this is a problem with libgcrypt11. I had the same messages in my syslog as those posted... but it turns out that it was my password had expired. The syslog didn't tell me anything to indicate an expired password, but as soon as my vpn password got reset, I could connect again.

mitch_feaster (mitch-special) wrote :

I'm also not 100% sure that libgcrpyt11 is to "blame" but as I changed one variable at a time that was where my bisection landed. I also confirmed that going back to the latest libgcrypt11 re-broke things, and re-rolling-back re-fixed them. Notably, my vpn account wasn't locked out and my password had not expired.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers