Sensible. If that were the case, a solution would rely in the capacity
of the network manager to detect that the new route does not work,(and
that the previous one did)

My naïve solution would be to ping a reliable server (I use 8.8.8.8) and
delete the new route if it timesout.

Additionally, if the new cabled connection were successful initially,
but later stopped working, shouldn't the network fallback to the
previous connection? A similar thing already happens when multiple dns
servers are specified.

2 functionalities failed for this bug to occur. (a third one if you
count my phone presenting itself as a router when it can't do that, but
that's not within Ubuntu's jurisdiction... is it?)

-- 
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/1879211

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1879211/+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