wow, in the end I think I really fixed this bug. I didn't think I would try fixing libnl backend ever, but here we go. Give it a try. Will bake a release after testing this for a bit...
------------------------------------------------------------
revno: 372
fixes bug: https://launchpad.net/bugs/770390
committer: Alexander Sack <email address hidden>
branch nick: ntrack
timestamp: Tue 2014-10-28 00:52:45 +0100
message:
modules[libnl]: redo reconnect logic noticed when topmost default route changes like in case of connecting/disconnecting from VPN - fixes lp:770390
This patch cleans up various aspects of the logic used to identify and process changes to topmost_route
that trigger a reconnect event.
While such logic in theory can happen often, in network-manager case we only observe this when having
two physical cards going on and off changing the default route and when enabling and disabling VPN.
wow, in the end I think I really fixed this bug. I didn't think I would try fixing libnl backend ever, but here we go. Give it a try. Will bake a release after testing this for a bit...
------- ------- ------- ------- ------- ------- ------- ------- ---- /launchpad. net/bugs/ 770390 disconnecting from VPN - fixes lp:770390
revno: 372
fixes bug: https:/
committer: Alexander Sack <email address hidden>
branch nick: ntrack
timestamp: Tue 2014-10-28 00:52:45 +0100
message:
modules[libnl]: redo reconnect logic noticed when topmost default route changes like in case of connecting/
This patch cleans up various aspects of the logic used to identify and process changes to topmost_route
that trigger a reconnect event.
While such logic in theory can happen often, in network-manager case we only observe this when having
two physical cards going on and off changing the default route and when enabling and disabling VPN.