Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1538608 - openconnect drop vpn connection if packet arrived is larger than MTU (Juniper / Pulse)
Summary: openconnect drop vpn connection if packet arrived is larger than MTU (Juniper...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openconnect
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-25 12:31 UTC by Enrico Tagliavini
Modified: 2019-01-11 04:34 UTC (History)
2 users (show)

Fixed In Version: openconnect-8.01-1.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 04:34:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Enrico Tagliavini 2018-01-25 12:31:29 UTC
Description of problem:

VM connection drops as soon as I start using it. I think it has to be something of a significant size, a standard ping (64 bytes) seems not to be enough to trigger this. Trying to load a web page definitely is. Logs shows the following (note I configure the VPN via NetworkManager):

Jan 24 19:57:38 f016l-700bcb.fmi.ch NetworkManager[1461]: <info>  [1516820258.2945] device (vpn0): Activation: successful, device activated.
Jan 24 19:57:38 f016l-700bcb.fmi.ch NetworkManager[1461]: <info>  [1516820258.2975] policy: set 'vpn0' (vpn0) as default for IPv4 routing and DNS
Jan 24 19:57:54 f016l-700bcb.fmi.ch openconnect[7238]: Unrecognised data packet
Jan 24 19:57:54 f016l-700bcb.fmi.ch openconnect[7238]: Unknown KMP message 300 of size 1500:
Jan 24 19:57:54 f016l-700bcb.fmi.ch openconnect[7238]: Unknown error; exiting.

At this point the VPN connection drops. The VPN type is Pulse Secure.

Version-Release number of selected component (if applicable):

root ~ # rpm -qa | grep openconnect
plasma-nm-openconnect-5.11.5-1.fc27.x86_64
NetworkManager-openconnect-gnome-1.2.4-6.fc27.x86_64
NetworkManager-openconnect-1.2.4-6.fc27.x86_64
openconnect-7.08-4.fc27.x86_64

How reproducible:
always

Steps to Reproduce:
I'm not sure what conditions should be applied on the server side, I have no access to the appliance configuration. All I know it's a Pulse Secure, it's not the old Juniper.
1. Configure a VPN connection of type Juniper / Pulse with openconnect, for example using NetworkManager
2. connect and login to the VPN, confirm networkmanager reporting success
3. start generating traffic going through the VPN, for example by opening a website

Actual results:
connection drops immediately with mentioned log found


Expected results:
connection should not drop


Additional info:

This is actually a known issue, see [1] for a ML thread with a proposed patch and quite a discussion following. Ultimately there is a patch available that was merged upstream many months ago, you can find it at [2]. Would it be possible to include this in the Fedora package to mitigate the issue?

Thank you.

[1] http://lists.infradead.org/pipermail/openconnect-devel/2017-May/004301.html
[2] http://git.infradead.org/users/dwmw2/openconnect.git/commit/9ac5e232214b728f675a44c43e61986ff9245b57

Comment 1 Ben Cotton 2018-11-27 17:21:46 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora Update System 2019-01-07 07:43:08 UTC
openconnect-8.01-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-267b29539a

Comment 3 Fedora Update System 2019-01-08 02:04:58 UTC
openconnect-8.01-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-267b29539a

Comment 4 Fedora Update System 2019-01-11 04:34:05 UTC
openconnect-8.01-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.