Hi Marcel ,
I was about to close this still open bug (which was cloned from a bug that was
closed), but decided to check the forum link you posted first :
https://debianforum.de/forum/viewtopic.php?t=183809
and noticed you said there you were still having an issue with
network-manager-l2tp and
Hi Michael,
> Is there anything to fix on the network-manager package side or can
> this issue be closed?
With the upgrade of the network-manager package to 1.36.4-1, the
VPN routing issue appears to have been resolved.
I just checked again now that I'm not able to reproduce the issue,
so this
Hi Doug
On Tue, 22 Mar 2022 00:38:54 + Douglas Kosovic wrote:
I suspect this is the same as the following upstream NetworkManager 1.36.2
routing bug:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/946
I assume you have enabled the "Use this connection only for
As mentioned to the upstream NetworkManager 1.36.2 VPN routing bug:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/946
The routing issue when the "Use this connection only for resources on its
network" IPv4 setting is enabled, no longer appears to occur with
I suspect this is the same as the following upstream NetworkManager 1.36.2
routing bug:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/946
I assume you have enabled the "Use this connection only for resources on
its network" checkbox in the VPN connection's IPv4 settings?
Control: clone -1 -2
Control: reassign -2 network-manager-l2tp
Am 18.03.22 um 10:50 schrieb Marcel Jira:
Package: network-manager
Version: 1.36.2-1
Severity: important
Tags: upstream
X-Debbugs-Cc: marcel.j...@gmail.com
I used to connect to a VPN using network-manager-l2tp and
Package: network-manager
Version: 1.36.2-1
Severity: important
Tags: upstream
X-Debbugs-Cc: marcel.j...@gmail.com
I used to connect to a VPN using network-manager-l2tp and network-manager-l2tp-
gnome.
The connection recently stopped working (see log below). A connection is
established but
7 matches
Mail list logo
