https://bugs.kde.org/show_bug.cgi?id=520363
Bug ID: 520363
Summary: SSTP VPN editor in Plasma NetworkManager lacks IPv6
controls; invalid IPv6 config causes otherwise-working
SSTP connection to fail
Classification: Plasma
Product: plasmashell
Version First 6.3.6
Reported In:
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Networking in general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
Product: plasma-nm
Component: VPN (or Network Management, whichever is closest)
Environment:
NetworkManager
network-manager-sstp
SSTP VPN configured through Plasma NetworkManager GUI
Problem:
The Plasma NetworkManager editor for SSTP VPN connections does not expose any
IPv6 configuration options. Only IPv4 settings are available in the GUI.
However, during SSTP connection establishment, NetworkManager still processes
IPv6 configuration internally. If the SSTP plugin returns an invalid or
incomplete IPv6 configuration, NetworkManager aborts the entire VPN connection
even though IPv4 configuration and authentication succeeded correctly.
This makes it impossible to disable IPv6 handling from the Plasma GUI, and
causes otherwise-functional SSTP VPN connections to fail.
Observed behavior:
The SSTP VPN authenticates successfully using CHAP and receives valid IPv4
addressing and DNS information, but the connection is immediately terminated
after NetworkManager reports:
vpn[...] invalid IP6 config received: address is zero
vpn[...] did not receive valid IP config information
Immediately afterward, NetworkManager terminates pppd/sstpc with signal 15.
Relevant log excerpts:
CHAP authentication succeeded
local IP address 192.168.252.241
remote IP address 192.168.252.1
primary DNS address 142.202.76.2
secondary DNS address 142.202.79.2
vpn[...] invalid IP6 config received: address is zero
vpn[...] did not receive valid IP config information
pppd[...] Terminating on signal 15
Workaround:
The connection works correctly if IPv6 is manually disabled using nmcli:
nmcli connection modify "SSTP-connection" ipv6.method disabled
After doing this, the SSTP VPN connects and operates normally.
Expected behavior:
One or both of the following should happen:
The Plasma SSTP editor should expose IPv6 configuration controls, including the
ability to disable IPv6 for the VPN connection.
NetworkManager / plasma-nm should not treat missing or malformed IPv6
configuration as fatal when IPv4 configuration is valid and functional.
Additional notes:
The issue appears to be specific to the Plasma NetworkManager SSTP editor/UI
integration. The underlying VPN connection itself functions correctly once IPv6
processing is disabled manually outside the GUI.
--
You are receiving this mail because:
You are watching all bug changes.
