OpenConnect takes measures to ensure that when it reconnects to establish the VPN after authentication, it connects to the *same* server that it authenticated too. Anything else isn't going to work.
Unfortunately, it only does this if it spots more than one result in the DNS lookup, and realises that there's a round-robin. Otherwise, it just continues to use the hostname.
This doesn't work when there's a trick DNS server returning different results each time for load-balancing or other reasons. We need to use the specific IP address *every* time.
Fixed upstream by http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/4e2ab55b1a
openconnect-7.03-1.fc21 has been submitted as an update for Fedora 21.
libnm-qt-0.9.8.3-2.fc20, kde-plasma-nm-0.9.3.5-5.fc20, openconnect-7.03-1.fc20, NetworkManager-openconnect-0.9.8.6-1.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openconnect-7.03-1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
openconnect-7.03-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
openconnect-7.03-1.fc20, NetworkManager-openconnect-0.9.8.6-1.fc20, libnm-qt-0.9.8.3-3.fc20, kde-plasma-nm-0.9.3.5-7.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.