Bug 2452330 - force mtu and skip detection - "Received unexpected packet (04) in MTU detection; skipping"
Summary: force mtu and skip detection - "Received unexpected packet (04) in MTU detect...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openconnect
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-27 16:30 UTC by Angelo Theodorakis
Modified: 2026-05-07 02:58 UTC (History)
4 users (show)

Fixed In Version: openconnect-9.12-11.fc44
Clone Of:
Environment:
Last Closed: 2026-05-05 00:54:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
result from fedpkg mockbuild --root fedora-43-x86_64 and rpm install (312.95 KB, text/plain)
2026-04-27 17:05 UTC, Angelo Theodorakis
no flags Details

Description Angelo Theodorakis 2026-03-27 16:30:49 UTC
This issue was reported already here: https://gitlab.com/openconnect/openconnect/-/work_items/823

A merge was committed with a fix: https://gitlab.com/openconnect/openconnect/-/commit/5fec1e2db56c7fce4e4de74baf8dec0d9efcd313

The fix is not yet built upstream so the Fedora repo provided package does not offer this yet.

The fix also addresses an issue where openconnect will not apply proposed IPv6 address.

Updating openconnect manually from the gitlab version fixes the issue


git clone https://gitlab.com/openconnect/openconnect.git

./autogen.sh
./configure
make -j$(nproc)


Can a new build be expedited upstream with the proposed fix and commit included? 

Reproducible: Always

Steps to Reproduce:
1. Initiate connection with VPN endpoint
2. Establish connection
3. IPv6 address provided by endpoint does not actually apply to the connection settings
Actual Results:
IPv6 advertised by the server does not apply to the client settings. IPv6 only addresses will then not work.

Expected Results:
IPv6 settings to apply locally and connection to fully work.

Additional Information:
Commit already exists and just needs to be added to the next build: 5fec1e2db56c7fce4e4de74baf8dec0d9efcd313

Comment 1 Angelo Theodorakis 2026-04-27 17:05:10 UTC
Created attachment 2138414 [details]
result from fedpkg mockbuild --root fedora-43-x86_64 and rpm install

result from mockbuild test for the PR here: https://src.fedoraproject.org/rpms/openconnect/pull-request/8#

Comment 2 Fedora Update System 2026-05-01 14:27:18 UTC
FEDORA-2026-6da4d1fce3 (openconnect-9.12-11.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-6da4d1fce3

Comment 3 Fedora Update System 2026-05-02 02:59:12 UTC
FEDORA-2026-6da4d1fce3 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-6da4d1fce3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6da4d1fce3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-05-05 00:54:55 UTC
FEDORA-2026-6da4d1fce3 (openconnect-9.12-11.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, 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.