Ubuntu
network-manager package

DHCP Renewal Kills Anyconnect VPN Connections

Bug #1783903 reported by Blade Coates on 2018-07-26

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	Confirmed	Low	Unassigned

Bug Description

When using the Cisco Anyconnect client to connect to my works VPN. The VPN is unstable and drops into re configuring mode when a DHCP request is sent. From my research if I remove the network-manager-config-connectivity-ubuntu package the connection is stable.

Similar Issues for like package with FC28: https://bugzilla.redhat.com/show_bug.cgi?id=1576910

Description: Linux Mint 19 Tara
Release: 19

network-manager:
  Installed: 1.10.6-2ubuntu1
  Candidate: 1.10.6-2ubuntu1
  Version table:
*** 1.10.6-2ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

network-manager-config-connectivity-ubuntu:
  Installed: 1.10.6-2ubuntu1
  Candidate: 1.10.6-2ubuntu1
  Version table:
*** 1.10.6-2ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
        100 /var/lib/dpkg/status

Log attached next comment

See original description

Revision history for this message

Blade Coates (romeoblade) wrote on 2018-07-26:

issuelog.log Edit (35.6 KiB, text/plain)

description:	updated
description:	updated

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-11-08:

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

Changed in network-manager (Ubuntu):
status:	New → Confirmed

Revision history for this message

Sebastien Bacher (seb128) wrote on 2018-11-09:

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.