More of a meta comment : If Ubuntu wishes to be taken seriously as a professional workstation OS (as I'm sure it will do, with an impending IPO next year), issues blocking VPN connectivity - especially to the Usual Suspect endpoints like L2TP (which will cover anyone using e.g. Azure for their corporate VPN) - need to be considered far more important.
This issue was reported four months ago and will block Azure VPN connections from 22.04 until it's fixed (in the absence of workarounds), which means that many users would be unable to do their job, but has yet to be marked with an importance other than "Undecided". As an engineer who believes strongly that Linux has a place among his co-workers, it gets increasingly hard to justify this to operations when their compliance requirements (like connecting to VPNs) cannot be met out of the box. L2TP is, yes, a Microsoft thing. But that doesn't mean you shouldn't be taking it seriously - quite the opposite, as that means it forms a substantial minority of VPN endpoints out there. Hackarounds like manually installing old package versions or alternative VPN clients [1] do not inspire confidence. I know that the maintainers are absolutely doing their best within the constraints they are operating in, this comment is more directed at Canonical, in the hope that they can understand this is a part of the distro that needs to be tested and supported more rigorously. [1] https://bugs.launchpad.net/ubuntu/+source/network-manager- strongswan/+bug/1457078/comments/19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
