@Andrea

There are two tests I'd like you to run for me.

First, let's verify the baseline by flashing OTA10 ( pre-NM 1.1.93
landing ) on a spare krillin, and then set the WiFi connection to the
opposite as earlier suggested, this time setting ipv4.method to ignore.
This will validate that IPv6 connections were actually working ( vs.
just not causing DNS to fail ), even though the kernels lack support for
IPv6 peer addresses ( which NM 1.2x always uses when adding IPv6
addresses, and which in turn always fail ).

Second, there are three cases currently that I can see where NM adds
IPv6 addresses ( note, there are more possible, but these are the most
common when method=auto ):

 - NM always configures an IPv6 Link Local address with the peer set to
the "Any" address ( all zeros or :: ); the code states that a LL address
is always added for any method other than "ignore"

 - a VPN configuration specifies an IPv6 address ( in this case, our VPN
always sets the peer with the interface identifier part of the address
set to ::1/64 )

 - an address is received via RDP ( router discovery protocol ); this is
the case that happens when you associate to an AP that supports IPv6 and
method=auto

As I can't reproduce the last case ( my ISP doesn't support IPv6 yet ),
it would be great if you could run NetworkManager in the foreground with
an env var specified which triggers netlink debug messages.  This will
let me see what peer_address is being set when you connect to the work
AP.  If you want to send me these traces privately, that might be best.
Please use a recent rc-proposed image.

Here are the steps:

1. From system-settings::wifi, "forget" the access point

2. adb into the phone, and start an interactive sudo session:

# sudo -i

3. Stop NM

# stop network-manager

4. Run the script command to capture output:

# script nm-nl.out

5. Start NetworkManager in the foreground like this:

# NLCB=debug /usr/sbin/NetworkManager -n -d --log-level=debug --log-
domains=ip6,wifi,vpn

6. From the indicator, connect to the AP

7. Leave the connection up and NM running for 5-10m

8. Kill NM via Ctl-C

9. Exit the script via Ctl-D

10. Grab the script output and send it to me direct, or put on a
fileshare

Please let me know if you have any questions, or want to discuss before
you try any of this.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1580146

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to