I'm running Precise. The 'Pass "lo" as faked tundev to NM' patch results in Network Manager setting a 172.16.X.X IP on "lo" on VPN connect. Since this replaces 127.0.0.1, other software breaks. Then, on VPN disconnection, Network Manager takes "lo" down.
This can be trivially confirmed by running "ifconfig lo" before doing anything, after connecting a VPN, and again after disconnecting the VPN. Can someone on Trusty or higher test this? Things work great if I change it to use "dummy0", but that requires configuring a dummy0 interface, so that's not a usable solution for the package. Has anyone looked into just fixing Network Manager to not require an interface? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-networkmanagement in Ubuntu. https://bugs.launchpad.net/bugs/872824 Title: Network-manager locks up when adding strongSwan VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement/+bug/872824/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
