https://bugs.kde.org/show_bug.cgi?id=464253
Bug ID: 464253
Summary: Support NAT
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Compiled Sources
OS: All
Status: REPORTED
Severity: minor
Priority: NOR
Component: common
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Consider the situation where two clients are on a network with hairpin NAT
(e.g. they are on the same Wireguard network, with the gateway set up to enable
IP forwarding).
In this case, packets are NAT-ed by the gateway. When this is done, the source
port is replaced by a randomly allocated port on the gateway.
When kdeconnectd receives the initial packet, it disregards the packet's source
port and always attempts to reply to port 1716. This causes the packet to not
be routed by the gateway back to the original server, causing the devices to
not see each other.
Ideally, kdeconnectd should pay attention to the port number of received
packets, and reply to this number. Hopefully, combined with adding devices by
IP in the mobile client, that should allow kdeconnect to work on such network
configurations.
--
You are receiving this mail because:
You are watching all bug changes.
