ubuntu-phonedations-bugs team mailing list archive

[Tony Espy <1435328@xxxxxxxxxxxxxxxxxx>]

@Alfonso

So looking closer at NM 0.9.8, the routing is updated by nm-policy.c in
its device_state_changed() function.  It calls update_routing_and_dns()
in several places, which in turn calls update_ip4_routing(), which in
turn calls nm_system_replace_default_ip4_route().  Only the last
function returns an error code, so if adding the default route fails,
the error doesn't bubble up, and the system is left partially
configured.

I hacked nm_system_replace_default_ip4_route() to return an error on
it's third invocation, then rebooted the system with WiFi disabled.
The first call to replace_default_ip4_route() happens when the mobile
data connection is established on reboot.  Next I activated WiFi and the
phone connected to an AP, that's the second route call.  Finally I
disabled WiFi and this triggers the third route call which fails.  At
this point we have a connection that NM still thinks is connected, with
an empty routing table.

Next I deactivated the context manually, and NM turned around and re-
established the connection, so I *think* this proves that the scenario
you described in comment #26 isn't happening with NM 0.9.8.

At this point, as changing the NM logic isn't super straight-forward, I
would suggest that we don't attempt to patch NM for utopic-RTM at this
point, unless someone else is able to prove for certain that NM can get
wedged in a bad state when the routing configuration fails.

-- 
You received this bug notification because you are a member of Ubuntu
Phonedations bugs, which is subscribed to ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1435328

Title:
  Leaving Wifi does not connect to mobile carrier data (GSM)

Status in the base for Ubuntu mobile products:
  Confirmed
Status in ofono package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu RTM:
  In Progress

Bug description:
  After leaving my home or work wifi, my Bq phone cannot connect to the
  data from my mobile carrier. The only thing that works is rebooting
  the phone.

  Steps to reproduce:

  1- Connect your phone to password secure Wifi.
  2- Suspend phone.
  3- Leave wifi area and resume phone
  4- Wait for 3g data to kick in (appears 3g indicator instead of wifi)
  5- No connection established. I have waited for more than 30 mins.

  6- A reboot of the phone fixes this issue.

  Really annoying to have to reboot phone 3-4 times a day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435328/+subscriptions