So a couple more comments... 1. Do we know if NM sees the mobile connection drop, and thus it re- activates the context again, or does the context appear active to NM the whole time and the connection drops and re-establishes itself without action from NM? My guess based upon Oliver's description is that the latter is happening.
2. Android is obviously able to handle devices that configure the routing table ( although I have seen references in the code that rild implementation should *not* do this ). Do we know how Android handles this? 3. How difficult would it be to change the NM policy so that we never have concurrent active mobile and Wi-Fi connections? Our current model is that we leave the mobile connection active when Wi-Fi is activated, and then just switch the default route to Wi-Fi once connected. One final thought along these lines, does this leave us in a situation where an app could have an active network session and continue to use mobile data when Wi-Fi is activated? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307981 Title: [touch] randomly messed up routing with recent trusty images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1307981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
