ifup -a does not start alias interfaces
Bug #114457 reported by
Sergey V. Udaltsov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Debian) |
New
|
Unknown
|
|||
ifupdown (Ubuntu) |
Fix Released
|
Low
|
LinU | ||
Bug Description
In my /etc/network/
auto eth0
iface eth0 inet dhcp
auto eth0:0
iface eth0:0 inet static
address 192.168.7.2
netmask 255.255.255.0
broadcast 192.168.7.255
# gateway 192.168.7.1
But the interface eth0:0 does not start at reboot. If I switch eth0 and eth0:0 - no effect either.
Changed in ifupdown: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in ifupdown: | |
status: | Unknown → New |
Changed in ifupdown (Ubuntu): | |
assignee: | nobody → LinU (linu-realweb) |
To post a comment you must log in.
I have this problem on both Feisty ppc and Gutsy x86. If I use "sudo ifup eth0:0" after boot it works although I am affected by this bug: https:/ /bugs.launchpad .net/ubuntu/ +source/ ifupdown/ +bug/123773. This seems like a major problem. I am unable to share files via NFS between 2 boxes hardwired into a basic hub without manually starting the iface for the alias every time I boot. If someone with more knowledge than myself could suggest a workaround that would be nice.