[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
[Expired for lxc-android-config (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: lxc-android-config (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
I'm removing the 'connectivity' tag, as this bug was specifically for
the issue where the routing table ends up with multiple conflicting
routes, and thus this is a slightly different problem than the current
problems seen with RTM ( empty routing table when switching from WiFi to
mobile data ).
** Tags added: connectivity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1307981
Title:
[touch] randomly messed up routing
Status in lxc-android-config package in Ubuntu:
I don't know that we're still seeing the same routing issues, so
unassigning for now.
Furthermore, as I understand it, this may well have been due to devices
handling; so on vivid with Tony's patches to ignore both ccmni* and
rmnet_usb* devices, we should be all good.
** Changed in:
Still not fixed it seems, was able to reproduce this issue on mako last
friday:
phablet@ubuntu-phablet:~/build/telepathy-ofono-0.2+14.10.20140725.2/obj-arm-linux-gnueabihf$
ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0
Could the routes now be in a different table, or added after NM has run
the 02default_route_workaround script?
Ideally, when reproduced, this issue should include both /var/log/syslog
for the full logs from NetworkManager, as well as the output of the 'ip
route' command, rather than 'route -n'.
Changed Status to FixCommitted, as this has landed in -proposed.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
lxc-android-config (0.163) utopic; urgency=medium
* add /etc/NetworkManager/dispatcher.d/02default_route_workaround to make
sure the default route is always reset when an interface change is
detected (LP: #1307981)
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
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
on boot my routing is usually fine ... what i see today is:
- boot with proper default route over WLAN, mobile is enabled but not owning
the default route.
- leave the phone next to me in the office or living room (both covered by the
same WLAN) and randomly pick up the device to check G+ or
After some discussion with Mathieu yesterday, there's one addition to my
previous comment.
On some phones, and in this case mako, rild actually configures the
routing table for the mobile network connection. As rild is a binary
blob, and there's no parameters available to control this behavior,
That routing code is a red herring, it's actually never reached in the
case where wifi is already activated, because wifi remains the best IP4
connection available (given that it has a higher priority than modems).
From what I see here, it seems like rild is just *always* setting the
route, and
I'm not sure what you mean by the routing code is a red herring?
Also, I'd like to get the exact scenario nailed down.
Oliver's description said that he had Wi-Fi enabled the whole time. If
so, was the routing table *ever* correct, or was it broken from boot
onwards?
So which of the
After the initial device boot, it has a valid default route pointing at
wlan and network access is enabled, then at some point rild comes along
and blindly adds a new default route due to the data call dropping and
being re-established.
This is only a problem when wifi is enabled, because
The routing and in particular the switching of the default route is
handled soley by NM.
This was an issue last Summer during initial development of the NM ofono
code, but Mathieu believed he'd resolved the issue.
Apparently there's still some sort of race and it's possible that other
recent
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1307981
Title:
maybe red herring, but see this entry which probably indicates that
stuff doesn't go as expected:
Apr 28 16:55:42 ubuntu-phablet NetworkManager[1212]: error
[1398718542.745922] [nm-system.c:965] add_ip4_route_to_gateway():
(rmnet_usb0): failed to add IPv4 route to gateway (-12)
--
You received
pat: the syslog you attached was captured when you were in that state?
or after reboot/fixing?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1307981
Title:
[touch] randomly
could be red herring, but guess that error could really make nm not do
proper default route replace...
in nm-system.c:1043 you see the code that will give up trying to replace
the gateway in case the add_ip4_route_to_gateway call fails...
/* Try adding a direct route to the gateway first
sorry above i referenced wrong linenumber inside the vpn specific code
... but the same pattern is also around 1094...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1307981
cypher/tony: maybe worth checking/debugging this code and making it more
robust?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1307981
Title:
[touch] randomly messed up
ignore my posts in #10 and #11... i misread that code... however, the
error in #9 seems to be in code that is only run if something with the
normal default route replace didn't work...
someone with device and closer to code probably should check this out.
Maybe ofono or the modem driver also
Happened here after first flash and boot to u3 on mako
phablet@ubuntu-phablet:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
default 10.185.115.145 0.0.0.0 UG0 00
rmnet_usb0
default 10.0.1.1
Same symptoms on 5 straight boots
Turning wifi off allowed 3g to work
Turning 3g off allowed wifi to work
Disabled 3g data and then reboot wlan worked fine
Enabled 3g data and reboot and back to the network not being reachable
--
You received this bug notification because you are a member of
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1307981/+attachment/4100752/+files/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
i just noticed bug 1314410
do not rely on a webapp for testing if your connectivity is back
(restarting the app works fine indeed, but the button on the error page
nor the refresh option from the hud does not)
--
You received this bug notification because you are a member of Desktop
Packages,
ogra@styx:~/apps$ adb shell ip route
default via 37.83.18.26 dev rmnet_usb1
default via 192.168.2.1 dev wlan0 proto static
37.83.18.24/30 dev rmnet_usb1 proto kernel scope link src 37.83.18.25
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.78 metric 9
ogra@styx:~/apps$
If this happens again, could you get the same routing table but with the
'ip route' command instead?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1307981
Title:
[touch]
30 matches
Mail list logo
