touch-packages team mailing list archive

[Tony Espy <1454625@xxxxxxxxxxxxxxxxxx>]

NetworkManager is supposed to handle adding a specific host route for a
MessageProxy present in a combined APN.  This doesn't appear to be
happening anymore in vivid.

I checked krillin/rtm #22/sim1=ATT sim2=empty.

With WiFi off, the routing table looks like this:

default via 10.186.165.219 dev ccmni0  proto static
66.209.11.32 dev ccmni0  proto static  scope link

Note, the MessageProxy from the active APN is 'wireless.cingular.com',
which is publicly resolvable to...66.209.11.32.

With WiFi on, the routing table looks like this:

default via 192.168.1.1 dev wlan0  proto static
66.209.11.32 dev ccmni0  proto static  scope link
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.8  metric 9

So, when the download manager connects through the proxy, it's data
flows over the mobile data interface ( ccmni0 ).

When I flash vivid-devel, on the same device, with the same SIM
configuration.  When WiFi is off, the routing table looks like this:

default via 10.177.125.140 dev ccmni0  proto static  metric 1024

When WiFi is enabled, it looks like this:

default via 192.168.1.1 dev wlan0  proto static  metric 1024 
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.8 

...which means all traffic goes over the WiFi interface.

I've produced similar results on mako/rtm #19/ATT SIM.  I haven't yet
retried mako/vivid, but I suspect the same problem as with krillin.

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

Title:
  Cannot send MMS messages with combined contexts with WiFi connected

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  New

Bug description:
  Cannot send MMS messages with combined contexts in case the WiFi is
  connected, for some operators. Combined contexts are able to handle
  internet data and MMS data. For the operator for which I've seen the
  bug, the data is:

  $ /usr/share/ofono/scripts/list-contexts
  [ /ril_0 ]
      [ /ril_0/context1 ]
          Password =
          MessageCenter = http://www.pepephone.com
          Name = MMS Pepephone
          Username =
          Protocol = ip
          Preferred = 0
          IPv6.Settings = { }
          Settings = { }
          MessageProxy = 10.138.255.43:8080
          Type = internet
          AccessPointName = gprs.pepephone.com
          Active = 0

  Sending an MMS with cellular data and WiFi enabled fails for this
  operator when using a combined context. Disabling WiFi I was able to
  send the MMS.

  The error I see in ~/.cache/upstart/dbus.log is:

  E0513 09:55:03.254148  4565 file_upload.cpp:345] Upload ID{
  d0e5da6eb7664d908ab49b810ff55e01 }  http://www.pepephone.com
  ERROR::Network error UnknownNetworkError: an unknown network-related
  error was detected

  The interface that were up when the failure happened were:

  $ ifconfig
  rmnet_usb0 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
            inet addr:10.60.155.62  Mask:255.255.255.0
            inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
            UP RUNNING  MTU:1500  Metric:1
            RX packets:4 errors:0 dropped:0 overruns:0 frame:0
            TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:829 (829.0 B)  TX bytes:1052 (1.0 KB)

  wlan0     Link encap:Ethernet  HWaddr 10:68:3f:7a:92:d5
            inet addr:192.168.1.40  Bcast:192.168.1.255  Mask:255.255.255.0
            inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:355 errors:0 dropped:0 overruns:0 frame:0
            TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:100
            RX bytes:51241 (51.2 KB)  TX bytes:18951 (18.9 KB)

  See attached the tcpdump of the packets sent when this happened. Some
  quick analysis shows that the uploader is sending through the WiFi
  (192.168.1.40) instead of using 10.60.155.62, so it is clearly a
  routing problem. The MMS proxy has private address 10.138.255.43 so it
  is not reachable from WiFi.

  Reproduced in:
  mako vivid-proposed image #195
  arale vivid-proposed image #38
  krillin vivid-proposed image #205

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1454625/+subscriptions