[Bug 1828749] Re: ifconfig dummy0 : Device not found
Robie Basak
1828749 at bugs.launchpad.net
Thu May 16 11:57:48 UTC 2019
Thank you for the additional information. I think this report is now
complete, and I think I understand exactly what you mean and how you are
affected.
Unfortunately the use cases you have presented don't change my opinion
that this is an unusual end-user configuration that is unlikely to
affect the majority of Ubuntu users. Therefore I don't intend to
prioritise working on it and don't expect other developers to volunteer
their time to do so.
My opinion will of course change if it turns out that there is some
other use case that is likely to impact a wider range of Ubuntu users.
Volunteers to investigate this problem deeper are welcome. Please do
continue to use this bug to coordinate any efforts.
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => New
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1828749
Title:
ifconfig dummy0 : Device not found
Status in ifupdown package in Ubuntu:
New
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/ifupdown/+bug/1828749/+subscriptions
More information about the foundations-bugs
mailing list