After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 705222 - Need --no-xmlpost for openconnect
Need --no-xmlpost for openconnect
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: VPN: openconnect
git master
Other Linux
: Normal normal
: ---
Assigned To: David Woodhouse
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-08-01 03:04 UTC by Darrin Thompson
Modified: 2015-07-28 15:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Darrin Thompson 2013-08-01 03:04:10 UTC 
I'm connecting to a network that seems to require the --no-xmlpass argument to openconnect. Can we add a way for me to configure that from network manager?
Comment 1 Darrin Thompson 2013-08-01 03:05:19 UTC 
Actually, that should have read --no-xmlpost
Comment 2 itchy355 2013-12-05 12:24:46 UTC 
Second that. I can't use NM any more for VPN connections.
Comment 3 Daniel Walker 2015-07-28 15:04:40 UTC 
I suspect a lot of problems like this could be fixed if openconnect had a default config file. Then you could add whatever you needed into that config to work around issues like this.
Comment 4 David Woodhouse 2015-07-28 15:15:57 UTC 
I'd be more inclined to accept a way for NM-openconnect to pass config options, rather than a system-wide file.

But really, it shouldn't be needed. The need for --no-xmlpost was basically a *bug*. I wouldn't want to design any scheme where it is required in perpetuity. Or indeed, where *any* such workaround is required. OpenConnect should Just Work.

I'm going to close this bug (since --no-xmlpost really shouldn't be needed any more now that OpenConnect is fixed). Please re-open if there are still issues.