[Bug 951410] New: Cannot connect to VPN using openconnect
http://bugzilla.opensuse.org/show_bug.cgi?id=951410 Bug ID: 951410 Summary: Cannot connect to VPN using openconnect Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: rjschwei@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After updating to TW 20151014 it is no longer possible to connect via openconnect using NetworkManager to Cisco backed infrastructure. The same behavior is observed with vpnc Using the previously functioning VPN configuration through NetworkManager does not establish the VPN connection. Unfortunately I cannot provide the message form the notification popup as I accidentally clicked the "Don't show this message again" button in the notification popup. With vpnc the password for the VPN connection is not accepted. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=951410 http://bugzilla.opensuse.org/show_bug.cgi?id=951410#c6 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org Flags| |needinfo?(rjschwei@suse.com | |) --- Comment #6 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Robert Schweikert from comment #3)
vpnc: can't open /dev/net/tun, check that it is either device char 10 200 or (with DevFS) a symlink to ../misc/net/tun (not misc/net/tun): No such device vpnc: can't initialise tunnel interface: No such device
# ls -l /dev/net total 0 crw-rw-rw- 1 root root 10, 200 Oct 22 17:58 tun
I suspect the same issue applies to using VPN with NM.
if vpnc has an issue on it's own, then NM is certainly impacted by the same... it's in essence a GUI frontend calling vpnc in the background. Now of course, vpnc did not get any package changes for about a year - so finding what broke will be fun. You mentioned after updating to 20151014 you saw the problem: do you happen to know from which snapshot up updated from (previous would have been 20151012, but there is a good chance of course you don't dup daily)
grep openSUSE-release /var/log/zypp/history | tail
should give the required info (maybe you need a longer tail in case you updated too often since then) With this info, we might at least have a chance to narrow down what all might have changed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=951410 http://bugzilla.opensuse.org/show_bug.cgi?id=951410#c7 --- Comment #7 from Dominique Leuenberger <dimstar@opensuse.org> --- oh, and let's check the usual suspects:
lsmod | grep tun modprobe -v tun
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=951410 http://bugzilla.opensuse.org/show_bug.cgi?id=951410#c8 --- Comment #8 from Robert Schweikert <rjschwei@suse.com> --- -> grep openSUSE-release /var/log/zypp/history | tail 2015-10-01 17:53:09|install|openSUSE-release-ftp|20150924-1.2|x86_64||repo-oss|fb5350c641f48c021462ec9643195571bf5fc319| 2015-10-01 17:53:12|install|openSUSE-release|20150924-1.2|x86_64||repo-oss|6728bdbc3e458070aee1cf370ad271fc876c6dc3| 2015-10-04 19:03:22|install|openSUSE-release-ftp|20151002-1.2|x86_64||repo-oss|021ea05a8eceae3383ccd1d38693aad0025734bd| 2015-10-04 19:03:46|install|openSUSE-release|20151002-1.2|x86_64||repo-oss|f20da1dec8c727a4f4b056a9671cbadcc9d67379| 2015-10-16 09:06:42|install|openSUSE-release-ftp|20151012-1.2|x86_64||repo-oss|81454cc08ab5a8899ce7523ec4d7f3d07b67fe26| 2015-10-16 09:07:00|install|openSUSE-release|20151012-1.2|x86_64||repo-oss|4f572f665f1460062a7ac2ca635e057bc3a263e8| 2015-10-19 07:28:18|install|openSUSE-release-ftp|20151014-1.2|x86_64||repo-oss|6a9166d98ffdd521df996991221286aada3f656d| 2015-10-19 07:28:54|install|openSUSE-release|20151014-1.2|x86_64||repo-oss|c72043dab95bca5ac134b9fe4b8451355757f18a| 2015-10-23 07:27:38|install|openSUSE-release-ftp|20151017-1.3|x86_64||repo-oss|b53836f9edd5da77ad0a88b98ebc67a48e7617fe| 2015-10-23 07:27:50|install|openSUSE-release|20151017-1.3|x86_64||repo-oss|c2be77dcdda7957bf2262a6b95f50f67d2b49b86| -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=951410 http://bugzilla.opensuse.org/show_bug.cgi?id=951410#c9 Robert Schweikert <rjschwei@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rjschwei@suse.com | |) | --- Comment #9 from Robert Schweikert <rjschwei@suse.com> --- # lsmod | grep tun tun 32768 0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=951410 http://bugzilla.opensuse.org/show_bug.cgi?id=951410#c10 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|os.gnome.maintainers@gmail. |tittiatcoke@gmail.com |com | --- Comment #10 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Robert Schweikert from comment #8)
09:07:00|install|openSUSE-release|20151012-1.2|x86_64||repo- oss|4f572f665f1460062a7ac2ca635e057bc3a263e8| 07:28:54|install|openSUSE-release|20151014-1.2|x86_64||repo- oss|c72043dab95bca5ac134b9fe4b8451355757f18a|
ok.. so a frequent updater... that narrows it hopefully down ==> assigne Raymond (as bugowner of vpnc) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=951410 http://bugzilla.opensuse.org/show_bug.cgi?id=951410#c11 Robert Schweikert <rjschwei@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #11 from Robert Schweikert <rjschwei@suse.com> --- Found some inconsistencies on my machine. After resolving those VPN connection works as expected. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com