Thank you for the additional information. If you hit the bug in an upgrade from Xenial to Bionic, then why did you report version 1.60-26ubuntu1 of net-tools as affected? This version shipped with Xenial, not Bionic. Please could you confirm the version of net-tools that affects you with this problem on Bionic?
I accept that an upgrade from Xenial to Bionic that uses ifupdown will continue to do so. I hadn't considered that. However, use of dummy0 in the way that you are doing seems to me to be an unusual end-user configuration, so I think it still qualifies as Importance: Low against https://wiki.ubuntu.com/Bugs/Importance. In any case the Importance doesn't really matter; I just want to set the expectation that you shouldn't expect developers to jump on this for you, since Bionic was released over a year ago now and you appear to be the only person affected by this problem. On Tue, May 14, 2019 at 08:01:16PM -0000, John Denker wrote: > If it really is deprecated and unsupported, somebody > should file a separate bug against the documentation. I didn't say it was unsupported. Patches are welcome. I specifically did say it is still maintained. However everything that you can do with ifconfig you can do with ip(8), and there are many modern networking things that ifconfig does not support. ip(8) was written to replace it. ** Changed in: net-tools (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in net-tools package in Ubuntu: New Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
