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 dummy0" and "ifup dummy0" are not maintained then why
bother to have a dummy device at all?  This is the most important
context, although there are MANY others.  I reported the ifconfig
context because it is the /simplest/ ... not the only manifestation.

And no, I'm definitely not the first person to encounter the bug.
I'm just the first to report it through this channel.  My first
message in this thread linked to a report that came up in another
context.

As for the software versions:
I must have typed the "apt-cache policy net-tools" in the wrong
window at one point.  As stated before that and after that, the
fact is that bionic is buggy while xenial is not.  Specifically,
the buggy packages are:

:; apt-cache policy net-tools
net-tools:
  Installed: 1.60+git20161116.90da8a0-1ubuntu1
  Candidate: 1.60+git20161116.90da8a0-1ubuntu1
  Version table:
 *** 1.60+git20161116.90da8a0-1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

and perhaps more to the point:

:; apt-cache policy ifupdown
ifupdown:
  Installed: 0.8.17ubuntu1.1
  Candidate: 0.8.17ubuntu1.1
  Version table:
 *** 0.8.17ubuntu1.1 500
        500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
        100 /var/lib/dpkg/status
     0.8.17ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

-- 
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     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to