Here is better evidence.
Just now I ran the experiment using same kernel version, 4.19.42,
as in the xenial experiment reported above.
My conclusions are unchanged. The newly-introduced incompatible
and inconsistent behavior depends on the modprobe release, not
on the kernel release. I knew
I have conducted more investigation into the cause, resulting in a
significant restatement of the issue.
As far as this bug is concerned, it appears there has been no
regression, indeed no change in behavior in ifconfig (net-tools package)
or ifup (ifupdown package). However it could be argued
Contrasting attachment, as discussed in previous comment.
** Attachment added: "bionic: insmod and modprobe behave differently"
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+attachment/5264585/+files/dummy-bionic.logg
--
You received this bug notification because you are
To reiterate and clarify: net-tools and ifupdown both exhibit the bug
in bionic, whereas neither exhibits the bug in xenial. The bug is
observed in the following package versions:
:; apt-cache policy net-tools
net-tools:
Installed: 1.60+git20161116.90da8a0-1ubuntu1
Candidate:
Message 2 of 2: This is easy to use and/or test ifup dummy0 and ifdown
dummy0
You don't need to know the complexities of the motivation for why this
is important; the test case is very simple.
In the context of the ifupdown package, this requires putting a stanza like
this in
Msg 1 of 2: Here is a use-case for ifup dummy0 and ifdown dummy0:
I have multiple laptops. Sally has multiple laptops. Sometimes they
are wired (for speed) and sometimes wireless (for portability).
Sometimes we are at the same workplace, or at my abode, or her abode, or
the local library, or
Can you please transfer this to the ifupdown package?
Or should I just resubmit it from scratch?
The discussions of the importance of ifconfig are beside the point.
The problem presented itself during boot-up, in connection with
an "auto dummy0" directive in /etc/network/interfaces.
If "auto
*) As for priority: It's not as low as you might imagine.
The problem affects not just ifconfig but also ifup, which is
indispensable. It also affects the "raise network interface"
target at boot time, as triggered by "auto dummy0" directives
in /etc/network/interfaces.
Symptom:
:; ifup dummy0
Public bug reported:
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
Here's the workaround.
** Attachment added: "workaround for ifconfig dummy0 bug"
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+attachment/5263317/+files/dummy-workaround
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I put the attached file in if-pre-up.d/dummy-workaround
to make my system work reliably.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828749
Title:
ifconfig dummy0 : Device not found
To manage
11 matches
Mail list logo
