https://bugs.kde.org/show_bug.cgi?id=428569
ak <anth...@windowslive.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anth...@windowslive.com
--- Comment #3 from ak <anth...@windowslive.com> ---
Looking over at Wireshark, it appears that the identity UDP packet has grown to
be around 1700-1850 bytes, ie a Jumbo Frame.
The reason is that the identity packet lists all of the device's capabilities,
which have grown to be a lot.
When in a local LAN (according to Wireshark) the router/phone fragments the
packet into two and sends it correctly to the computer. However, OpenVPN not
having this capability sends half of the packet, which gets ignored by the
computer.
Perhaps the proper solution would be to rework the protocol to fix the packet
size, but that may require modification of all the clients that implement the
protocol.
However, there is a botch available.
The default upper limit of UDP packets in most interfaces is 1500 bytes.
OpenVPN has a fragment option that would split the identity packet, but it's
not supported in Android. Another option is to use the tun-mtu-extra option,
which will resize the internal buffer of OpenVPN to be able to accept larger
packets, with whatever issue that may cause.
Adding the following two lines in the client/server configs of OpenVPN fixes
the issue by allowing the packet through.
tun-mtu sets the max packet size to be 1500 (if it's not already) and
tun-mtu-extra allows OpenVPN to accept packets up to 500 bytes larger (so up to
2000).
tun-mtu 1500
tun-mtu-extra 500
It would be nice to edit the KDE Connect readme at least for the time being
with the above option.
https://userbase.kde.org/KDEConnect#Running_KDE_Connect_over_OpenVPN
Software:
Phone: KDE Connect 1.17 (also tried 1.13), Android 10, Official OpenVPN client
(unofficial also has this issue)
Computer: kdeconnect 21.08.1-1, OpenVPN 2.5.3
--
You are receiving this mail because:
You are watching all bug changes.
