Attached is the NetworkManager dispatch script which is supposed to add the MMS Proxy route. This script is part of the lxc-android-config package. I've verified that it exists in our vivid images. For some reason it appears to be broken.
The script is passed the modem_path ( env:DEVICE_IPATH ) and connection ( env:CONNECTION_ID). If either is 'None', the script silently fails. Next it validates both to ensure that they start with "/", if they don't it again silently fails. Next it does a synchronous DBus call to ConnectionContext.GetProperties() in order to grab 'Settings', and in turn 'Gateway' ( for logging ). If 'MessageProxy' is found, it's used for new route, else if 'MessageCenter' is found, it's used instead. The script then attempts to resolve the hostname using socket.gethostbyname(). I *think* this is a no-op if the MessageProxy is specified as dotted network address instead of a hostname. The script then uses subprocess.call() to add the route. No error checking is done for the "ip route" command. The bulk of the logic is surrounding by a try/catch block, which does log a "failed to add route" message, however I'm not seeing this in my syslog, so I believe the failure is earlier in the script itself, or maybe the dispatch mechanism isn't properly triggering the script? I think with some additional logging we should be able to pinpoint the failure... ** Attachment added: "NetworkManager MMS Proxy script" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1454625/+attachment/4397058/+files/03mmsproxy ** Changed in: ubuntu-download-manager (Ubuntu) Status: New => Incomplete ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- 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 the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: Incomplete 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/canonical-devices-system-image/+bug/1454625/+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
