I don't understand how the specific fix would work, but the general process towards a resolution would be for someone to investigate the code and find out why and how the default route is being adjusted, for someone to use this information to determine how the application should behave, for someone to use that information to prepare a patch, for someone to wrap the patch in a debdiff, and for someone to upload a new revision including that debdiff to the repositories. These could be different people or all one person, depending on who has which knowledge and skills.
>From my viewpoint, a correct solution would include the ability of the VPN provider to allow or block a default route not through the VPN, would be consistent and documented, would match the behaviour of commercial clients, and would integrate properly with NetworkManager. -- No default internet traffic after connecting to VPN https://bugs.launchpad.net/bugs/124663 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
