[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias

Rolf Leggewie 123773 at bugs.launchpad.net
Sun Nov 23 15:08:00 UTC 2014


Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as "Won't Fix".

** Changed in: wireless-tools (Ubuntu Hardy)
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to wireless-tools in Ubuntu.
https://bugs.launchpad.net/bugs/123773

Title:
  'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip
  alias

Status in “ifupdown” package in Ubuntu:
  Invalid
Status in “wireless-tools” package in Ubuntu:
  Fix Released
Status in “ifupdown” source package in Hardy:
  Invalid
Status in “wireless-tools” source package in Hardy:
  Won't Fix

Bug description:
  Binary package hint: ifupdown

  Add the following to /etc/network/interfaces on Feisty:
  auto  eth0
  iface eth0 inet static
          address 192.168.3.50
          netmask 255.255.255.0
          gateway 192.168.3.1

  auto eth0:0
  iface eth0:0 inet static
          address 192.168.3.51
          netmask 255.255.255.0

  Then do:
  $ sudo ifup eth0 (works fine)
  $ sudo ifup eth0:0
  SIOCSIFFLAGS: Cannot assign requested address

  However, though ifup (and ifdown) will give that error, the interface comes up fine, and is pingable:
  $ ifconfig
  ...
  eth0:0    Link encap:Ethernet  HWaddr 00:04:5A:7D:4C:73
            inet addr:192.168.3.51  Bcast:192.168.3.255  Mask:255.255.255.0
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            Interrupt:9 Base address:0xf800
  ...
  $ ping -c 1 192.168.3.51
  PING 192.168.3.51 (192.168.3.51) 56(84) bytes of data.
  64 bytes from 192.168.3.51: icmp_seq=1 ttl=64 time=0.079 ms

  --- 192.168.3.51 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.079/0.079/0.079/0.000 ms

  This configuration works fine in Dapper.  Also, using ifconfig on its own works too:
  $ sudo ifconfig eth0:0 192.168.3.51 up

  If nothing else, the message is confusing to the user (it was to me,
  since I thought something was wrong when it seems to work fine).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/+subscriptions



More information about the foundations-bugs mailing list